Karim Yaghmour wrote:
>
> In the fix I've done, rather than reading the latched value of
> timer 0, the TSC is used to update the time (yes, this is only for
> Pentium machines, I don't have any other type of machine and don't
> have the time to do the tests even if I had one). We assume (correctly)
> that RTAI doesn't write into the TSC. Therefore, whatever value is
> in there reflects the machine's behavior.
>
Actually the latched value is used to set the delay_at_last_interrupt
variable which should be commented out wherever used. Most importantly
in do_fast_gettimeoffset. And, to be more acurate than the above
paragraph, the TSC is actually used to update time, not just the latched
timer, but it isn't used correctly in the context of RTAI's behavior.
The suggested fix corrects this.
Incidently, this solves problems I had with KDE reacting way too
fast when runing RTAI. Now I can double-click on my e-mail without having
to be faster that 50micro-seconds :)
===================================================
Karim Yaghmour
[EMAIL PROTECTED]
Operating System Consultant
(Linux kernel, real-time and distributed systems)
===================================================
-- [rtl] ---
To unsubscribe:
echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR
echo "unsubscribe rtl <Your_email>" | mail [EMAIL PROTECTED]
---
For more information on Real-Time Linux see:
http://www.rtlinux.org/rtlinux/
