From: Gabriel Paubert <paubert@iram.es>
To: Kumar Gala <kumar.gala@freescale.com>
Cc: linuxppc-dev@ozlabs.org, Christian <evil@g-house.de>
Subject: Re: use of rtc.c on chrp/prep?
Date: Fri, 2 Sep 2005 09:21:36 +0200 [thread overview]
Message-ID: <20050902072136.GA19676@iram.es> (raw)
In-Reply-To: <86F3DB1B-C396-45F4-8DBA-87176648D143@freescale.com>
On Thu, Sep 01, 2005 at 01:47:36PM -0500, Kumar Gala wrote:
> On Sep 1, 2005, at 1:38 PM, Sven Luther wrote:
>
> >On Thu, Sep 01, 2005 at 12:57:55PM -0500, Kumar Gala wrote:
> >
> >>Does anyone enable CONFIG_RTC on chrp/prep? Tom tells me these are
> >>the only platforms that it is even valid to do so on.
> >>
> >
> >The debian powerpc kernels enables :
> >
> > $ grep RTC /boot/config-2.6.12-1-powerpc
> > CONFIG_GEN_RTC=y
> > CONFIG_GEN_RTC_X=y
> >
> >and not the CONFIG_RTC variant, and it works well on pegasos, and prep
> >boxes,
> >and probably on ibm chrps too, altough i have not tested personally.
>
> Thanks, as far as I can tell no one is using CONFIG_RTC, which means
> I can "fix" asm-ppc/mc146818rtc.h to no longer #define RTC_IRQ 8
For the record, on MVME boards with PowerPlus bridges, the RTC driver
cannot work because the interrupt output is not connected. IRQ 8 is
instead connected to a front panel switch labelled abort that nobody
uses either (at least under Linux).
Anyway, there are better ways to obtain regularly spaced interrupts
on PPC. They are just not implemented (yet).
Gabriel
next prev parent reply other threads:[~2005-09-02 7:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-10 16:37 [PATCH] Use todc on Mot PReP platforms Matt Porter
2005-08-11 19:43 ` Tom Rini
2005-08-12 10:20 ` Christian
2005-09-01 17:57 ` use of rtc.c on chrp/prep? Kumar Gala
2005-09-01 18:38 ` Sven Luther
2005-09-01 18:47 ` Kumar Gala
2005-09-02 7:21 ` Gabriel Paubert [this message]
2005-09-04 0:41 ` evilninja
2005-08-16 5:52 ` [PATCH] Use todc on Mot PReP platforms Matt Porter
2005-08-16 7:19 ` Sven Luther
2005-08-16 7:33 ` Matt Porter
2005-08-16 14:49 ` Tom Rini
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=20050902072136.GA19676@iram.es \
--to=paubert@iram.es \
--cc=evil@g-house.de \
--cc=kumar.gala@freescale.com \
--cc=linuxppc-dev@ozlabs.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).