diff for duplicates of <3BF15F55.AABB383C@mvista.com> diff --git a/a/1.txt b/N1/1.txt index e78e4ac..946b621 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,9 +1,10 @@ + Richard Zidlicky wrote: > Btw the interrupt need not to be hardware, for the Q40 I test > a rtc register once per jiffie and generate a "soft interrupt". > It could be done generic at least for m68k. -> +> I have written an experiemntal ptimer driver to do just this and potential more. Such a device is useful for real-time programming (e.g., when you try @@ -18,3 +19,5 @@ timer) and RTC operations, my vote for future work is to leave them as two separate drivers. To me, RTC is really just to read/write RTC clock. Jun + +** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/ diff --git a/a/content_digest b/N1/content_digest index 513aabb..e69d6dc 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -13,12 +13,13 @@ " Linux/PPC Development <linuxppc-dev@lists.linuxppc.org>\0" "\00:1\0" "b\0" + "\n" "Richard Zidlicky wrote:\n" "\n" "> Btw the interrupt need not to be hardware, for the Q40 I test\n" "> a rtc register once per jiffie and generate a \"soft interrupt\".\n" "> It could be done generic at least for m68k.\n" - "> \n" + ">\n" "\n" "I have written an experiemntal ptimer driver to do just this and potential\n" "more. Such a device is useful for real-time programming (e.g., when you try\n" @@ -32,6 +33,8 @@ "timer) and RTC operations, my vote for future work is to leave them as two\n" "separate drivers. To me, RTC is really just to read/write RTC clock.\n" "\n" - Jun + "Jun\n" + "\n" + ** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/ -3eadf46cc74166ba93ebaa28dbbaf9d0c5d422dda73a59f0567d9bd08fa753bf +693d0b6df9c9db2672d0819b3ee839d5107201b3e21066d63f9495629b2e75bc
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.