diff for duplicates of <3BF013E3.52F45AE9@mvista.com> diff --git a/a/1.txt b/N1/1.txt index e6e789a..23692d3 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,15 +1,16 @@ + "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. +> 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 @@ -21,7 +22,7 @@ read/write date. Don't quite understand this statement. -If everybody uses the generic rtc driver, there will be only one copy of it. +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 @@ -29,3 +30,5 @@ 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/ diff --git a/a/content_digest b/N1/content_digest index cabd5ac..12a0339 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -9,18 +9,19 @@ " 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, Geert Uytterhoeven wrote:\n" - "> \n" + ">\n" "> > > Unless you use a non-MC146818 RTC, which you need to write a separate\n" "> > > driver for anyway.\n" "> >\n" "> > Yep, so that's why both m68k and PPC have common routines to read/write the\n" "> > RTC, with a /dev/rtc-compatible abstraction on top of it.\n" - "> \n" + ">\n" "> OK, then you need an RTC chipset-specific driver and not a CPU\n" - "> architecture-specific one. \n" + "> architecture-specific one.\n" "\n" "You *can* write a chip specific driver in addition to this generic one if you\n" "want. Presumably the chip-specific one provides more operations than just\n" @@ -32,13 +33,15 @@ "\n" "Don't quite understand this statement.\n" "\n" - "If everybody uses the generic rtc driver, there will be only one copy of it. \n" + "If everybody uses the generic rtc driver, there will be only one copy of it.\n" "It will prevent zillions copies of similar thing.\n" "\n" "Note that hardware specifics are already abstracted by rtc_set_time() and\n" "rtc_get_time() routines. The generic RTC driver makes use of them and has no\n" "RTC chip or machine dependent code.\n" "\n" - Jun + "Jun\n" + "\n" + ** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/ -3459bfa049ecfdc294d3aa8584792f063840a42130530c61ee0e2cc396c111de +6114ea7a0183dc6b2db81545e5614b43e398ea968e4d21e4b91d5c1c5dfd0cc9
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.