On Fri, 28 Apr 2000, daniel sheltraw wrote:
> I am not sure what you meant by the statement "they are not RT, you can
> allocate memory, etc.". Would you please clarify so that I can be sure I am
> not missing something important.
It was about the code you put in e.g. character device driver in
read/write/open etc. methods. By not being RT I mean:
Can not preempt the Linux kernel.
This means you are in the normal Linux kernel context and you can do all
what all other drivers do. You can for example go to sleep or allocate lots
of memory or ...
The code which is executed as interrupt handler (non RT - can not preempt
kernel when it executed soft cli). is more restricted.
RT code (RT interrupt handlers, RT threads) can in principle use only
services of RT layer.
--
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/