Re: mimic the RTC restart delay (was: hwclock issue)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, 7 Aug 2008 14:41:14 +0200 (CEST)
Alain Guibert <alguibert+ulng@xxxxxxx> wrote:

> Hello David,
> 
>  On Wednesday, August 6, 2008 at 17:19:49 -0700, David Brownell wrote:
> 
> > in practice [/sys/class/rtc/rtc0/settime_offset_ms is] never needed
> > except for PC-compatible RTCs (as we already discussed).
> 
> You proposed that in the absence of the settime_offset_Ns information,
> hwclock should consider it to be zero. There is a problem with this
> approach: hwclock would misbehave on PC-compatible RTCs with today's and
> older kernels.

 hwclock could check /sys/class/rtc/rtc0/name and assume 0 if the driver
 is not rtc_cmos.
 

-- 

 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

[Index of Archives]     [Netdev]     [Ethernet Bridging]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux Admin]     [Samba]

  Powered by Linux