Would setting the CONFIG_RTC option break the powerpc kernel on your machine ?
sven.luther at wanadoo.fr
Wed Jan 7 18:47:40 EST 2004
On Wed, Jan 07, 2004 at 06:22:25PM +1100, Benjamin Herrenschmidt wrote:
> > 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 ?
> will the kernel let you build both drivers in ?
> then you can do, in 2.4, something ugly like that:
> #ifdef CONFIG_ALL_PPC
> if (_machine == _MACH_Pmac)
> return -ENODEV;
Mmm, two questions :
1) could a #ifdef __powerpc__ not be enough ?
2) The other failures in rtc_init return -EIO, not -ENODEV.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
More information about the Linuxppc-dev