David Olofson wrote:
> > 2. Are all interrupts disabled while a RT-ISR is running as in Linux?
>
> AFAIK, this is the case with the old RTL API, but you can change that
> behavior if you need to.
>
I am a little bit confused about the API. I am using RTL V1.1 for Linux 2.0.
At the moment there is a RTL 1.2 Version for 2.0 Kernel and a RTL V2 for the
2.2 Kernel.
Which one has what API?
>
> > 4. Can I register a RT-ISR within a standard module where nothin else is
> > real time to get a determinism interrupt response time?
>
> Yep. I've done that with standard Linux drivers as a first test of my
> ideas for the Driver Programming Interface. (DPI - see Audiality site,
> downloads.) Keep in mind that you *MUST* use RT safe methods to sync the
> f_ops calls (or whatever) with the RT ISR, or you'll get nasty
> surprises... RTL spin locks and rtl_critical()/rtl_end_critical() works.
> You can also use RT-FIFOs.
what is the definition for RT safe methods? Do you mean Linux system or
kernel calls, which should be RT-safe?
> > 5. If 4, can I call a standard linux system call within a RT-ISR? It is
> > not important for me that the execution of the RT-ISR is fast, but the
> > reaction on the interrupt must be fast.
>
> There are some safe calls, but generally, you can't. RT interrupts DON'T
> get disabled by spin_lock_irqsave() for example... The standard solution
> is throwing some data into a struct or some variables, and triggering a
> standard Linux bottom half handler. (See RT_FIFO code, or rtl_drvsync of
> the DPI.)
I am using a kill_proc() to send a signal to a standard linux user process.
It seems to me to work fine.
S. Heursch
--- [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/
