On Sun, 2011-05-01 at 00:11 -0400, Neal Murphy wrote: > *As written*, the subsystem rule is triggered *if* the RTC is in subsystem > rtc; if there is no such subsystem, the rule will never be triggered. The > kernel rule will never be triggered because it is looking for a device with > kernel name 'rtc'; this device doesn't exist. If this rule is changed to look > for a device with correct kernel name of 'rtc0', it will be triggered.
Looking through kernel configs, I think it's a matter of kernel configuration, or possibly version. On my current (2.6.33.4) system, I don't have the "Real Time Clock" options enabled, and I have a /dev/rtc device that udevadm tells me belong to the "misc" subsystem - this would match one of the two rules. In contrast, my in-progress system (2.6.38.4) *does* have "Real Time Clock" enabled, and it has /dev/rtc0 (with a /dev/rtc symlink) which belongs to the 'rtc' subsystem - matching the other rule. Simon.
signature.asc
Description: This is a digitally signed message part
-- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
