Re: flyvideo3000(saa7134) and remote control

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]





Is there a "generic" procedure that is needed to get remotes working
with these sorts of cards, or are specific drivers/configs required?
Is it done with the irda drivers, lm-sensors, i2c, bttv, or what?
Schematics of the SAA7134 Philips reference boards show an i2c based solution for the IR receiver IC. But it could also be possible that the IR receiver IC is connected to the gpio of the SAA7134.

If you would scan which devices are available on the i2c bus, you could see wheter an i2c based solution is available. In the bttv-0.7 package there is a tool called "detect", which scan the i2c bus for devices.

Output for my bttv-card:

[root@viper tools]# /sbin/modprobe i2c-dev
[root@viper tools]# ./detect
0x30: Hauppauge IR (pic16c54 onboard)
0x80: msp34xx/tea6300 sound processor (error: Device or resource busy)
0xa0: eeprom (bt878, Hauppauge-848)
0xc2: tuner (error: Device or resource busy)
[root@viper tools]#

In case of a SAA7134, you will find a tuner (0xc0,0xc2), maybe an eeprom (0xa0,0xa2,0xa4,....) and if there still one more i2c address left, it is likely the IR receiver IC.

You could also have a look at the board, and see what IR receiver IC is mounted on it.

The lirc package has a driver for a i2c based IR receiver, which works for my bttv board.

Gert






[Index of Archives]     [Linux DVB]     [Video Disk Recorder]     [Asterisk]     [Photo]     [DCCP]     [Netdev]     [Xorg]     [Util Linux NG]     [Xfree86]     [Free Photo Albums]     [Fedora Users]     [Fedora Women]     [ALSA Users]     [ALSA Devel]     [Linux USB]

Powered by Linux