On Mon, Dec 22, 2003 at 09:33:15AM -0700, Tom Rini wrote: > > On Mon, Dec 22, 2003 at 05:26:01PM +0100, Sven Luther wrote: > > > On Mon, Dec 22, 2003 at 09:10:42AM -0700, Tom Rini wrote: > > > > Also, the todc code knows about many RTC chips, among them, the MC146818 > > > > seems to be the one used by the rtc.h stuff, and seems to be a generic > > > > legacy RTC chip or something. he one i have, builtin the VIA VT8231 > > > > southbridge is said to be called VT82887, altough i have no docs of > > > > those, but the header files found in 2.6 concord. But i seem to have > > > > some additional DATE_ALARM, MONTH_ALARM and CENTURY_FIELD registers not > > > > found int the MC146818 header file. > > > > > > I appologize since I ramble a bit too much. For 2.4, the best fix is > > > (1) above. For 2.6 however, it should be possible to remove chrp_time.c > > > and use todc_time.c instead (it is self-contained, wrt nvram read/write, > > > iirc) and do some sub-casing to pick the right RTC chip code to use. > > > For example on PReP we still case between the two different chips, and > > > just call todc_init (iirc) with a different param. Or something along > > > those lines. > > > > Ok, i have looked more, and the MC146818 is ok for my box. don't know > > about other chrp boxes though. > > > > There is also the todc code in the 2.4 tree though, so it should also be > > possible to do it this way, or would it not ? > > It would be possible, but it would be more intrusive for a stable > series.
BTW, i didn't manage to get the generic RTC code working on my pegasos, and i am actually a bit pressed for time. Do you think a workaround, for the debian powerpc packages, would be to add a test for the presence of a pmac in the CONFIG_RTC code, and abort if one is found ? If so, what would be the best way to test for a pmac subarch in the drivers/char/rtc.c code ? Friendly, Sven Luther