From: Leonardo D. M. <mzd...@cs...> - 2003-03-29 00:05:19
|
Hi, I have an AIMSLab Video Highway Xtreme 98 Deluxe (Brooktree chipset bt848, card 14 in the CARDLIST bbtv's kernel driver) and I would like to have lirc running on it. I was reading this list discovering that Timothy Lu Hu Ball on 2001-11-28 20:14 post on the same topic but unfortunatelly there was no response. I've tried to load the bttv module as: "modprobe bttv card=6" and it seemed that something could start working. Of course, that is another card but my question is: Lirc is not running in my card because of bbtv's kernel driver or just because there's not enogh support in the lirc's module driver itself? I'm interested to help in the support of lirc for my card if my knowledge allows me to do so. |
From: Leonardo D. M. <md...@cs...> - 2003-03-27 22:15:40
|
Hi, I have an AIMSLab Video Highway Xtreme 98 Deluxe (Brooktree chipset bt848, card 14 in the CARDLIST bbtv's kernel driver) and I would like to have lirc running on it. I was reading this list discovering that Timothy Lu Hu Ball on 2001-11-28 20:14 post on the same topic but unfortunatelly there was no response. I've tried to load the bttv module as: "modprobe bttv card=6" and it seemed that something could start to work. Of course, that is another card but my question is: Lirc is not running in my card because of bbtv's kernel driver or just because there's not enogh support in the lirc's module driver itself? I'm interested to help in the support of lirc for my card if my knowledge allows me. |
From: <col...@hi...> - 2003-03-30 17:15:41
|
Hi! Leonardo Daniel Mizyrycki "md...@cs..." wrote: > Hi, I have an AIMSLab Video Highway Xtreme 98 Deluxe (Brooktree chipset [...] > Lirc is not running in my card because of bbtv's kernel driver or > just because there's not enogh support in the lirc's module driver itself? There is no entry in the rcv_infos table in lirc_gpio.c for your card. Christoph |
From: Leonardo D. M. <mzd...@cs...> - 2003-04-14 21:11:16
|
Christoph Bartelmus wrote: >Hi! > >Leonardo Daniel Mizyrycki "md...@cs..." wrote: > > >>Hi, I have an AIMSLab Video Highway Xtreme 98 Deluxe (Brooktree chipset >> >> >[...] > > >> Lirc is not running in my card because of bbtv's kernel driver or >>just because there's not enogh support in the lirc's module driver itself? >> >> > >There is no entry in the rcv_infos table in lirc_gpio.c for your card. > >Christoph > > Do you mean that in order to support VHX card, it's nessesary to tweak rcv_infos table and not the bttv's kernel driver? I add to that file in the rcv_info table the following line: {BTTV_VHX, 0, 0x000000f8, 0, 0x0000100, 0x0000100, 0, 10, 0}, I decided to assign gpio_mask 0xf8, because in the bttv's kernel driver said gpiomask: 7. I chose the rest of the parameters more or less at random. It seemed that the gpio port is reading something when loading bttv and lirc_gpio modules, and later running irrecord. I didn't expect to have my card running, but the values I obtained from lirc_gpio with debug activated were always the same. I expected to have something different when I sent signal from a remote control to the card. That's why I started to suspect my card maybe needs more support from the kernel. Anyway I have that card and I would like to try to add support to it, but I will need help. Any suggestions? |
From: <col...@hi...> - 2003-04-18 20:15:32
|
Hi! Leonardo Daniel Mizyrycki "mzd...@cs..." wrote: [...] >>> Lirc is not running in my card because of bbtv's kernel driver or >>> just because there's not enogh support in the lirc's module driver itself? >> >> There is no entry in the rcv_infos table in lirc_gpio.c for your card. [...] > Do you mean that in order to support VHX card, it's nessesary to > tweak rcv_infos table and > not the bttv's kernel driver? Yes, if the card is designed to use GPIO for the remote control. > I add to that file in the rcv_info table the following line: > {BTTV_VHX, 0, 0x000000f8, 0, 0x0000100, 0x0000100, 0, 10, 0}, > > I decided to assign gpio_mask 0xf8, because in the bttv's kernel [...] > Any suggestions? Try differnt gpio masks. I'd try 0xfffffff8 first. Christoph |