From: Richard Zidlicky <Richard.Zidlicky@stud.informatik.uni-erlangen.de>
To: Tom Rini <trini@kernel.crashing.org>
Cc: Roman Zippel <zippel@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 and PATCH] Move the m68k genrtc driver into 2.5 and use on PPC
Date: Fri, 14 Jun 2002 00:31:43 +0200 [thread overview]
Message-ID: <20020614003143.C1230@linux-m68k.org> (raw)
In-Reply-To: <20020613190646.GT13541@opus.bloom.county>; from trini@kernel.crashing.org on Thu, Jun 13, 2002 at 12:06:46PM -0700
On Thu, Jun 13, 2002 at 12:06:46PM -0700, Tom Rini wrote:
Hi,
> Secondly to the m68k people, does anyone have an objection (or would
> like to do it themselves?) with me trying to get Linus to take the
> changes to include/linux/rtc.h? radeonfb.c currently conflicts with the
> 'pll_info' struct, but Ani Joshi is renaming it.
I will be happy whoever gets it in. The pll_info stuff could be
renamed in genrtc.c as well.
> Also, CONFIG_GEN_RTC
> used to be define_bool'ed to y on CONFIG_SUN3, but I'm not sure if that
> looks nice in a common file. Any idea on how to solve this nicely?
m68k doesn't source drivers/chars/Config.in so just don't do
anything about it?
> diff -Nru a/drivers/char/Config.help b/drivers/char/Config.help
> --- a/drivers/char/Config.help Thu Jun 13 12:03:49 2002
> +++ b/drivers/char/Config.help Thu Jun 13 12:03:49 2002
> @@ -1058,6 +1058,34 @@
> The module is called rtc.o. If you want to compile it as a module,
> say M here and read <file:Documentation/modules.txt>.
>
> +Generic Real Time Clock Support
> +CONFIG_GEN_RTC
> + If you say Y here and create a character special file /dev/rtc with
> + major number 10 and minor number 135 using mknod ("man mknod"), you
> + will get access to the real time clock (or hardware clock) built
> + into your computer.
> +
> + In 2.4 and later kernels this is the only way to set and get rtc
> + time on m68k systems so it is highly recommended.
> +
> + It reports status information via the file /proc/driver/rtc and its
> + behaviour is set by various ioctls on /dev/rtc. If you enable the
> + "extended RTC operation" below it will also provide an emulation
> + for RTC_UIE which is required by some programs and may improve
> + precision in some cases.
> +
> + This driver is also available as a module ( = code which can be
> + inserted in and removed from the running kernel whenever you want).
> + The module is called rtc.o. If you want to compile it as a module,
^^^^^^^
genrtc.o ... I could swear I fixed it in m68k CVS ;)
Richard
WARNING: multiple messages have this Message-ID (diff)
From: Richard Zidlicky <Richard.Zidlicky@stud.informatik.uni-erlangen.de>
To: Tom Rini <trini@kernel.crashing.org>
Cc: Roman Zippel <zippel@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 and PATCH] Move the m68k genrtc driver into 2.5 and use on PPC
Date: Fri, 14 Jun 2002 00:31:43 +0200 [thread overview]
Message-ID: <20020614003143.C1230@linux-m68k.org> (raw)
In-Reply-To: <20020613190646.GT13541@opus.bloom.county>; from trini@kernel.crashing.org on Thu, Jun 13, 2002 at 12:06:46PM -0700
On Thu, Jun 13, 2002 at 12:06:46PM -0700, Tom Rini wrote:
Hi,
> Secondly to the m68k people, does anyone have an objection (or would
> like to do it themselves?) with me trying to get Linus to take the
> changes to include/linux/rtc.h? radeonfb.c currently conflicts with the
> 'pll_info' struct, but Ani Joshi is renaming it.
I will be happy whoever gets it in. The pll_info stuff could be
renamed in genrtc.c as well.
> Also, CONFIG_GEN_RTC
> used to be define_bool'ed to y on CONFIG_SUN3, but I'm not sure if that
> looks nice in a common file. Any idea on how to solve this nicely?
m68k doesn't source drivers/chars/Config.in so just don't do
anything about it?
> diff -Nru a/drivers/char/Config.help b/drivers/char/Config.help
> --- a/drivers/char/Config.help Thu Jun 13 12:03:49 2002
> +++ b/drivers/char/Config.help Thu Jun 13 12:03:49 2002
> @@ -1058,6 +1058,34 @@
> The module is called rtc.o. If you want to compile it as a module,
> say M here and read <file:Documentation/modules.txt>.
>
> +Generic Real Time Clock Support
> +CONFIG_GEN_RTC
> + If you say Y here and create a character special file /dev/rtc with
> + major number 10 and minor number 135 using mknod ("man mknod"), you
> + will get access to the real time clock (or hardware clock) built
> + into your computer.
> +
> + In 2.4 and later kernels this is the only way to set and get rtc
> + time on m68k systems so it is highly recommended.
> +
> + It reports status information via the file /proc/driver/rtc and its
> + behaviour is set by various ioctls on /dev/rtc. If you enable the
> + "extended RTC operation" below it will also provide an emulation
> + for RTC_UIE which is required by some programs and may improve
> + precision in some cases.
> +
> + This driver is also available as a module ( = code which can be
> + inserted in and removed from the running kernel whenever you want).
> + The module is called rtc.o. If you want to compile it as a module,
^^^^^^^
genrtc.o ... I could swear I fixed it in m68k CVS ;)
Richard
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-06-13 22:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-13 19:06 [RFC and PATCH] Move the m68k genrtc driver into 2.5 and use on PPC Tom Rini
2002-06-13 19:06 ` Tom Rini
2002-06-13 22:31 ` Richard Zidlicky [this message]
2002-06-13 22:31 ` Richard Zidlicky
2002-06-14 0:27 ` Tom Rini
2002-06-14 0:27 ` Tom Rini
2002-06-14 8:03 ` Geert Uytterhoeven
2002-06-14 8:03 ` 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=20020614003143.C1230@linux-m68k.org \
--to=richard.zidlicky@stud.informatik.uni-erlangen.de \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linux-mips@oss.sgi.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=trini@kernel.crashing.org \
--cc=zippel@linux-m68k.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.