From: Tom Rini <trini@kernel.crashing.org>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: viro@ZenIV.linux.org.uk, "David S. Miller" <davem@davemloft.net>,
torvalds@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Kconfig fix (GEN_RTC dependencies)
Date: Tue, 6 Sep 2005 10:48:18 -0700 [thread overview]
Message-ID: <20050906174818.GB3966@smtp.west.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.61L.0509061109350.6760@blysk.ds.pg.gda.pl>
On Tue, Sep 06, 2005 at 03:40:47PM +0100, Maciej W. Rozycki wrote:
> On Tue, 6 Sep 2005 viro@ZenIV.linux.org.uk wrote:
>
> > >From my reading of that code, GEN_RTC should've been called FAKE_RTC...
>
> Yep, it's an excuse for platform maintainers not to write proper drivers.
I talked with Al about this off list a bit, and pointed out it's
different than it appears. GEN_RTC really is a mostly-generic RTC
driver. There's some fakey stuff going on for UIE (all under
GEN_RTC_X), but the real meat of the driver is common export get/set
time and per-arch (which can abstract further, see ppc32) poke the
hardware for the time. There's 2 (afaik) problems, one being a lack of
alarm support, and the other being hardware access isn't (today)
abstracted out far enough for i2c stuff to work.
Russell King has both of these fixed in the ARM-specific but hardware
poking abstracted rtc driver. I'd like to try and merge things at
somepoint...
--
Tom Rini
http://gate.crashing.org/~trini/
next prev parent reply other threads:[~2005-09-06 17:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-06 0:56 viro
2005-09-06 1:51 ` David S. Miller
2005-09-06 2:24 ` viro
2005-09-06 14:40 ` Maciej W. Rozycki
2005-09-06 17:48 ` Tom Rini [this message]
2005-09-07 18:06 ` Maciej W. Rozycki
2005-09-07 19:42 ` 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=20050906174818.GB3966@smtp.west.cox.net \
--to=trini@kernel.crashing.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@linux-mips.org \
--cc=torvalds@osdl.org \
--cc=viro@ZenIV.linux.org.uk \
/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
all inboxes | Powered by JetHome®