This statement more appropriately describes the real-time portion of applications, not the entire application. Display software and database queries do not often need real-time and under the RTLinux paradigm are best left as Linux tasks. Feel free to contact me at (505) 480-7341 and I can answer any questions for you. } "RTLinux real-time programs should be fast, simple and small" } - Our whole embedded flight software application must run in many real-time } threads. } } "The real-time kernel is itself non-preemptable" } - All our real-time threads have priorities which must be preemptable by } higher priority threads. The objects in the system may be multi-rate and be } required to dynamically changed to a different priority rate they are } dispatched in. } } "Real-Time tasks cannot use Linux system calls or directly call routines or } access ordinary data structures in the Linux kernel" } - Our threads must have full access to system drivers such as the Network } } I would appreciate any comments on the statements made above and any } guidance anyone may have to offer.. -- [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/
