Bug 3341 - hwclock.sh startup script does not work if hardware clock is kept in UTC
Summary: hwclock.sh startup script does not work if hardware clock is kept in UTC
Status: RESOLVED FIXED
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: core (show other bugs)
Version: 1.2.1
Hardware: x86 Multiple
: Medium normal
Target Milestone: 1.2.2
Assignee: Chen Qi
QA Contact:
URL:
Whiteboard: Patch sent to OE list.
Depends on:
Blocks:
 
Reported: 2012-10-26 20:10 UTC by Marc Ferland
Modified: 2012-11-05 03:33 UTC (History)
2 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Marc Ferland 2012-10-26 20:10:30 UTC 
The hwclock.sh script assumes the hardware clock is kept in localtime. A variable similar to the UTC variable found in /etc/default/rcS should be used to declare whether the HW clock is in local or UTC.

Based on the value of this variable, call hwclock with '--utc' or '--localtime'.

BTW, if the current UTC variable in /etc/default/rcS indicates the HW clock format then the comment should be changed (i.e.: it mentions the system time (linux clock) which is different from the HW clock (bios/cmos)).