linux-kernel - 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-next>] [day] [month] [year] [list]

Date:	Tue, 14 Oct 2008 12:00:21 +0300
From:	Jüri Reitel <juri.reitel@...wenthal.ee>
To:	linux-kernel@...r.kernel.org
Subject: invalid default values in RTC chip

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?

PS. please add me to CC also.

JR
--
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/