On Wed, Jun 23, 1999 at 01:19:57PM +0100, Steve Jefferies wrote:
> Our company is currently looking at many different RTOS and EOS for our
> embedded system. We are using 80486 processor on a PC104 card.
>
> We need to know the following information about RT Linux so we can make our
> judgement call on which operating system we choose early in July
>
> Here are some of the criteria :-
Most of your criteria are completely irrelevant for RTLinux. Writing
for RTLinux is very similar to writing for a DSP plug-in card -- you
are very close to the hardware, have limited "normal OS" functionality,
and have to be careful how you talk to the "host processor". In the
RTLinux case, you have an extraordinarily fast "DSP" (i.e., PIII 500
and SMP, if you want), and the host processor is the extra CPU cycles
your "DSP" doesn't use.
Before you choose an OS, you need to have in mind what you need in
RT space and non-RT space. Linux supports basically everything you
need in non-RT space. If you need some of these features (like FTP
support) in RT space, you probably have design problems. The questions
you ask suggest that you don't need an RTOS, but just a decent OS.
>
> FTP Support (Server) ?
> SMB Support (Server) ?
> PPP Serial Access (Server) ?
Typical distributions (Red Hat) have all three.
> Ethernet Card Driver Support (NE2000) ?
yes. Linux supports basically all ethernet cards.
> Multi Threaded OS ?
Explain. Do you mean to ask if the OS supports multi-threaded
processes? Then yes. The kernel is not naturally multithreaded,
but that is a design feature that has little relevance to the end
user.
> Multi Threading debug support at source code and assembly levels ?
Don't know. See documentation for gdb.
> Debug sessions controlled via serial, parallel or ethernet to a remote PC ?
yes.
> Thread priority control ?
> Thread switch Times ?
> Dynamic thread creation times ?
Don't know. See thread docs.
> WIN 32 API compliant/compatable or simmilar under different syntax ?
Is this a feature? Why not use a standard interface, like POSIX?
> Sleep accuracies to 1ms ?
Yes.
> Wait for single events ?
> wait for multiple events ?
Yes.
> thread synchronisation controls ?
Don't know. See thread docs.
> Timers available to 1us resolution ?
Yes.
> Interrupt handling support ?
Eh? Of course...
> What prossessor support is there ?
Intel >=386, StrongARM, PowerPC, MIPS, Sparc, others...
RTLinux only runs on intel architecture.
> VGA driver support ?
yes. XFree86 also supports many common accelerated chipsets.
> UART driver support ?
> Keyboard driver support AT and XT ?
yes.
> Support for customer provided devices ?
If you write a driver...
> supports C++ ?
> Templates ?
> C++ exceptions ?
> IOStreams ?
> Namespaces ?
> Jave virtual Machine ?
Yes. As these aren't standardized yet, they may be a little different
than other compilers. See the gcc/ecgs docs.
> COM, DECOM, CORBA ?
Corba, yes. Others, don't know.
> File systems supported ?
Many native Linux filesystems, plus NTFS, FAT, VFAT, NFS, CODA, SMBFS.
> Operation System image size ?
Kernel image is typ 1M for a workstation, actual system footprint
depends on applications. System using 2.0.37 without X runs fine in
8MB with no large applications. 2.2.x has a little bit of trouble.
> Worst case interrupt latency times ?
Depends on tuning. On a system with crappy hardware, can be large. On
a decent system, in the 10's of us. Running RTLinux, typically a few
us.
> 64 bit integer arithmetic support ?
Yes. However, on any 32 bit architecture, it is not native.
> Licensing and Run Time Licensing costs ?
None.
> OS Must be configurable.i.e we can choose which bits be want in it ?
Completely.
> TCP/IP is socket based ?
yes.
dave...
--- [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/
