I actually sent these attachments last night, but I must have been too tired to notice it was from the wrong account :)
Anyway, I hacked together the additions to the saa7134 code to enable access to the GPIO data, and modified the lirc_gpio driver for the saa7134. The IR remote now works for me. The relevant files are attached.
Wan Tat Chee wrote:
The reported GPIO readouts so far doesn't have 0x01000 (bit12) enabled.
Most people are seeing 0x30000 (which is similar to your no button pressed
case). I wonder if 0x01000 (bit 12) is set at a later time?
So I *guess* the GPIO map for FV2K/FV3K looks like the following:
Bits: 27-25 24 23-21 20 19 18 17-16 15-13 12 11-0
RemIn ?? RemIn ?? ?? BtnIn ????? AMuxOut ?? ????
RemIn: Remote Input Value (Input)
BtnIn: Button Pressed (Input)
AMuxOut: HEF4052 Analog Mux Enable & Select (Output)
????: Unknown (I'm assuming the constant bits, e.g. b16-17, may be other
inputs like the Resistor pad Configuration)
That seems to be in-line with what I've noticed (and implemented for the remote).
It doesn't seem to be possible to detect for a remote from the GPIO pins (see below). However I wonder if bit 12 (0x01000) indicates radio?
- David Atkinson. GPIO Results for FlyVIDEO cards -------------------- Philip Gladstone ? 1,3,5 NTSC 2k (?) Wan Tat Chee 0x30500 1,3 PAL-BG 2k, no radio, no EEPROM Silvano Galliani 0x31000 5 PAL-BG / PAL-DK 2k, IR, radio Shaun Jackman 0x38500 1,3 NTSC(USA) 2k, IR, no radio, EEPROM David Atkinson 0x39000 5 PAL-BG / PAL-DK 3k, IR, radio
Attachment:
irfiles.tar.bz2
Description: Binary data
