Would setting the CONFIG_RTC option break the powerpc kernel on your machine ?
Tom Rini
trini at kernel.crashing.org
Thu Dec 18 04:24:20 EST 2003
On Wed, Dec 17, 2003 at 06:10:52PM +0100, Sven Luther wrote:
>
> On Wed, Dec 17, 2003 at 10:06:20AM -0700, Tom Rini wrote:
> > On Wed, Dec 17, 2003 at 05:56:08PM +0100, Sven Luther wrote:
> > >
> > > On Wed, Dec 17, 2003 at 09:47:40AM -0700, Tom Rini wrote:
> > > > 4) Use CONFIG_GEN_RTC and be happy. What _might_ be happening right now
> > > > is that chrp_get_rtc_time is 'funky' and not quite right for anything
> > > > other than an IBM OpenFirmeware'd CHRP box. What I would suggest is
> > > > looking at include/asm-generic/rtc.h in 2.6 and moving much of that code
> > > > into 'chrp_get_rtc_time' and 'chrp_set_rtc_time'.
> > >
> > > Ok, thanks, i will look into it.
> > >
> > > But then, remember, this is for the debian powerpc kernel, and has to be
> > > 2.4.x still for now.
> >
> > Yes. The code in <asm-generic/rtc.h> is taken right from
> > drivers/char/rtc.c. It just didn't get sent to 2.4 for some reason.
>
> Ok, will do this tomorrow, thanks for your help.
>
> BTW, in this case, would it make sense to hide the CONFIG_RTC on powerpc ?
iff we get it working on chrp properly and someone adds the alarm
functionality, it shouldn't be objectionable.
--
Tom Rini
http://gate.crashing.org/~trini/
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
More information about the Linuxppc-dev
mailing list