Wind River Completes Embedded Linux Metamorphosis
An anonymous reader writes "Embedded software powerhouse Wind River's metamorphosis into an embedded Linux vendor appears to be complete. The company will announce today that it is shipping a pre-release version of its first embedded Linux distribution, and that it has already delivered 1,000 "developer seats" for the Carrier Grade Linux 2.0 compliant software."
I wouldn't say their "metamorphosis", if they ever purported to want or aim to do such a thing, is complete - I mean they are still selling VxWorks right? I believe the top four platforms on their Product Directory are based on VxWorks, not Linux. I think they can fairly be described as an embedded software vendor that supplies Linux platforms, rather than an "embedded Linux vendor".
-- Nothing unusual happened today
I think Wind River is making a smart move. They could have easily dug their heels in and raged against the Linux tide. Instead they're going with the flow and building to take advantage of new opportunities and serving their customers' needs. Good show!
To the making of books there is no end, so let's get started
The Market thinks they are turning it around.
Less geeky Stock Talk chat here.
...but is Linux really the platform for hard real-time embedded control? I like Linux as much as the next /.er, but it's not the ultimate solution for everything. VxWorks does something very different to most Linux boxes. Let's keep some variety in the world, so we can choose the tool for the job.
Wind River DID NOT do the Mars Rover software. JPL did. JPL only used Vxworks as the OS. Any mature real time OS would have worked. JPL did the hard part.
Same here.
...
I joined a team working on functionality running on an embedded Linux distribution about a year ago. After doing major cleanup in the sources, including an upgrade to the newest release of the embedded distribution; I started looking under the hood.
Several portions of the distributions were replaced by busybox, uclibc and a gcc-3.4 based toolchain. In the process, we built our own Perl based build system (with CVS): we check in/out only the modified files (basically only platform files) and use the original tarballs (tar xkfj).
As a result, we were able to decrease the embedded compressed filesystem to less than 33%, our code is much closer to the upstream developments (e.g. for network drivers, this can be an issue) and our system is modular and flexible. (btw, size does matter in production and for field upgrades): smaller, faster and cleaner...
I am currently in the process of cleaning up the platform dependent files for release and inclusion into the upstream projects (hopefully they get accepted).
We moved away and have not looked back and saved over 25,000 Euros per year (and rising) in the process. Yes, the embedded distributions are terribly expensive. If you have money to spare, consider hiring teams from the companies selling expertise and releasing the code like http://www.denx.de/, http://www.codepoet.org/, http://www.pengutronix.de/, http://www.mind.be/,
Genius doesn't work on an assembly line basis. You can't simply say, "Today I will be brilliant."
Besides, this story is about WindRiver adding Linux to its lineup, not replacing VxWorks.