Re: kernel function called with 200Hz
From: Rich Walker (rw_at_shadow.org.uk)
Date: 05/18/05
- Next message: Ming-Chuan Huang: "kernel thread Vs. softirq"
- Previous message: Josef Moellers: "Re: permission to parport"
- In reply to: Klaus Schneider: "Re: kernel function called with 200Hz"
- Next in thread: Robert Redelmeier: "Re: kernel function called with 200Hz"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Wed, 18 May 2005 14:26:42 +0100
Klaus Schneider <klaus.schneider@iup.uni-heidelberg.de.x> writes:
> I do not need higher resolution than microseconds (at 200Hz, one "tick" is
> 5ms, which is fairy above 1us), but I found on some kernel developer page
> that usleep() does not wait *exactly* the specified time but it is at
> minimum this value; that's why I thought it would not be exact enough. But,
> as 200Hz is not that much for nowadays computers, perhaps I could just give
> it a try and check the signal with an osziloscope.
You should *try* RTAI for your problem. We have found it to be extremely
robust in practice - like, crash Linux and have the hard-real-time RTAI
tasks carry on as the machine falls down around your ears...
cheers, Rich/
-- rich walker | Shadow Robot Company | rw@shadow.org.uk technical director 251 Liverpool Road | need a Hand? London N1 1LX | +UK 20 7700 2487 www.shadow.org.uk/products/newhand.shtml
- Next message: Ming-Chuan Huang: "kernel thread Vs. softirq"
- Previous message: Josef Moellers: "Re: permission to parport"
- In reply to: Klaus Schneider: "Re: kernel function called with 200Hz"
- Next in thread: Robert Redelmeier: "Re: kernel function called with 200Hz"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]