From: Sven Luther <sven.luther@wanadoo.fr>
To: debian-powerpc@lists.debian.org,
linuxppc-dev list <linuxppc-dev@lists.linuxppc.org>
Subject: Re: Volunteer needed : Re: Would setting the CONFIG_RTC option break the powerpc kernel on your machine ?
Date: Wed, 7 Jan 2004 15:47:44 +0100 [thread overview]
Message-ID: <20040107144744.GA29449@iliana> (raw)
In-Reply-To: <20040107122828.GJ14918@plato.local.lan>
On Wed, Jan 07, 2004 at 03:28:28AM -0900, Ethan Benson wrote:
>
> On Wed, Jan 07, 2004 at 12:27:26PM +0100, Sven Luther wrote:
> >
> > Mmm, notice that this is the rtc_init code, not the rtc ioctl's
> > themself. In my understanding this is launched when the kernel is
> > loaded, and is used to setup the rtc clock. If it fails, then no harm
> > should be done, since the generic rtc driver should take over, not sure
> > though.
>
> sounds iffy to me. especially if both are compiled as modules, in
> which case the rtc module will be loaded, fail and im betting the
> whole thing stops right there.
Yeah, not sure also, need a volunteer to test it.
> debian used to ship kernels with both PPC_RTC and RTC as modules,
> hoping the right one would magically load and work on the right
> hardware, of couse this was not the case, RTC was always loaded, and
> broke powermacs.
Yeah, but this was because the RTC driver does some rtc register probing
the pmac hardware does not like. If the RTC clock detects it is a pmac,
it will fail to initialize before causing damage.
The worse that can happen is the GENERIC_RTC driver not being
initialized because linux believes the RTC driver should be ok.
Friendly,
Sven Luther
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-01-07 14: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
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 [this message]
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=20040107144744.GA29449@iliana \
--to=sven.luther@wanadoo.fr \
--cc=debian-powerpc@lists.debian.org \
--cc=linuxppc-dev@lists.linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).