Open main menu
Home
Random
Recent changes
Special pages
Community portal
Preferences
About Wikipedia
Disclaimers
Incubator escapee wiki
Search
User menu
Talk
Dark mode
Contributions
Create account
Log in
Editing
I2O
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
{{about||the chemical|Diiodine oxide|the automobile|Hyundai i20}} {{Multiple issues| {{more footnotes|date=February 2015}} {{primary sources|date=February 2015}} }} '''Intelligent Input/Output''' ('''I2O''') is a defunct computer input/output (I/O) specification. I2O was originally designed to make use of the [[Intel i960]] microprocessor as the I/O offload engine, bringing [[channel I/O]] to the PC. I2O emerged from [[Intel]] in the mid 1990s with the publication of the I2O specification in 1996 by the Intelligent I/O [[Special Interest Group]], which dissolved as of 13 October 2000.<ref>[https://web.archive.org/web/20010502171128/http://www.intelligent-io.com/ I2O SIG]</ref> I2O's principal architectural components included the I/O processor (IOP) and a split device driver model, with an OSM (OS Module) running in the host operating system and a HDM (Hardware Device Module) running on the I/O processor. This formally separated OS-specific driver functionality from the underlying device, and the two software components used message passing for communications. This split is suggestive of another initiative in which Intel participated at the time, the [[Uniform Driver Interface]] (UDI), which sought to establish a common device driver interface spanning multiple software platforms. I2O was plagued by several problems: the i960 was largely a failure and I2O made systems more expensive in a low cost marketplace. Additionally, the I2O SIG was seen as hostile to open source and insensitive to small players because it charged high fees for participation and was dominated by a few corporate players, notably Microsoft. While it remains unclear which of these factors caused the ultimate failure of I2O, only a few server class machines were ever built with onboard I2O. The I2O-SIG disbanded in October 2000, with a small amount of architectural information being made available via FTP at about the same time. A number of x86-compatible operating systems provided support (or still do) for I2O, including [[Windows (operating system)|Windows]], [[Linux]] (removed in 4.0<ref>[https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=2cbf7fe2d5d32a4747c1f8ad163e886dccad930c removal commit], [https://lwn.net/Articles/633416/ coverage]</ref>), [[Solaris (operating system)|Solaris]], [[OpenBSD]], and [[NetWare]]. ==Examples of systems which utilized I2O== * [[Compaq Proliant]] * [[HP NetServer LH3000]] * [[Dell PowerEdge|PERC]] 4 DC SCSI/i20 on Dell [[PowerEdge]] * [[NEC]] Express5800 ==References== {{Reflist}} ==External links== * [https://web.archive.org/web/20060513124134/http://docsrv.sco.com/HDK_concepts/ddT_I2O.html sco.com - I<sub>2</sub>0] * [http://www.intel.com/design/servers/dev_guides/content/doc_lib/udi_wp.htm intel.com - UDI and I<sub>2</sub>O: Complementary Approaches to Portable, High-performance I/O] * [https://web.archive.org/web/20020526140758/http://intelligent-io.com/ intelligent-io.com] from the [[Internet Archive]] * [http://archive.wired.com/science/discoveries/news/1997/07/5343 wired.com - Consortium segregates the bus] {{DEFAULTSORT:I2o}} [[Category:Input/output]]
Edit summary
(Briefly describe your changes)
By publishing changes, you agree to the
Terms of Use
, and you irrevocably agree to release your contribution under the
CC BY-SA 4.0 License
and the
GFDL
. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel
Editing help
(opens in new window)
Pages transcluded onto the current version of this page
(
help
)
:
Template:About
(
edit
)
Template:Multiple issues
(
edit
)
Template:Reflist
(
edit
)