* David Brownell <[EMAIL PROTECTED]> wrote: > Start making the rtc-cmos alarm act more like a oneshot alarm by > disabling that alarm after its IRQ fires. (ACPI hooks are also > needed.) > > The Linux RTC framework has previously been a bit vague in this area, > but any other behavior is problematic and not very portable. RTCs > with full YYYY-MM-DD HH:MM[:SS] alarms won't have a problem here. > Only ones with partial match criteria, with the most visible example > being the PC RTC, get confused. (Because the criteria will match > repeatedly.) > > Update comments relating to that oneshot behavior and timezone > handling. (Timezones are another issue that's mostly visible with > rtc-cmos. That's because PCs often dual-boot MS-Windows, which likes > its RTC to match local wall-clock time instead of UTC.)
Cool. I'm still wondering about: http://bugzilla.kernel.org/show_bug.cgi?id=7014 basically, we had universally working /dev/rtc before, now it appears we dont have it anymore. Or were the problems in this bugzilla present with the old code too? Ingo -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
