On Wednesday 21 July 2004 14:18, Holger Waechtler wrote: > I have to admit that I didn't felt the urge to use this yet, but at a > first glance over the API everything looks good, pretty cleanly > implemented and provides all the power management and hotplug features > the current dvb_i2c and the kernel i2c API are still missing.
Power management is provided through the dvb driver, and do you really need to hotplug a frontend? > If implemented in a wrapper API pretty similiar to dvb_i2c.[ch] then the > driver even don't need to know anything about the device/bus API. HU? What's the point of beeing able to use a i2c device on another bus type? > > Theoretically, the kernel I2C layer provides exactly the same behavior as > > the old dvb_i2c layer, with added features. Who says we can't > > mimic/emulate another bus type on I2C as long as the drivers are aware of > > the protocol in use on the adapter. > > you are kidding, are you? Basically this is what you want, no? Kenneth
