On Fri, Jun 16, 2000 at 11:09:37AM +0200, Arnaud Westenberg wrote:
> Hi all,
>
> Sorry for the long mail, but as you probably already noticed I'm just
> starting with RTLinux.
>
> I have the next problem:
>
> I've written a driver of wich I only need the irq-handler to be RT. The
> handler reeds data from the hardware and puts it in a kernel buffer. The
> kernel read call, reads the data from the buffer and copies it to
> userspace.
>
> I have assumed there's no problem for the RT irq-handler to work with
> shared kernel memory allocated at open time of the device with vmalloc.
> Is this correct?
>
> The buffer is circular and I'm using the following code:
>
Why don't you just use the rtfifo interface? Is is not adequate for some reason?
> Does a "hard" handler stop a RT thread? (I would say yes) How are the
> "priorities" between hard handlers and RT threads determined by RTLinux?
Hard handlers preempt anything that is not running with hard interrupts disabled.
There is no other priority mechanism.
> question:
> It takes a verry long time before I receive my own messages from the
> list (~45 min.) is it normal?
Yes.
-- [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/
