Jon, Can you post your kernel patch with the fixes. I'm probably using the one by Dwaine Garden "80th attempt...." post. I would like any improvement in button response. Thank you. Nathan. ------------------------------------------- Nathan Faust -----Original Message----- From: Jonathan Isom [mailto:jeisom@xxxxxxxxx] Sent: Monday, April 02, 2007 11:13 AM To: Nathan Faust Cc: linux-dvb@xxxxxxxxxxx Subject: Re: kworld atsc 110 remote Hello Yeah I have a modified patch that seems more responsive that detects button presses through gpio. also the patch I found on the list (80th attempt....) has some duplicate entries in the key map that i think is causing some of the problems(specifically presses being miss detected as other buttons. so far (since last night) it seems better. Though I'd like to use lirc directly so any remote would work. the lirc_i2c driver is very similar to the saa7134's i2c input driver, code wise , but I just get 1 byte codes like its hard coded for there remote. If the patch stays stable I'll post it. later Jonathan On 4/2/07, Nathan Faust <nfaust@xxxxxxxxxxxxxxxxxxxxx> wrote: > Jon, > > Having the same card, the best I have done is: > Apply the kernel patch to create an event input device for the ir > sensor. > I'm still seeing some of the issues talked about with the patch: > delayed button presses the most notable one. > I created a udev rule to map /dev/input/event? -> /dev/input/irremote > KERNEL=="event*",ATTRS{modalias}=="input:b0018v0000p0000e0000- > e0,1,14,k71,72,73,74,80,9F,A3,A4,A5,A7,A8,D2,D9,16D,174,188,189,192,193, > ramlsfw",SYMLINK="input/ > irremote" > I setup lirc in /etc/lirc/hardware.conf to read from the dev/input > driver on /dev/input/irremote > # /etc/lirc/hardware.conf > # > # Arguments which will be used when launching lircd > LIRCD_ARGS="" > #Don't start lircmd even if there seems to be a good config file > #START_LIRCMD=false > #Try to load appropriate kernel modules > LOAD_MODULES=false > # Run "lircd --driver=help" for a list of supported drivers. > DRIVER="dev/input" > # If DEVICE is set to /dev/lirc and devfs is in use /dev/lirc/0 > will be > # automatically used instead > DEVICE="/dev/input/irremote" > MODULES="" > # Default configuration files for your hardware if any > LIRCD_CONF="/etc/lirc/lircd.conf" > LIRCMD_CONF="" > And used the lircd.conf file from > http://lirc.sourceforge.net/remotes/kworld/ATSC_110 > ------------------------------------------- > Nathan Faust > > > -----Original Message----- > From: linux-dvb-bounces@xxxxxxxxxxx > [mailto:linux-dvb-bounces@xxxxxxxxxxx] On Behalf Of Jonathan Isom > Sent: Sunday, April 01, 2007 9:24 PM > To: linux-dvb@xxxxxxxxxxx > Subject: kworld atsc 110 remote > > Hello > I'm hoping some one can help me. I'm trying to make lirc handle > the remote control for the 110 but all the data i get from the card is > from the remote that came with the card. The codes i receive from the > remote are 1 byte long and match the buttons mapping in the patch > floating around. I was wondering if maybe you have to init the ir > controller to use it with another remote. > any ideas > Jonathan > > _______________________________________________ > linux-dvb mailing list > linux-dvb@xxxxxxxxxxx > http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb > > > _______________________________________________ linux-dvb mailing list linux-dvb@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb