> > > // msp34xx: init: chip=MSP3450G-B6, has NICAM support > > > // but then only: chip reset failed, penguin on i2c bus? > > > > Might be that they use the same trick as Hauppauge: connect the msp3400 > > reset pin to one of the gpio pins. If you get the gpio wrong then, it > > might be that the reset line is permanently active and thus the > > communication with the chip failes for obvious reasons ... > > No, as MSP responds properly (by sending it's model id etc) it is not > in the munge-i2c-bus state. Yes. > (With reset line active the chip should not affect i2c). It will not corrupt all bus activity, but it also not respond to any read/write requests to its address (which will cause the "penguin on i2c bus" message, that printk is in the msp3400 module). The above might happen if the reset line is _not_ active at initialization time, but gets enabled later (which then deactivates the msp3400). Gerd -- Damn lot people confuse usability and eye-candy.
