Hi Oldrich, On Thu, 9 Apr 2009 21:15:30 +0200, Oldrich Jedlicka wrote: > I've tried your patches with AverMedia Cardbus Hybrid (E506R) and they works > fine. Thanks for testing and reporting, and sorry for the late answer. > My current experience with AverMedia's IR chip (I don't know which one is on > the card) is that I2C probing didn't find anything, but it got the chip into > some strange state - next operation failed (so that the autodetection on > address 0x40 and "subaddress" 0x0b/0x0d failed). OK, that makes sense. Many I2C devices only support a limited subset of the I2C protocol, and if you try to address them with a message format they don't support, their state machine goes into a bad state. That's probably what was happening there. This is the reason why we should always instantiate I2C devices explicitly when possible: whatever probing method you use, you have no guarantee that every device will like it. > The chip at address 0x40 needs the write first (one byte: 0x0b or 0x0d) and > immediate read, otherwise it would not respond. The saa7134's I2C 0xfd quirk > (actually I would call it a hack :-)) caused failures in communication with > the IR chip. I didn't know about this hack. The implementation choice seems wrong to me. The hack should be triggered only when needed, rather than by default with an exception for address 0x40. This goes beyond the scope of my patch though, and I don't want to touch that kind of code without hardware at hand to test my changes. > The way I'm doing the IR reading is the same as the Windows driver does - I > got the information through the Qemu with pci-proxy patch applied. Thanks, -- Jean Delvare -- 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
