From: Gregory J. Haase <haaseg@on...> - 2005-04-04 23:51:49
The IR Receiver for the Hauppauge PVR150 uses the lirc_i2c driver, which
uses lirc_dev. From what I gather from looking at the code and the
docs, lirc_dev creates an abstraction layer so that it's easy to create
drivers for additional products.
What I haven't been able to figure out, is whether or not lirc_dev has
necessary support for transmitting IR. Is that what ir_command is for
(in lirc_i2c, there is only "/* do nothing */ return 0;" here)
Anyhow... It seems that the IR Receiver is at i2c address 0xe2. I'm
assuming that the IR Blaster is at a different address.
So I'll narrow this ramble down to two questions:
1.) Can someone point me to a driver that is using lirc_dev and
2.) How can I determine the i2c address of the transmitter on my card?
And a bonus question: If the i2c address is 0xe2, why do we probe for
Gregory J. Haase "haaseg@..." wrote:
> So I'll narrow this ramble down to two questions:
> 1.) Can someone point me to a driver that is using lirc_dev and
lirc_parallel, lirc_serial, lirc_sir.
> 2.) How can I determine the i2c address of the transmitter on my card?
Ask Hauppauge. Look at the Windows driver.
> And a bonus question: If the i2c address is 0xe2, why do we probe for
0x71 = 0xe2 >> 1;
This seems to have something to do with I2C internals. I don't really
know why you have to shift the address.
Get latest updates about Open Source Projects, Conferences and News.