From: Jun Sun <jsun@mvista.com>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Linux/MIPS Development <linux-mips@oss.sgi.com>,
Linux/m68k <linux-m68k@lists.linux-m68k.org>,
Linux/PPC Development <linuxppc-dev@lists.linuxppc.org>
Subject: Re: [RFC] generic MIPS RTC driver
Date: Mon, 12 Nov 2001 10:24:35 -0800 [thread overview]
Message-ID: <3BF013E3.52F45AE9@mvista.com> (raw)
In-Reply-To: Pine.GSO.3.96.1011112142501.24771K-100000@delta.ds2.pg.gda.pl
"Maciej W. Rozycki" wrote:
>
> On Mon, 12 Nov 2001, Geert Uytterhoeven wrote:
>
> > > Unless you use a non-MC146818 RTC, which you need to write a separate
> > > driver for anyway.
> >
> > Yep, so that's why both m68k and PPC have common routines to read/write the
> > RTC, with a /dev/rtc-compatible abstraction on top of it.
>
> OK, then you need an RTC chipset-specific driver and not a CPU
> architecture-specific one.
You *can* write a chip specific driver in addition to this generic one if you
want. Presumably the chip-specific one provides more operations than just
read/write date.
> Otherwise we'll end with a zillion of similar
> RTC drivers like we already have for LANCE and SCC chips.
>
Don't quite understand this statement.
If everybody uses the generic rtc driver, there will be only one copy of it.
It will prevent zillions copies of similar thing.
Note that hardware specifics are already abstracted by rtc_set_time() and
rtc_get_time() routines. The generic RTC driver makes use of them and has no
RTC chip or machine dependent code.
Jun
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-11-12 18:24 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20011110231746.B4342@mvista.com>
2001-11-11 10:14 ` [RFC] generic MIPS RTC driver Geert Uytterhoeven
2001-11-12 12:59 ` Maciej W. Rozycki
2001-11-12 13:11 ` Geert Uytterhoeven
2001-11-12 13:29 ` Maciej W. Rozycki
2001-11-12 16:14 ` Pete Popov
2001-11-12 18:26 ` Jun Sun
2001-11-12 18:56 ` Jun Sun
2001-11-12 21:51 ` Tom Rini
2001-11-12 18:24 ` Jun Sun [this message]
2001-11-12 19:04 ` Maciej W. Rozycki
2001-11-12 19:21 ` Jun Sun
2001-11-12 18:19 ` Jun Sun
2001-11-12 18:55 ` Maciej W. Rozycki
2001-11-12 19:13 ` Jun Sun
2001-11-12 20:02 ` Geert Uytterhoeven
2001-11-12 20:54 ` Roman Zippel
2001-11-13 1:31 ` Tom Rini
2001-11-13 6:20 ` Geert Uytterhoeven
2001-11-13 14:44 ` Tom Rini
2001-11-13 14:47 ` Geert Uytterhoeven
2001-11-13 15:30 ` Roman Zippel
2001-11-13 13:42 ` Richard Zidlicky
2001-11-13 15:32 ` Roman Zippel
2001-11-14 9:46 ` Richard Zidlicky
2001-11-13 17:58 ` Jun Sun
2001-11-14 10:08 ` Richard Zidlicky
2001-11-15 17:41 ` Jun Sun
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=3BF013E3.52F45AE9@mvista.com \
--to=jsun@mvista.com \
--cc=geert@linux-m68k.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linux-mips@oss.sgi.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=macro@ds2.pg.gda.pl \
/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).