On Sat, Mar 09, 2002 at 05:02:52PM +0100, Der Herr Hofrat wrote:
> > On Fri, 8 Mar 2002 [EMAIL PROTECTED] wrote:
> > > The latencies show up in both the RTLinux scheduling test and the
> > > timer test.
> > 
> > True, but you cannot be sure if it comes from your soft- or hardware.
> > There have also been reported long latencies which come from some weird X
> > or framebuffer activities.

In RTLinux "wierd X" delays are only caused by 
hardware bus locks and there is no framebuffer problem. The scheduler test
shows hardware problems. 

In any case, who cares? Latencies are latencies. The good thing about the RTLinux
scheduler and timer tests are that they show delays that application code will
actually experience. If your robot tosses a 300Kilo steel bar through the 
wall, a "buslock" test that didn't account for such things as a stupid 
hardware design where video memory was put in main memory won't do you much 
good.


-- 
---------------------------------------------------------
Victor Yodaiken 
Finite State Machine Labs: The RTLinux Company.
 www.fsmlabs.com  www.rtlinux.com

-- [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/

Reply via email to