From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.3/8.12.3) with ESMTP id g5DMkmnC007287 for ; Thu, 13 Jun 2002 15:46:48 -0700 Received: (from majordomo@localhost) by oss.sgi.com (8.12.3/8.12.3/Submit) id g5DMkmBL007286 for linux-mips-outgoing; Thu, 13 Jun 2002 15:46:48 -0700 X-Authentication-Warning: oss.sgi.com: majordomo set sender to owner-linux-mips@oss.sgi.com using -f Received: from faui02.informatik.uni-erlangen.de (root@faui02.informatik.uni-erlangen.de [131.188.30.102]) by oss.sgi.com (8.12.3/8.12.3) with SMTP id g5DMkenC007280 for ; Thu, 13 Jun 2002 15:46:41 -0700 Received: from rz.de (root@faui02b.informatik.uni-erlangen.de [131.188.30.151]) by faui02.informatik.uni-erlangen.de (8.9.1/8.1.16-FAU) with ESMTP id AAA03684; Fri, 14 Jun 2002 00:48:53 +0200 (MEST) Received: (from rz@localhost) by rz.de (8.8.8/8.8.8) id AAA01325; Fri, 14 Jun 2002 00:31:43 +0200 Date: Fri, 14 Jun 2002 00:31:43 +0200 From: Richard Zidlicky To: Tom Rini Cc: Roman Zippel , Linux/MIPS Development , Linux/m68k , Linux/PPC Development Subject: Re: [RFC and PATCH] Move the m68k genrtc driver into 2.5 and use on PPC Message-ID: <20020614003143.C1230@linux-m68k.org> References: <20020613190646.GT13541@opus.bloom.county> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20020613190646.GT13541@opus.bloom.county>; from trini@kernel.crashing.org on Thu, Jun 13, 2002 at 12:06:46PM -0700 Sender: owner-linux-mips@oss.sgi.com Precedence: bulk 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 . > > +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 From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Fri, 14 Jun 2002 00:31:43 +0200 From: Richard Zidlicky To: Tom Rini Cc: Roman Zippel , Linux/MIPS Development , Linux/m68k , Linux/PPC Development Subject: Re: [RFC and PATCH] Move the m68k genrtc driver into 2.5 and use on PPC Message-ID: <20020614003143.C1230@linux-m68k.org> References: <20020613190646.GT13541@opus.bloom.county> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <20020613190646.GT13541@opus.bloom.county>; from trini@kernel.crashing.org on Thu, Jun 13, 2002 at 12:06:46PM -0700 Sender: owner-linuxppc-dev@lists.linuxppc.org List-Id: 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 . > > +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/