On Mon, 17 Aug 2009 11:32:56 +0200 Karel Zak <kzak@xxxxxxxxxx> wrote: > > Looking at the other rtc drivers, some of them *do* set tm_isdst to -1, > > some of them (especially rtc-efi) set tm_isdst to real data ... so I'm > > not sure this patch to rtcwake will work right on EFI based systems. > > > > Would it be better to say this is a kernel RTC driver problem, in that > > it is returning 0 instead of -1 in tm_isdst? > > Redirecting to RTC guys, see > http://thread.gmane.org/gmane.linux.utilities.util-linux-ng/2516 I'm inclined to say that the whole DST thing is an userspace problem and that all hardware clocks should be set to UTC :) or rtc_read_alarm_internal could be patched to initialize that field to -1 prior to the call to ops->read_alarm -- Best regards, Alessandro Zummo, Tower Technologies - Torino, Italy http://www.towertech.it -- To unsubscribe from this list: send the line "unsubscribe util-linux-ng" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
