--- gert.vervoort@xxxxxxxxx wrote: > > > > > At the moment I don't have any tech docs to help > me > > out at all here. Has anyone developed an i2c > sniffer > > for Win32 I can use to help me along? > > > > In the bttv-0.7 package there is a tool, called > "detect", which uses the I2C userspace device to > scan the I2C bus for attached devices. Perhaps this > can be of help in order to see if your remote is I2C > of gpio attached to the SAA7134. > > If you scan the I2C bus with this tool, you will > find a tuner. And if there is a I2C based remote, > this will show up in the list of I2C devices > attached to the I2C bus of you SAA7134. > > Example: > > [vervoort@pc6475 tools]$ ./detect > 0x40: ??? > 0x76: ??? > 0xc0: tuner (error: Device or resource busy) > [vervoort@pc6475 tools]$ > > In this case I find a tuner on addres 0xC0, an > SAA6752 MPEG-2 encoder on addres 0x40 and an I2C I/O > expander on addres 0x76. > > Gert > Ran the tool and got the following. # ./detect 0xa0: eeprom (bt878, Hauppauge-848) 0xc2: tuner (error: Device or resource busy) Also tried modprobe saa7134 i2c_debug=1 i2c_scan=1 Which probed the i2c bus and only found the same two devices. Hence it looks like the remote is accessed via GPIO rather than i2c.. Any ideas of where to go from here at the saa7134 driver doesn't have the same gpio controls at the bttv drivers. Steve ===== -- If you listen very carefully you can sometimes hear the dolphins sing pinguellis@xxxxxxxxxxx __________________________________________________ Do you Yahoo!? Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop! http://platinum.yahoo.com
