From: Kurt W Telep <gurft@ma...> - 2004-12-01 22:35:07
I've been fighting getting my Hauppauge WinTV-GO-Plus remote (Gray
remote) workgin with LIRC.
Kernel is 2.6.9-rc4, I've downloaded lirc (0.7.0pre7) and built it with
Hauppauge support, builds fine, no issues.
modprobe lirc_dev works fine, however lirc_i2c doesn't give any output
in dmesg, almost like the module isn't even registering. I've turned on
i2c debugging and it looks liek it's scanning for the remote controller
on the i2c bus, but never finds it.
Any suggestions? In my frustration I built a serial IR module to hold
me over, but I'd liek to get this working.
Kurt W Telep <gurft@...> writes:
> I've been fighting getting my Hauppauge WinTV-GO-Plus remote
What hardware is this? bt878? cx2388x?
bt878 based cards should do just fine since ages, both lirc driver
(lirc_i2c) and linux input layer driver (ir-kbd-i2c, ships with the
2.6 kernels, see http://linux.bytesex.org/v4l2/faq.html#ir). You
can't use both drivers at the same time through.
For cx2388x support (via linux input layer) you need a cutting edge
snapshot from http://dl.bytesex.org/cvs-snapshots/. I hacked it up
yesterday, it is in the video4linux cvs since about 24 hours. Just
load the cx88 driver, you'll get a input device then. That works
completely different btw, no i2c involved, there is no way to make
lirc_i2c work with this hardware.
> (Gray remote)
Doesn't matter much, all Hauppauge remotes speak RC5 ...
#define printk(args...) fprintf(stderr, ## args)
> Even loading the ir-kbd-i2c modules gives me no output, nor does
> ir-gpio-i2c (it was a shot in the dark). hence why I'm at a loss to get
> this working.
Recent bttv versions have a i2c_scan insmod option, when enabled the
driver should print something like this:
bttv0: i2c scan: found device @ 0x30 [IR (hauppauge)]
bttv0: i2c scan: found device @ 0x80 [msp34xx]
bttv0: i2c scan: found device @ 0xa0 [eeprom]
bttv0: i2c scan: found device @ 0xc2 [tuner (analog)]
ir-kbd-i2c should print a message like this:
ir-kbd-i2c: i2c IR (Hauppauge) detected at i2c-1/1-0018/ir0 [bt878 #0 [sw]]
lirc_i2c most likely prints something as well ...