diff for duplicates of <20011114110842.A473@linux-m68k.org> diff --git a/a/1.txt b/N1/1.txt index e88e9ac..dea3cf0 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,26 +1,29 @@ + On Tue, Nov 13, 2001 at 09:58:45AM -0800, Jun Sun wrote: > 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 > to implement a periodic user task). -> +> > See http://linux.junsun.net/realtime-linux/preemption-test -> +> > The driver is architecture independent (i.e., linux-common code) -> +> > Due to the different programming needs behind periodic timers (or user-level > 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. -RTC_UIE is needed (or at least very useful) to set the clock, so it belongs +RTC_UIE is needed (or at least very useful) to set the clock, so it belongs into a rtc driver if it can be implemented. General purpose timers are -different story, btw what is wrong with setitimer that you have chosen +different story, btw what is wrong with setitimer that you have chosen to implement an additional driver for it? Richard + +** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/ diff --git a/a/content_digest b/N1/content_digest index 7dbca06..55c033b 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -14,31 +14,34 @@ " Linux/PPC Development <linuxppc-dev@lists.linuxppc.org>\0" "\00:1\0" "b\0" + "\n" "On Tue, Nov 13, 2001 at 09:58:45AM -0800, Jun Sun wrote:\n" "> Richard Zidlicky wrote:\n" - "> \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" + ">\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" "> to implement a periodic user task).\n" - "> \n" + ">\n" "> See http://linux.junsun.net/realtime-linux/preemption-test\n" - "> \n" + ">\n" "> The driver is architecture independent (i.e., linux-common code)\n" - "> \n" + ">\n" "> Due to the different programming needs behind periodic timers (or user-level\n" "> 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" - "RTC_UIE is needed (or at least very useful) to set the clock, so it belongs \n" + "RTC_UIE is needed (or at least very useful) to set the clock, so it belongs\n" "into a rtc driver if it can be implemented. General purpose timers are\n" - "different story, btw what is wrong with setitimer that you have chosen \n" + "different story, btw what is wrong with setitimer that you have chosen\n" "to implement an additional driver for it?\n" "\n" - Richard + "Richard\n" + "\n" + ** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/ -6eefe6c053f9a8e01c1a913bc80b7c3d78457e77755880a25ec1c844ae810f6e +0708e6040937d5f5da65c4fc22d6f28a3c3d9c6fe8bbfaac047a100c99ab773a
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.