From: Sven Luther <sven.luther@wanadoo•fr>
To: Benjamin Herrenschmidt <benh@kernel•crashing.org>
Cc: Sven Luther <sven.luther@wanadoo•fr>,
Tom Rini <trini@kernel•crashing.org>,
Lee Braiden <jel@ntlworld•com>,
debian-powerpc@lists•debian.org,
linuxppc-dev list <linuxppc-dev@lists•linuxppc.org>
Subject: Re: Would setting the CONFIG_RTC option break the powerpc kernel on your machine ?
Date: Wed, 7 Jan 2004 08:47:40 +0100 [thread overview]
Message-ID: <20040107074740.GB22544@iliana> (raw)
In-Reply-To: <1073460144.784.79.camel@gaston>
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;
> #endif
Mmm, two questions :
1) could a #ifdef __powerpc__ not be enough ?
2) The other failures in rtc_init return -EIO, not -ENODEV.
Friendly,
Sven Luther
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-01-07 7:47 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20031216105656.GA5291@iliana>
[not found] ` <1071642293.753.414.camel@gaston>
[not found] ` <200312170717.36564.jel@ntlworld.com>
[not found] ` <1071646057.6370.482.camel@gaston>
2003-12-17 9:51 ` Would setting the CONFIG_RTC option break the powerpc kernel on your machine ? Sven Luther
2003-12-17 10:27 ` Geert Uytterhoeven
2003-12-17 15:45 ` Segher Boessenkool
2003-12-17 16:18 ` Geert Uytterhoeven
2003-12-17 17:16 ` Segher Boessenkool
2003-12-17 16:47 ` Tom Rini
2003-12-17 16:56 ` Sven Luther
2003-12-17 17:06 ` Tom Rini
2003-12-17 17:10 ` Sven Luther
2003-12-17 17:24 ` Tom Rini
2003-12-19 11:40 ` Sven Luther
2003-12-19 16:28 ` Tom Rini
2003-12-22 13:45 ` Sven Luther
2003-12-22 16:10 ` Tom Rini
2003-12-22 16:26 ` Sven Luther
2003-12-22 16:33 ` Tom Rini
2003-12-22 16:48 ` Sven Luther
2003-12-22 16:59 ` Tom Rini
2003-12-22 17:02 ` Mark Guertin
2003-12-22 17:27 ` Sven Luther
2004-01-07 6:54 ` Sven Luther
2004-01-07 7:22 ` Benjamin Herrenschmidt
2004-01-07 7:43 ` Sven Luther
2004-01-07 7:47 ` Sven Luther [this message]
2004-01-07 8:30 ` Benjamin Herrenschmidt
2004-01-07 9:53 ` Sven Luther
2004-01-07 10:44 ` Benjamin Herrenschmidt
2004-01-07 10:54 ` Sven Luther
2004-01-07 11:47 ` Benjamin Herrenschmidt
2004-01-07 11:53 ` Sven Luther
2004-01-07 18:34 ` Tom Rini
2004-01-07 7:51 ` Ethan Benson
2004-01-07 11:27 ` Volunteer needed : " Sven Luther
2004-01-07 12:28 ` Ethan Benson
2004-01-07 14:47 ` Sven Luther
2004-01-08 7:27 ` Ethan Benson
2004-01-08 15:53 ` Tom Rini
2004-01-08 17:47 ` Sven Luther
2004-01-08 21:53 ` Benjamin Herrenschmidt
2004-01-08 21:57 ` Sven Luther
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040107074740.GB22544@iliana \
--to=sven.luther@wanadoo$(echo .)fr \
--cc=benh@kernel$(echo .)crashing.org \
--cc=debian-powerpc@lists$(echo .)debian.org \
--cc=jel@ntlworld$(echo .)com \
--cc=linuxppc-dev@lists$(echo .)linuxppc.org \
--cc=trini@kernel$(echo .)crashing.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox