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: Boplicity who wrote (1974)9/10/1997 6:21:00 PM
From: Allen Benn   of 10309
 
>Why does a BIOS company have to go through WIND for emulation library?

Sorry for the miscommunication. I didn't mean to suggest they would need to. I2O is an open standard, so just about anybody is free to code their own emulation library of routines. In particular, WIND could decide to do it themselves, but I doubt if they would be interested. On the other hand, it is a natural for BIOS companies.

I see BIOS companies now having to support two flavors of I/O drivers: legacy and I2O. That means they need to add the I2O flavor for existing peripherals, where they already have legacy software so they can take advantage of I2O. That is what they are probably spending nights doing now.

But what happens in the future when new devices come along, and device software is needed for them? Why write and test two flavors of software, especially when testing the legacy approach is made difficult and expensive trying to cope with potential incompatibility problems with other devices that may or may not be connected to a computer. An alternative is to write only the I2O flavor, and include I2O emulation software that will enable the device(s) to execute properly in all computers, including those that lack I2O. Since the emulated I2O need only support the device(s) in question, probably only a subset of I2O need be implemented by the BIOS company.

Allen
Report TOU ViolationShare This Post
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext