Michael Hunold wrote:
Hi, I don't understand your concerns completely, please be patient with me. Do the MPC8xx and/or IBM4xx platforms already support kernel i2c?
yes.
there is no "mother bus system" where the i2c adapter is attached to, thus you can't use PCI or USB device/vendor ids to determine the hardware config.On 21.09.2004 16:35, Andreas Oberritter wrote:Well, I dislike using "I2C commands" for the following reason: On embedded STBs the I2C bus is usually not bound to a PCI/USB device like in the PC world.Does this matter? It's simply "there" isn't it?
you can't extend the (sometimes proprietary) vendor i2c drivers with your own patches.Why do the frontends drivers have to be cluttered with #ifdefs?then make 8xx-i2c depend on dvb, include the necessary headers and have a lot of knowledge about the 6 different dbox2 frontends and their PLLs *inside* the generic mpc8xx i2c driver.)
No, the knowledge is inside the mpc8xx main driver that handles the kernel i2c callback functions like client_register() (when a client has attached), client_unregister() and the new born command().
You can implement a generic mpc8xx i2c driver that provides the i2c algorithm, then register an i2c_adapter inside the core dbox2 mpc8xx driver which additionally provides the callback functions. (I hope I got this right)
This would mean reimplementing the driver. Holger