From: Marc L. <mla...@ho...> - 2003-04-23 00:54:41
|
> ls -l /dev/lirc* ? > Which device does lircd try to open? Thanks, turns out I didn't have my device setup properly, redid it as follows: crw-r--r-- 1 root root 61, 0 Apr 18 19:26 /dev/lirc I got a little bit further but now term 1 ------ insmod drivers/lirc_dev/lirc_dev.o insmod drivers/lirc_i2c/lirc_i2c.o ./daemons/lircd /etc/lircd.conf lircd 0.7.0pre1: lircd(hauppauge) ready term 2 ------ ./tools/irw term 1 (cont) ------ lircd 0.7.0pre1: accepted new client on /dev/lircd lircd 0.7.0pre1: could not open /dev/lirc lircd 0.7.0pre1: default_init(): No such device lircd 0.7.0pre1: caught signal That said, I can see an attempt is made to load the bttv module. However, this card uses the ivtv module since the encoder chip is a Conexant. So, back to my original post, there does appear to be a dependency on the bttv driver for the LIRC implementation of the Hauppauge IRs. So would my best bet be to modify the bttv module to fake it into loading for the WinTV PVR 250/350 cards or cannibalize the IR related code and add it to the ivtv code (ivtv.sf.net). It looks like the mapping functions used by LIRC are in bttv-if.c, in particular the GPIO stuff. I checked the ivtv code and the GPIO interface is not implemented. Is it safe to say that the first step into getting this working would be to copy the GPIO code from the bttv driver into the ivtv driver? Any hints or suggestions are really appreciated! Thanks, Marc L. |
From: Marc L. <mla...@ho...> - 2003-04-21 13:50:53
|
> ls -l /dev/lirc* ? > Which device does lircd try to open? Thanks, turns out I didn't have my device setup properly, redid it as follows: crw-r--r-- 1 root root 61, 0 Apr 18 19:26 /dev/lirc I got a little bit further but now term 1 ------ insmod drivers/lirc_dev/lirc_dev.o insmod drivers/lirc_i2c/lirc_i2c.o ./daemons/lircd /etc/lircd.conf lircd 0.7.0pre1: lircd(hauppauge) ready term 2 ------ ./tools/irw term 1 (cont) ------ lircd 0.7.0pre1: accepted new client on /dev/lircd lircd 0.7.0pre1: could not open /dev/lirc lircd 0.7.0pre1: default_init(): No such device lircd 0.7.0pre1: caught signal That said, I can see an attempt is made to load the bttv module. However, this card uses the ivtv module since the encoder chip is a Conexant. So, back to my original post, there does appear to be a dependency on the bttv driver for the LIRC implementation of the Hauppauge IRs. So would my best bet be to modify the bttv module to fake it into loading for the WinTV PVR 250/350 cards or cannibalize the IR related code and add it to the ivtv code (ivtv.sf.net). It looks like the mapping functions used by LIRC are in bttv-if.c, in particular the GPIO stuff. I checked the ivtv code and the GPIO interface is not implemented. Is it safe to say that the first step into getting this working would be to copy the GPIO code from the bttv driver into the ivtv driver? Any hints or suggestions are really appreciated! Thanks, Marc L. |
From: Sam W. <wa...@he...> - 2003-05-18 00:12:13
|
Hi Marc, I am having exactly the same problem as you are having -- have you had any luck in getting the PVR 250 remote to work under LIRC? The lirc_i2c module inserts without errors, but the log file reads something like May 17 16:05:59 mythtv.waldman lircd 0.7.0pre1: lircd(hauppauge) ready May 17 16:06:05 mythtv.waldman lircd 0.7.0pre1: accepted new client on /dev/lircd May 17 16:06:05 mythtv.waldman lircd 0.7.0pre1: could not open /dev/lirc May 17 16:06:05 mythtv.waldman lircd 0.7.0pre1: default_init(): No such device May 17 16:06:05 mythtv.waldman lircd 0.7.0pre1: caught signal when I try to run irw. Any help would be greatly appreciated. sam >Thanks, turns out I didn't have my device setup properly, redid it as > follows: > > crw-r--r-- 1 root root 61, 0 Apr 18 19:26 /dev/lirc > > I got a little bit further but now > > term 1 > ------ > insmod drivers/lirc_dev/lirc_dev.o > insmod drivers/lirc_i2c/lirc_i2c.o > ./daemons/lircd /etc/lircd.conf > lircd 0.7.0pre1: lircd(hauppauge) ready > > term 2 > ------ > ./tools/irw > > term 1 (cont) > ------ > lircd 0.7.0pre1: accepted new client on /dev/lircd > lircd 0.7.0pre1: could not open /dev/lirc > lircd 0.7.0pre1: default_init(): No such device > lircd 0.7.0pre1: caught signal > > That said, I can see an attempt is made to load the bttv module. > However, this card uses the ivtv module since the encoder chip is a > Conexant. > |
From: <col...@hi...> - 2003-05-25 09:15:08
|
Hi! Sam Waldman "wa...@he..." wrote: [...] > I am having exactly the same problem as you are having -- have you > had any luck in getting the PVR 250 remote to work under LIRC? The > lirc_i2c module inserts without errors, but the log file reads something > like > > May 17 16:05:59 mythtv.waldman lircd 0.7.0pre1: lircd(hauppauge) ready > May 17 16:06:05 mythtv.waldman lircd 0.7.0pre1: accepted new client on > /dev/lircd > May 17 16:06:05 mythtv.waldman lircd 0.7.0pre1: could not open /dev/lirc > May 17 16:06:05 mythtv.waldman lircd 0.7.0pre1: default_init(): No such > device lirc_i2c probably does not find any known chips. [...] >> That said, I can see an attempt is made to load the bttv module. >> However, this card uses the ivtv module since the encoder chip is a >> Conexant. My guess is that you will have to modify lirc_i2c to support this card. Christoph |