Jose,
I guess you'll need to go to LinuxWorld in August.
I am giving a paper that will cover excatly these points.
The only slight problem compared to VxWorks is the fact that
you cannot make mormal kernel system calls inside the RT process.
Such calls would create things like semaphores , tasks , queues etc.
for a "defined scope" system this should not be a problem.
I have raised this point briefly with Victor and I know he is thinking
about a solution to this problem.
The problem with VxWorks is the need to make features work in a
"standard way".
Since you do not have the source you depend on WindRiver to do it right.
You also depend on them to fix it it it is not right.
In many cases WindRiver have got most things almost right. It is a very
usable system.
I choose RT-Linux because :-
1/ for the non real time needs there is a higher level of "
standardization".
2/ Performance
3/ Reliability
4/ Ease of use
5/ Massive pool of non realtime applications to directly interface to.
Development tools are "on the way" look at www.zentropix.com
There have been several complex applications developed with out such
tools
but they do help.
Cross development ...this is a compiler issue
All you need is a gnu cross. The same holds true for
WindRiver.
Kernel size.
< 3M for full linux + RT but you get FULL LINUX.
I include quite a few tools etc in this
Documentation ... poor at present but the newsgroups make up for it.
Support ... superb from the users
Portability ... poor PPC,ALPHA coming soon but that is it for now.
What do you need intel should do you just fine for PC104.
A final note.
In working with RT Linux I find that the bottleneck is the ISA bus.
For example I can do all the calculations required for a motion
controller in the time
that it takes to do one ISA transaction.(1-2 MicroSecs)
How about this for an idea...
Since RT LINUX is free
do your system design and most of your code under RT Linux to get your
prototype running.
Your entire design can then be simply ported to VxWorks should the need
arise.
MOst of My VxWorks code is prototypes under Linux and then transferred
to VxWorks.
( I am running under Dec Alphas in a VME environment
plans are in the works to move the whole system to RT Linux )
Hope this helps
Phil Wilshire
Jose Antonio Sanchez Valenzuela wrote:
>
> I'm considering the use of RT-Linux or vxWorks on a
> embedded PC104 system. The project deals with a complex
> control and information system. I will have to manage
> several interrupts , serial lines, LCD displays, ethernet,
> memory management, etc.
>
> I notice that vxWorks is expensive but there are several
> points, detailed above, that invite me to discard RT-Linux
> but I am not sure and need more information:
>
> * Development tools. Runtime debugging, interrupt level
> debugging, attaching/deattaching to tasks...
>
> * Cross development. Intel, PowerPC.
>
> * Kernel size. EPROM size
>
> * Documentation and support
>
> * Portability
>
> Could you send me some information about this points or
> some address for get it?
>
> Thank you in advance,
>
> Best Regards,
>
> Jose Antonio
>
> ==================================================
> Jose Antonio Sanchez Valenzuela
> Electronic engineer
> C/Federico Rubio y Gali, 16 4ª D
> 28039 MADRID
> Tel:91 5360491
> ==================================================
> Tu E-Mail Gratis en http://www.olemail.com
> --- [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/
--- [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/
