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 RTC driver should be ok.
This doesn't work anyway, it stops pmacs from hanging but still there is a long wait, which you can ^C interrupt. I believe this is because since there is the RTC clock, the GENERIC_RTC code will not be called or something. > > which breaks hwclock, not acceptable. > > This is getting _much_ uglier, but how about: > 1) Modify genrtc.c and rtc.c so that they do _not_ initalize on their > own. > 2) Create a 'dummy_rtc.c' driver that just tests _machine and calls > rtc.c's init bits on chrp (or just pegasos) and genrtc's bits otherwise. > > And again, this is ugly ugly ugly, and I disavow any knowledge of > typing the above. That would be a solution, but i think i will look again at my previous effort. 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. Strange. Friendly, Sven Luther
