linux-kernel - Re: invalid default values in RTC chip

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]

Date:	Thu, 16 Oct 2008 13:58:46 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Jüri Reitel <juri.reitel@...wenthal.ee>
Cc:	linux-kernel@...r.kernel.org, David Brownell <david-b@...bell.net>,
	Jean Delvare <khali@...ux-fr.org>,
	Rodolfo Giometti <giometti@...ux.it>,
	rtc-linux@...glegroups.com
Subject: Re: invalid default values in RTC chip

On Tue, 14 Oct 2008 12:00:21 +0300
J__ri Reitel <juri.reitel@...wenthal.ee> wrote:

> Hi,
> 
> My question relates to RTC driver linux/drivers/rtc/rtc-ds1307.c for 
> device m41t00. Driver probe function will fail if some of the chip's 
> registers contain invalid date time values i.e. if month register is 32 
> or minutes is 61. Is this correct behavior? Probe function's purpose is 
> to check if the device is as was assumed (this time RTC and it is). The 
> chip's values are incorrect but the chip works, even the m41t00 chip 
> manual states that after initial powerup (RTC battery power applied) 
> internal registers will contain random data.
> 
> There are two solutions first is driver patch and another is i2c-dev and 
> i2cset tool to use from user space during bootup. Whitch one should be used?
> 

(cc's added)
--
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/