SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Technology Stocks : Wind River going up, up, up!

 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  
To: JB who wrote (1055)5/13/1997 12:08:00 AM
From: Richard Karpel   of 10309
 
Allen or Dave, in today's release WIND made the point of noting the following:

>>>``It's important that those companies wishing to implement I(2)O understand that this is a software specification. And, as is true of the 'companion' PCI specification, I(2)O is a massive document,'' Shulman added. ``A company that tries to implement I(2)O compliance from scratch will have to devote a lot of time and resources to the effort. Because Wind River has played a significant role in the I(2)O effort from the beginning, we are thoroughly familiar with the spec and will update the IRTOS accordingly to reflect any changes. This effort alone will result in major resource, time and money savings for those companies developing I(2)O-ready products.''<<<

With this statement, WIND seems to be saying, "Yeah, we know that IxWorks isn't your only option, but it beats the hell out of hacking your own I(2)O solution."

This statement appears to be directed at OEMs who may be thinking of writing their own I(2)O. However, while it may be an inefficient allocation of resources for an OEM to hack its own code, it may not be for a company that wants to create an I(2)O product that competes with IxWorks in OEM sales. Am I right about this? Are we likely to see a competitive I2O product?

Also, why is I2O considered an RTOS -- where does the "real time" come into play?
Report TOU ViolationShare This Post
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext