From: Tom Rini <trini@kernel.crashing.org>
To: Tolunay Orkun <listmember@orkun.us>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Question on RTC options (CONFIG_RTC, CONFIG_GEN_RTC, CONFIG_PPC_RTC)
Date: Tue, 6 Apr 2004 14:14:39 -0700 [thread overview]
Message-ID: <20040406211439.GD31152@smtp.west.cox.net> (raw)
In-Reply-To: <19625.216.110.51.8.1081285199.squirrel@www.orkun.us>
On Tue, Apr 06, 2004 at 03:59:59PM -0500, Tolunay Orkun wrote:
> >> CONFIG_RTC (PC Architecture?)
> >> CONFIG_GEN_RTC
> >> CONFIG_PPC_RTC
> >>
> >> I also saw references to CONFIG_GEN_RTC_X with Google searches...
> >>
> >> I appreciate if someone explain me when to use each of these kernel
> >> config
> >> options?
> >
> > In the context of 2.4 or 2.6?
>
> 2.4
CONFIG_RTC is the "pc style" rtc driver, which works on a number of
arches, so long as they have a rtc chip found in PCs, and it can be
talked to as such.
GEN_RTC is a generic RTC driver, which offers hooks to the architectures
to do the hw-specific portions. This _could_ be made to work with RTCs
over I2C, but at this time does not.
PPC_RTC is like the above, except it calls the PPC hooks directly, and
is obsolete (and gone in 2.6).
--
Tom Rini
http://gate.crashing.org/~trini/
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-04-06 21:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-06 19:00 Question on RTC options (CONFIG_RTC, CONFIG_GEN_RTC, CONFIG_PPC_RTC) Tolunay Orkun
2004-04-06 20:00 ` Tom Rini
2004-04-06 20:59 ` Tolunay Orkun
2004-04-06 21:14 ` Tom Rini [this message]
2004-04-06 21:23 ` Tolunay Orkun
2004-04-06 21:32 ` Tom Rini
2004-04-06 21:51 ` Tolunay Orkun
2004-04-06 22:02 ` Tom Rini
2004-04-06 23:03 ` Tolunay Orkun
2004-04-06 23:09 ` 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=20040406211439.GD31152@smtp.west.cox.net \
--to=trini@kernel.crashing.org \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=listmember@orkun.us \
/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).