diff for duplicates of <3BF01F6F.D64CEA50@mvista.com> diff --git a/a/1.txt b/N1/1.txt index 951f580..f04106b 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,13 +1,14 @@ + "Maciej W. Rozycki" wrote: -> +> > On Mon, 12 Nov 2001, Jun Sun wrote: -> +> > > The /dev/rtc interface is highly influenced by MC146818 chip, which not all > > RTC devices are alike. The only fundamental thing in the driver is really the > > read and write time. -> +> > You need only to keep the interface, which is: -> +> > static struct file_operations rtc_fops = { > owner: THIS_MODULE, > llseek: no_llseek, @@ -20,20 +21,20 @@ > release: rtc_release, > fasync: rtc_fasync, > }; -> +> > Of these you probably must only implement open() and ioctl() -- you may > provide others as hardware permits -- see how these functions are > implemented in drivers/char/rtc.c. The interface is pretty generic, IMHO. -> +> > > If their abstraction is reasonable, perhaps they can all converge to a better, > > more generic rtc interface. -> +> > Just implement the ioctls given hardware permits and return -EINVAL for > others. Again, they are pretty generic: get/set the time, alarm, epoch, > disable/enable various interrupts, etc. -- see include/linux/rtc.h. You > may propose additional ioctls if they would be useful for particular > hardware. -> +> Basically agree. @@ -46,3 +47,5 @@ hardware routines, especially anything beyond rtc_read_time() and rt_write_time(). Jun + +** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/ diff --git a/a/content_digest b/N1/content_digest index c6ab183..2b5ec08 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -9,16 +9,17 @@ " Linux/PPC Development <linuxppc-dev@lists.linuxppc.org>\0" "\00:1\0" "b\0" + "\n" "\"Maciej W. Rozycki\" wrote:\n" - "> \n" + ">\n" "> On Mon, 12 Nov 2001, Jun Sun wrote:\n" - "> \n" + ">\n" "> > The /dev/rtc interface is highly influenced by MC146818 chip, which not all\n" "> > RTC devices are alike. The only fundamental thing in the driver is really the\n" "> > read and write time.\n" - "> \n" + ">\n" "> You need only to keep the interface, which is:\n" - "> \n" + ">\n" "> static struct file_operations rtc_fops = {\n" "> owner: THIS_MODULE,\n" "> llseek: no_llseek,\n" @@ -31,20 +32,20 @@ "> release: rtc_release,\n" "> fasync: rtc_fasync,\n" "> };\n" - "> \n" + ">\n" "> Of these you probably must only implement open() and ioctl() -- you may\n" "> provide others as hardware permits -- see how these functions are\n" "> implemented in drivers/char/rtc.c. The interface is pretty generic, IMHO.\n" - "> \n" + ">\n" "> > If their abstraction is reasonable, perhaps they can all converge to a better,\n" "> > more generic rtc interface.\n" - "> \n" + ">\n" "> Just implement the ioctls given hardware permits and return -EINVAL for\n" "> others. Again, they are pretty generic: get/set the time, alarm, epoch,\n" "> disable/enable various interrupts, etc. -- see include/linux/rtc.h. You\n" "> may propose additional ioctls if they would be useful for particular\n" "> hardware.\n" - "> \n" + ">\n" "\n" "Basically agree.\n" "\n" @@ -56,6 +57,8 @@ "hardware routines, especially anything beyond rtc_read_time() and\n" "rt_write_time().\n" "\n" - Jun + "Jun\n" + "\n" + ** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/ -950ea9ac3fd394cf98e93344043e68c7637b32c7d049ccd64625957785612dda +b1c611edfa401fccd256d51ab61516f6e4377effbc312c75ac9a1de10e5e42c9
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.