lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080429145135.26d53758@i1501.lan.towertech.it>
Date:	Tue, 29 Apr 2008 14:51:35 +0200
From:	Alessandro Zummo <alessandro.zummo@...ertech.it>
To:	Uwe Kleine-König <Uwe.Kleine-Koenig@...i.com>
Cc:	David Brownell <dbrownell@...rs.sourceforge.net>,
	<linux-kernel@...r.kernel.org>
Subject: Re: rtc: how should I handle an invalid state?

On Tue, 29 Apr 2008 14:19:24 +0200
Uwe Kleine-König <Uwe.Kleine-Koenig@...i.com> wrote:

> Hello,
> 
> I'm still stuck with my rtc.  My current problem is setting the rtc
> using hwclock --systohc.
> 
> The problem is that hwclock tries to read the current time before
> setting the new one.  And if that fails, it doesn't update the rtc.

 That's a bug of hwclock. :( The correct behaviour for a driver
 is to return an error if the clock cannot be read.

-- 

 Best regards,

 Alessandro Zummo,
  Tower Technologies - Torino, Italy

  http://www.towertech.it

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ