From: Richard Zidlicky <rz@linux-m68k.org>
To: Helge Deller <deller@gmx.de>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
parisc-linux@parisc-linux.org,
Linux/PPC Development <linuxppc-dev@lists.linuxppc.org>,
Linux/m68k <linux-m68k@lists.linux-m68k.org>
Subject: [parisc-linux] Re: Generic RTC driver in 2.4.x
Date: Sun, 12 Jan 2003 22:49:08 +0100 [thread overview]
Message-ID: <20030112224908.A618@linux-m68k.org> (raw)
In-Reply-To: <200301121333.17077.deller@gmx.de>; from deller@gmx.de on Sun, Jan 12, 2003 at 01:35:33PM +0100
On Sun, Jan 12, 2003 at 01:35:33PM +0100, Helge Deller wrote:
> > BTW, perhaps we should move the global RTC_* definitions in <asm/rtc.h> to
> > <linux/genrtc.h>, or merge them with the ones in <linux/mc146818rtc.h> and
> > move them to <linux/rtc.h>?
>
> IMHO leaving them architecture specific in <asm/rtc.h> seems best to me, and it
> leaves the most possibilities to make them later more dependend on the hardware.
in genrtc the RTC_* defs should be used only for interface definition,
unlike rtc.c where they are 1:1 with some obscure bits in the rtc chip
and also happen to be the interface..
It would make sense to merge them into <linux/rtc.h>, whether it is
a good idea to do it in 2.4 is another question.
Stuff that is really hw dependent should use different naming (and stay
in asm/rtc.h of course).
Richard
WARNING: multiple messages have this Message-ID (diff)
From: Richard Zidlicky <rz@linux-m68k.org>
To: Helge Deller <deller@gmx.de>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
parisc-linux@parisc-linux.org,
Linux/PPC Development <linuxppc-dev@lists.linuxppc.org>,
Linux/m68k <linux-m68k@lists.linux-m68k.org>
Subject: Re: Generic RTC driver in 2.4.x
Date: Sun, 12 Jan 2003 22:49:08 +0100 [thread overview]
Message-ID: <20030112224908.A618@linux-m68k.org> (raw)
In-Reply-To: <200301121333.17077.deller@gmx.de>; from deller@gmx.de on Sun, Jan 12, 2003 at 01:35:33PM +0100
On Sun, Jan 12, 2003 at 01:35:33PM +0100, Helge Deller wrote:
> > BTW, perhaps we should move the global RTC_* definitions in <asm/rtc.h> to
> > <linux/genrtc.h>, or merge them with the ones in <linux/mc146818rtc.h> and
> > move them to <linux/rtc.h>?
>
> IMHO leaving them architecture specific in <asm/rtc.h> seems best to me, and it
> leaves the most possibilities to make them later more dependend on the hardware.
in genrtc the RTC_* defs should be used only for interface definition,
unlike rtc.c where they are 1:1 with some obscure bits in the rtc chip
and also happen to be the interface..
It would make sense to merge them into <linux/rtc.h>, whether it is
a good idea to do it in 2.4 is another question.
Stuff that is really hw dependent should use different naming (and stay
in asm/rtc.h of course).
Richard
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-01-12 22:27 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-24 13:55 [parisc-linux] Generic RTC driver in 2.4.x? Geert Uytterhoeven
2002-12-24 13:55 ` Geert Uytterhoeven
2002-12-24 23:51 ` [parisc-linux] " Randolph Chung
2002-12-24 23:51 ` Randolph Chung
2002-12-26 17:55 ` Tom Rini
2002-12-26 17:55 ` Tom Rini
2002-12-28 22:37 ` Geert Uytterhoeven
2002-12-28 22:37 ` Geert Uytterhoeven
2003-01-05 14:44 ` Geert Uytterhoeven
2003-01-05 14:44 ` Geert Uytterhoeven
2003-01-10 20:05 ` [parisc-linux] Generic RTC driver in 2.4.x Geert Uytterhoeven
2003-01-10 20:05 ` Geert Uytterhoeven
2003-01-10 20:05 ` Geert Uytterhoeven
2003-01-11 19:50 ` [parisc-linux] " Helge Deller
2003-01-12 11:33 ` Geert Uytterhoeven
2003-01-12 11:33 ` Geert Uytterhoeven
2003-01-12 11:33 ` Geert Uytterhoeven
2003-01-12 12:35 ` [parisc-linux] " Helge Deller
2003-01-12 12:35 ` Helge Deller
2003-01-12 21:49 ` [parisc-linux] " Richard Zidlicky
2003-01-12 21:49 ` Richard Zidlicky [this message]
2003-01-12 21:49 ` Richard Zidlicky
2003-01-12 12:35 ` [parisc-linux] " Helge Deller
2003-01-30 18:03 ` Tom Rini
2003-01-30 18:03 ` Tom Rini
2003-01-30 18:03 ` Tom Rini
2003-01-31 17:43 ` [parisc-linux] " Geert Uytterhoeven
2003-01-31 17:43 ` Geert Uytterhoeven
2003-01-31 17:43 ` Geert Uytterhoeven
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=20030112224908.A618@linux-m68k.org \
--to=rz@linux-m68k.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=deller@gmx.de \
--cc=geert@linux-m68k.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=parisc-linux@parisc-linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.