Wind River's Linux transformation (ZDNet)
Posted May 13, 2005 9:55 UTC (Fri) by
simlo (subscriber, #10866)
In reply to:
Wind River's Linux transformation (ZDNet) by clugstj
Parent article:
Wind River's Linux transformation (ZDNet)
It depends on whichs parts of VxWorks you use. If you use the core, i.e. the
scheduler, I would have no problems with it. It just _works_. If you start
to use all their add-ons: They are crap. The functionality is 95% there so
you think you can use it but once you have deployed your stuff the last 5% starts to hit you and give a lot of trouble.
VxWorks is good for a small, well defined project where you can make an combined OS-application image and burn it into a flash or a prom and skip it with the device. But once you start to do more dynamic stuff like loading an application in the middle of it or just running a lot of different services it sucks compared to Linux. Also the hardware support for common devices lacks in vxWorks compared to Linux.
BUT Linux isn't deterministic real-time although Ingo is working hard on getting it detterministic. But Linux will not obtain the low interrupt and task latencies of vxWorks. Linux will probably get to 50-100 us whereas vxWorks is down to 1-10 us on a typical embedded target.
(
Log in to post comments)