|
lirc-i2c does no longer work with Hauppauge HVR-1300?
|
View:
New views
5 Messages
—
Rating Filter:
Alert me
|
 |
lirc-i2c does no longer work with Hauppauge HVR-1300?
by Bugzilla from sha@mail-ng.de
::
Rate this Message:
Hi,
I have a Hauppauge HVR-1300 TV-Card with a bundled remote, which worked fine with lirc-i2c + 2.6.28.x in Ubuntu 9.04. Unfortunately, I can't remember which lirc version it was. Now, with Linux 2.6.31.x and lirc 0.8.5 and also 0.8.6 it doesn't work. I tested with Gentoo Linux and Ubuntu 9.10 (beta). I'm not getting the /dev/lirc0 device node, and the device is not listed in /proc/bus/input/devices. # uname -r Ubuntu: 2.6.31-11-generic Gentoo: 2.6.31-gentoo-r1 # dmesg | grep lirc [ 31.798564] lirc_dev: IR Remote Control driver registered, major 61 # lsmod | grep lirc lirc_i2c 8996 0 lirc_dev 14120 1 lirc_i2c # ls -l /dev/lirc* srw-rw-rw- 1 root root 0 2009-10-04 18:55 /dev/lircd # lircd -v Ubuntu: lircd 0.8.5 Gentoo: lircd 0.8.6 ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf |
|
|
Re: lirc-i2c does no longer work with Hauppauge HVR-1300?
by Jarod Wilson
::
Rate this Message:
On Oct 4, 2009, at 1:49 PM, sha wrote:
> I have a Hauppauge HVR-1300 TV-Card with a bundled remote, which > worked > fine with lirc-i2c + 2.6.28.x in Ubuntu 9.04. Unfortunately, I can't > remember which lirc version it was. Now, with Linux 2.6.31.x and lirc > 0.8.5 and also 0.8.6 it doesn't work. I tested with Gentoo Linux > and Ubuntu 9.10 (beta). I'm not getting the /dev/lirc0 device node, > and > the device is not listed in /proc/bus/input/devices. The i2c binding model changed considerably between 2.6.29 and 2.6.31[*], not sure if its an issue with the driver for the HVR-1300 or with lirc_i2c, will have to look into it. Not sure off the top of my head what driver the HVR-1300 uses though. [*] devices are supposed to provide all the info necessary for drivers to bind to them, so its likely the HVR-1300's driver isn't providing binding info we recognize as being legitimate for lirc_i2c to connect to. Could be that we need to add something to lirc_i2c, could also be that the HVR-1300 driver is lacking. We might also consider doing something similar to the ir-i2c-kbd driver, and try legacy probing if no devices with proper config info are found... -- Jarod Wilson jarod@... ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf |
|
|
|
|
|
Re: lirc-i2c does no longer work with Hauppauge HVR-1300?
by tmkt
::
Rate this Message:
Any progress on this?
I also have the HVR-1600, and upgrading to the new Ubuntu 9.10 with the 2.6.31-* kernel no luck whatsoever getting it to work. Use to work with ubuntu 9.04, and lirc 0.84a(which won't compile on the new kernel) Dave |
|
|
Re: lirc-i2c does no longer work with Hauppauge HVR-1300?
by Jarod Wilson
::
Rate this Message:
On Oct 4, 2009, at 2:34 PM, Jarod Wilson wrote:
> On Oct 4, 2009, at 1:49 PM, sha wrote: > >> I have a Hauppauge HVR-1300 TV-Card with a bundled remote, which >> worked >> fine with lirc-i2c + 2.6.28.x in Ubuntu 9.04. Unfortunately, I can't >> remember which lirc version it was. Now, with Linux 2.6.31.x and lirc >> 0.8.5 and also 0.8.6 it doesn't work. I tested with Gentoo Linux >> and Ubuntu 9.10 (beta). I'm not getting the /dev/lirc0 device node, >> and >> the device is not listed in /proc/bus/input/devices. > > The i2c binding model changed considerably between 2.6.29 and > 2.6.31[*], not sure if its an issue with the driver for the HVR-1300 > or with lirc_i2c, will have to look into it. Not sure off the top of > my head what driver the HVR-1300 uses though. > > [*] devices are supposed to provide all the info necessary for drivers > to bind to them, so its likely the HVR-1300's driver isn't providing > binding info we recognize as being legitimate for lirc_i2c to connect > to. Could be that we need to add something to lirc_i2c, could also be > that the HVR-1300 driver is lacking. We might also consider doing > something similar to the ir-i2c-kbd driver, and try legacy probing if > no devices with proper config info are found... So I'm not quite sure what I was thinking... There is no legacy probing that I can see in ir-kbd-i2c (didn't even get the name right). So far as I can tell, probing has to be done on the main device driver side, including legacy probing -- the new/preferred method is to explicitly list where a device's i2c parts are, rather than probing. Now, we *do* have Dave(tmkt)'s system w/an HVR-1600 working... The root of the problem is that the i2c client model changed significantly in 2.6.31, and some drivers (such as the cx18 driver for the HVR-1600) weren't updated soon enough for the 2.6.31 window, meaning even ir-kbd- i2c is broken with them as well. What needs to happen is some patchification of those drivers in a 2.6.31.x stable release, I think (going to ping some v4l/dvb folks on that). What we did on Dave's box is build the cx18 driver (well, all v4l-dvb drivers) from v4l-dvb mercurial, and all was well again. Short version: hg clone http://linuxtv.org/hg/v4l-dvb cd v4l-dvb make make install If you get errors about some driver or another not building, if its one you don't need, you can disable it from being built in v4l/ Makefile.media (the firedtv driver was failing on Dave's system for some reason). If you update your kernel to another that still doesn't have the required i2c fixage in it, you'll lose the fixes from v4l-dvb, but can get 'em back by going back into that v4l-dvb checkout and rebuilding (after doing a 'make distclean' so the build uses the new kernel headers instead of the prior one). HTH, -- Jarod Wilson jarod@... ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference |
| Free embeddable forum powered by Nabble | Forum Help |
