On Wed, Jan 07, 2004 at 03:47:44PM +0100, Sven Luther wrote:
The worse that can happen is the GENERIC_RTC driver not being
initialized because linux believes the RTC driver should be ok.
which breaks hwclock, not acceptable.
--
Ethan Benson
http://www.alaska.net/~erbenson/
On Wed, Jan 07, 2004 at 10:27:33PM -0900, Ethan Benson wrote:
On Wed, Jan 07, 2004 at 03:47:44PM +0100, Sven Luther wrote:
The worse that can happen is the GENERIC_RTC driver not being
initialized because linux believes the RTC driver should be ok.
which breaks hwclock, not acceptable.
On Thu, Jan 08, 2004 at 08:53:31AM -0700, Tom Rini wrote:
On Wed, Jan 07, 2004 at 10:27:33PM -0900, Ethan Benson wrote:
On Wed, Jan 07, 2004 at 03:47:44PM +0100, Sven Luther wrote:
The worse that can happen is the GENERIC_RTC driver not being
initialized because linux believes the
Anyway, on pegasos 2, i have the problem that CONFIG_RTC works fine, and
the clock is set, but only _later_. This has as result that the clock is
wrong when it is the time for filesystem checks, and thus filesystems
are checked each time.
Your arch code should set an initial UTC time in
On Fri, Jan 09, 2004 at 08:53:07AM +1100, Benjamin Herrenschmidt wrote:
Anyway, on pegasos 2, i have the problem that CONFIG_RTC works fine, and
the clock is set, but only _later_. This has as result that the clock is
wrong when it is the time for filesystem checks, and thus filesystems
On Wed, Jan 07, 2004 at 12:27:26PM +0100, Sven Luther wrote:
Mmm, notice that this is the rtc_init code, not the rtc ioctl's
themself. In my understanding this is launched when the kernel is
loaded, and is used to setup the rtc clock. If it fails, then no harm
should be done, since the
6 matches
Mail list logo
