I presently work in a group that involves creating a hard real-time flight
software controls application. To provide portability and distribution of
objects, Washington Universities ACE/TAO is being used.  The OOD software is
C++ middleware and a user application framework.  For development and
testing purpose we have ported to WinNT and Linux but also have ported to
VXWorks.  A request was made to look into RTLinux.  From my initial
investigation it looks like that RTLinux may not be well suited for our
particular application.  The following statements seem to indicate this:

"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.

Thanks,
Dave Lee
[EMAIL PROTECTED]
-- [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