1. Basics
I2O is a hardware device interface.
UDI is a device driver interface.
2. I2O
We know what I2O wants. But hardware needs software in order to be useful and
I2O devices need yet to be accepted and drivers need yet to be written. And
that's on all platforms and for all operating systems. Because that's quite an
effort, I2O needs something like...
3. UDI
UDI can make I2O work. Or it can make I2O die. Or it can force I2O to change.
It all depends on how UDI people relate to I2O people and what UDI people
really want - Drivers For Everyone, or Leverage For The Inner Circle? No matter
what they say, what UDI people really want will be clear the moment UDI specs
are finished.
4. Open source community
Because of its rapidly growing strength, Linux and the open source community
came as an unexpected player into the world domination game. A player that one
cannot afford to ignore though - much less have on the other side of the
barricades.
We appologize for the inconvenience.
5. Dependencies
Dependencies go like this: I2O depends on UDI depends on open source
community. I2O therefore transitively depends on open source community, so
open source community can use UDI as a leverage to get to I2O. This is done by
_insisting_ that UDI conformant hardware either has (a) open source drivers, or
(b) hardware specs available to the public so that an open source driver can be
written (ie no NDAs and shit like that).
Andrej
-- Andrej Presern, andrejp@luz.fe.uni-lj.si- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/