KWorld ATSC110 Remote: Share data from your PCI-Bus scan with the list?

[David Freeman <lists (at) davidfreeman.net>]

David Freeman wrote:

> Hi Curt,
>
> I was just thinking that there might be room for an IR remote-control 
> brainstorm afforded by your pci-bus scan data that would be better 
> than my paltry dscaler output.
>
> Could you maybe share a data dump from that scan and put it up on the 
> wiki if too large for the list?
>
> Thanks again for everything,
Sure, cause I need some help solving this is such a way that it could be 
checked in when I am done and not just a hack.

What appears to happen when the card is functioning under windows.

The GPIO bit 0x100 going low indicates there is IR data pending readback 
from an i2c device. The i2c device resides at address 0x60 in i2c 
address space.

I need the saa7134 driver to perform GPIO polling every 50ms until it 
sees bit 8 go low. Then it should read from the i2c device.

This is easy enough but this is what is messing things up I think. The 
tuner module is using 0xC2 (or 0x61). If I take out all other modules 
from saa7134-core.c the tuner module still loads.

So, here are some questions:

1. Is the IR remote stuff supposed to go in the saa7134 area or should 
it go in the ir-kbd area?

2. Can multiple modules (like the tuner and saa7134) both talk to the 
same i2c device?


Thanks,
Curt

--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request (at) redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list