<snip> > >>> It probably makes sense to add a "has_ir_i2c" field at bttv, add a flag >>> there at modprobe to prevent the autoload, and start tagging the boards >>> with I2C IR with such tag. >> Without having looked into the code, it seems that the driver detects >> the i2c rc already without a board flag. >> Otherwise it wouldn't register the i2c device. Unfortunately, it doesn't >> display a message. > No. In the past (kernel 2.4 and upper), I2C bus used to work with 0-len > reads to scan the used I2C addresses. The I2C drivers like tuners, demods, > IR's etc used to register to the I2C core saying that they were to be used > on TV boards. The I2C logic binds them to the I2C bus driver when they were > detected, during the scanning process. > > That's why it is so hard to know what boards are using I2C remotes, on > those older drivers. Hmmm... so the I2C subystem probes a list of addresses and just registers all devices it finds, but the driver itself doesn't know if one of them is a RC device ? Sounds odd. Will have to check the code to understand what's going on... Regards, Frank -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
