diff for duplicates of <3BF012CA.287A76A@mvista.com> diff --git a/a/1.txt b/N1/1.txt index ace8b61..4b15ce6 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,5 +1,6 @@ + Geert Uytterhoeven wrote: -> +> > On Mon, 12 Nov 2001, Maciej W. Rozycki wrote: > > On Sun, 11 Nov 2001, Geert Uytterhoeven wrote: > > > > In other words, with such a driver, once you implemented rtc_get_time() @@ -17,19 +18,19 @@ Geert Uytterhoeven wrote: > > > - On MIPS, we now have your drivers/char/mips_rtc.c. > > > > Agreed, what's wrong with drivers/char/rtc.c? It even works for the -> +> > It's for MC146818 RTCs only. -> +> > > DECstation which maps its RTC in an unusual (but nice) way -- it's just a > > matter of initializing rtc_ops appropriately. See arch/mips/dec/rtc-dec.c > > for an example. > > > > 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. -> +> Geert, what is the abstraction they used? @@ -41,3 +42,5 @@ If their abstraction is reasonable, perhaps they can all converge to a better, more generic rtc interface. Jun + +** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/ diff --git a/a/content_digest b/N1/content_digest index 4794a10..4976dd2 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -9,8 +9,9 @@ " Linux/PPC Development <linuxppc-dev@lists.linuxppc.org>\0" "\00:1\0" "b\0" + "\n" "Geert Uytterhoeven wrote:\n" - "> \n" + ">\n" "> On Mon, 12 Nov 2001, Maciej W. Rozycki wrote:\n" "> > On Sun, 11 Nov 2001, Geert Uytterhoeven wrote:\n" "> > > > In other words, with such a driver, once you implemented rtc_get_time()\n" @@ -28,19 +29,19 @@ "> > > - On MIPS, we now have your drivers/char/mips_rtc.c.\n" "> >\n" "> > Agreed, what's wrong with drivers/char/rtc.c? It even works for the\n" - "> \n" + ">\n" "> It's for MC146818 RTCs only.\n" - "> \n" + ">\n" "> > DECstation which maps its RTC in an unusual (but nice) way -- it's just a\n" "> > matter of initializing rtc_ops appropriately. See arch/mips/dec/rtc-dec.c\n" "> > for an example.\n" "> >\n" "> > Unless you use a non-MC146818 RTC, which you need to write a separate\n" "> > driver for anyway.\n" - "> \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" "\n" "Geert, what is the abstraction they used?\n" "\n" @@ -51,6 +52,8 @@ "If their abstraction is reasonable, perhaps they can all converge to a better,\n" "more generic rtc interface.\n" "\n" - Jun + "Jun\n" + "\n" + ** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/ -d00059dacb169b82347d99e8482b988e283fd6f946d6637bb3cf1924be016bbc +bab410ec59477d5f5fc4d9e79405fa5a73aec8621eae2890b184caceacf5c8be
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.