Anonymous | Login | Signup for a new account | 11-10-2008 11:10 PST |
Main | My View | View Issues | Change Log | Docs |
Viewing Issue Simple Details [ Jump to Notes ] | [ View Advanced ] [ Issue History ] [ Print ] | ||||||||
ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||
0001179 | [BusyBox] New Features | feature | always | 01-26-07 12:00 | 03-07-07 15:03 | ||||
Reporter | db | View Status | public | ||||||
Assigned To | BusyBox | ||||||||
Priority | normal | Resolution | fixed | ||||||
Status | closed | Product Version | |||||||
Summary | 0001179: [PATCH] hwclock must understand /dev/rtc0, /dev/rtc1, etc | ||||||||
Description |
For the past year or more, Linux has had an RTC framework supporting multiple RTCs, conventionally named /dev/rtcN (N starting at zero). This is widely used on embedded Linuxes, since there are so many different implementations of RTCs, and systems may need more than one (e.g. the full featured integrated one may not be battery backed). The /dev/rtc name is conventionally used only for the RTC on an x86_pc. The busybox "hwclock" doesn't understand those names, and has no way to access more than one RTC at a time, even if someone sets up a symlink from e.g. rtc pointing at rtc0. |
||||||||
Additional Information |
The attached patch is against busybox SVN which I pulled down a few minutes ago. It matches functionality which should be included in the next util-linux release. A command line option provides access to arbitrary RTC files; and if /dev/rtc isn't found, /dev/rtc0 is tried. |
||||||||
Attached Files | hwclock.patch [^] (3,319 bytes) 01-26-07 12:00 | ||||||||
|
Copyright © 2000 - 2006 Mantis Group |