On Mon, 20 Dec 1999, Alex Dubov wrote:

> [EMAIL PROTECTED] wrote:
> > This is not likely for technical reasons.

Victor, could you elaborate on it? What reasons?

>  I solely agree with this too. But my work lies primary in the
> servocontrol areas (with a 10msec tasks). In these areas it is

> > We are moving towards a "debug under pthreads/ run in kspace" functionality.
> >
>  So the whole linux community (with the SGI's kernel debugger). But I
> still insist, that all processing must be done in the user space (in
> accordance with TS systems policy).

So you do not need RTL, you need KURT, or RED-Linux. Both of them need
microsecond resolution timers in the kernel and I will make some efforts
to bring this patch into the official kernel. But for below 100 us latency
RTL (kernel space programming) is the only answer (Linux kernel is not
preemptable by user space tasks, and even if you put in preemption points,
they can not be everywhere).

> Because of some inherent problems in the kernel module mechanism, many
> SC drivers are unable to properly save the context of the respective
> cards, when computer goes to sleep; this renders the use of these cards
> impossible after wake-up, untill a hard reset is performed (of course,

What about write only registers? Making driver to be able to restore any
given config in the middle of any operation is very complex. Much easier
would be just to reload a module, or implelent software reset (config
settings lost from the card, but application may set them again).

--
Tomek


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

Reply via email to