Lesson plan
I2O
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. 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.…
Article summary
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. 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.…
Key claims
No claims recorded.
Discussion questions
- Summarise the article in your own words. Which single claim would you verify first, and why?
- Which claim in this article is most likely to be revised as the sources update? How would you check its current status?
- If two sources disagreed about one of these facts, what would you need in order to trust one over the other?
Bibliography
No sources recorded.
Key claims and bibliography are generated from the same tracked claims and sources as the article page.