This driver has the following properties compared to the old driver:1. Support for multiple interfaces.2. Interrupt driven I/O as opposed to polling/busy waiting.3. Support for _one_ repeated start (Sr) condition, which is enough for most real-world applications including all SMBus transfer types. (The hardware does not support issuing arbitrary Sr conditions on the bus.)

- This driver is BROKEN because the controller which it uses- will easily trigger RX overrun and TX underrun errors. Using- low I2C clock rates may partially work around those issues- on some systems. Another serious problem is that there is no- documented way to issue repeated START conditions, as needed+ A serious problem is that there is no documented way to issue+ repeated START conditions for more than two messages, as needed to support combined I2C messages. Use the i2c-gpio driver- unless your system can cope with those limitations.+ unless your system can cope with this limitation.