linux-kernel - Re: [PATCH] rtc-ds1307: Reset bogus register values on m41t00

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: <200810301006.01689.david-b@pacbell.net>
Date:	Thu, 30 Oct 2008 10:06:01 -0700
From:	David Brownell <david-b@...bell.net>
To:	Nate Case <ncase@...-inc.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] rtc-ds1307: Reset bogus register values on m41t00

On Thursday 30 October 2008, Nate Case wrote:
> But, based on what you're saying, it sounds like I should rework this
> patch to make a 'ds1307_reset_regs()' function that would be called both
> when the registers are found to be in a bogus state (at least for the
> m41t00), and also anytime we restart the oscillator for all chips?

I think that'd be good, yes.

You'r sure that the m41t00 oscillator keeps going in this odd
state you're defending against, and it wouldn't suffice to have
the time and date registers initialized when restarting the
oscillator?

- Dave

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