Re: ir-keytable: infinite loops, segfaults

On 3/1/17, Sean Young wrote: > > Sorry Vincent, but are you sure you're running the patch with the > & 0xff mask? That should have solved it. > er, no. Some kind of build issue. Once I applied your media_build patch and then the latest kernel patch you sent, this is what the test

Re: ir-keytable: infinite loops, segfaults

On Sat, Feb 25, 2017 at 02:08:39AM +1100, Vincent McIntyre wrote: > On 2/22/17, Sean Young wrote: > > > So it's still using the old keymap. I've attached a new one. > > That works, thanks. > > >> # vol down > >> 1487676637.746348: event type EV_MSC(0x04): scancode = 0x0105

Re: ir-keytable: infinite loops, segfaults

On 2/22/17, Sean Young wrote: > So it's still using the old keymap. I've attached a new one. That works, thanks. >> # vol down >> 1487676637.746348: event type EV_MSC(0x04): scancode = 0x0105 >> 1487676637.746348: event type EV_SYN(0x00). >> # vol up >>

Re: ir-keytable: infinite loops, segfaults

On Wed, Feb 22, 2017 at 12:07:07AM +1100, Vincent McIntyre wrote: > On 2/21/17, Sean Young wrote: > >> $ sudo cat /sys/class/rc/rc1/protocols > >> nec > >> $ sudo sh > >> # echo "+rc-5 +nec +rc-6 +jvc +sony +rc-5-sz +sanyo +sharp +xmp" > > >> /sys/class/rc/rc1/protocols > >> bash:

Re: ir-keytable: infinite loops, segfaults

On 2/21/17, Sean Young wrote: > Hi Vincent, > ... > > On the cxusb the protocol is now nec, and that is the only protocol it > supports, you can't change it. > doh! ok well that's all good then. >> $ sudo cat /sys/class/rc/rc1/protocols >> nec >> $ sudo sh >> # echo "+rc-5 +nec

Re: ir-keytable: infinite loops, segfaults

Hi Vincent, Thanks for testing this. On Fri, Feb 17, 2017 at 12:05:50AM +1100, Vincent McIntyre wrote: > Hi again > > after you kindly fixed media_build for me I applied the nec protocol > patch and tried again. > > $ sudo ir-keytable > Found /sys/class/rc/rc0/ (/dev/input/event5) with: >

Fwd: [regression] dvb_usb_cxusb (was Re: ir-keytable: infinite loops, segfaults)

Hi list I missed you in the cc: field... -- Forwarded message -- From: Vincent McIntyre <vincent.mcint...@gmail.com> Date: Thu, 16 Feb 2017 23:51:05 +1100 Subject: Re: [regression] dvb_usb_cxusb (was Re: ir-keytable: infinite loops, segfaults) To: Sean Young <s...@mess.o

Re: ir-keytable: infinite loops, segfaults

The dmesg... dmesg.txt.gz Description: GNU Zip compressed data

Re: ir-keytable: infinite loops, segfaults

Hi again after you kindly fixed media_build for me I applied the nec protocol patch and tried again. $ sudo ir-keytable Found /sys/class/rc/rc0/ (/dev/input/event5) with: Driver imon, table rc-imon-mce Supported protocols: rc-6 Enabled protocols: rc-6 Name: iMON

Re: [regression] dvb_usb_cxusb (was Re: ir-keytable: infinite loops, segfaults)

On Wed, Feb 08, 2017 at 10:30:30PM +1100, Vincent McIntyre wrote: > Hi > > I have been working with Sean on figuring out the protocol used by a > dvico remote. > I thought the patch he sent was at fault but I backed it out and tried again. > > I've attached a full dmesg but the core of it is

Re: [regression] dvb_usb_cxusb (was Re: ir-keytable: infinite loops, segfaults)

ping? My media_build tree is updated as far as: $ git log -1 commit 0721d4bde661c71cd4e41de37afb24b0694c65a3 Author: Hans Verkuil Date: Mon Nov 21 13:17:19 2016 +0100 Only use Makefile.mm if frame_vector.c is present. Signed-off-by: Hans Verkuil

Re: [regression] dvb_usb_cxusb (was Re: ir-keytable: infinite loops, segfaults)

Hi Vincent, On Wed, Feb 08, 2017 at 10:30:30PM +1100, Vincent McIntyre wrote: > Hi > > I have been working with Sean on figuring out the protocol used by a > dvico remote. > I thought the patch he sent was at fault but I backed it out and tried again. > > I've attached a full dmesg but the core

[regression] dvb_usb_cxusb (was Re: ir-keytable: infinite loops, segfaults)

Hi I have been working with Sean on figuring out the protocol used by a dvico remote. I thought the patch he sent was at fault but I backed it out and tried again. I've attached a full dmesg but the core of it is when dvb_usb_cxusb tries to load: [7.858907] WARNING: You are using an

Re: ir-keytable: infinite loops, segfaults

I tried your patch, after disabling the custom keymap file I had put in. Unfortunately the remote isn't working at all. When the relevant modules get loaded I see this in dmesg [7.838223] media: Linux media interface: v0.10 [7.840484] WARNING: You are using an experimental version of the

Re: ir-keytable: infinite loops, segfaults

Hi Vincent, On Thu, Feb 02, 2017 at 10:18:52PM +1100, Vincent McIntyre wrote: > On 11/30/16, Vincent McIntyre wrote: > > On Sun, Nov 27, 2016 at 07:35:10PM +, Sean Young wrote: > >> > >> > I wanted to mention that the IR protocol is still showing as unknown. > >>

Re: ir-keytable: infinite loops, segfaults

Hey there On 11/30/16, Vincent McIntyre wrote: > On Sun, Nov 27, 2016 at 07:35:10PM +, Sean Young wrote: >> >> > I wanted to mention that the IR protocol is still showing as unknown. >> > Is there anything that can be done to sort that out? >> >> It would be nice

Re: ir-keytable: infinite loops, segfaults

On Sun, Nov 27, 2016 at 07:35:10PM +, Sean Young wrote: > > > I wanted to mention that the IR protocol is still showing as unknown. > > Is there anything that can be done to sort that out? > > It would be nice if that could be sorted out, although that would be > a separate patch. > > So

Re: ir-keytable: infinite loops, segfaults

On Sun, Nov 27, 2016 at 07:35:10PM +, Sean Young wrote: > > The application I am trying to use it with is the mythtv frontend. I > > am doing the keycode munging from an SSH session while myth is still > > running on the main screen. I didn't think this would matter (since it > > worked for

Re: ir-keytable: infinite loops, segfaults

On Fri, Nov 25, 2016 at 07:59:21PM +1100, Vincent McIntyre wrote: > On 11/25/16, Sean Young wrote: > > > > So if I understand you correctly, if you change the keymap, like you > > changed 0xfe47 to KEY_PAUSE, then "ir-keytable -s rc1 -t" show you the > > correct (new) key? So as

Re: ir-keytable: infinite loops, segfaults

>> >> However when you try to use the new mapping in some application then >> it does not work? > > That's correct. ir-keytable seems to be doing the right thing, mapping > the scancode to the input-event-codes.h key code I asked it to. > > The application I am trying to use it with is the mythtv

Re: ir-keytable: infinite loops, segfaults

On 11/25/16, Sean Young wrote: > > So if I understand you correctly, if you change the keymap, like you > changed 0xfe47 to KEY_PAUSE, then "ir-keytable -s rc1 -t" show you the > correct (new) key? So as far as ir-keytable is concerned, everything > works? > > However when you try

Re: ir-keytable: infinite loops, segfaults

On Thu, Nov 24, 2016 at 11:12:57PM +1100, Vincent McIntyre wrote: > On Wed, Nov 23, 2016 at 10:34:19PM +, Sean Young wrote: > > > Not sure why Driver is (null), dvb_usb_cxusb is loaded. > > > > That's a mistake, I've fixed that now. > > Ah. I see the added module_name struct members. > > >

Re: ir-keytable: infinite loops, segfaults

On Wed, Nov 23, 2016 at 10:34:19PM +, Sean Young wrote: > > Not sure why Driver is (null), dvb_usb_cxusb is loaded. > > That's a mistake, I've fixed that now. Ah. I see the added module_name struct members. > > I tried -t and it generated events constantly, before I could press > > any

Re: ir-keytable: infinite loops, segfaults

On Wed, Nov 23, 2016 at 11:39:06PM +1100, Vincent McIntyre wrote: > On Tue, Nov 22, 2016 at 09:20:44AM +, Sean Young wrote: > > > Thanks for this. I have got it to build within the media_build setup > > > but will need to find some windows in the schedule for testing. More > > > in a couple of

Re: ir-keytable: infinite loops, segfaults

On Tue, Nov 22, 2016 at 09:20:44AM +, Sean Young wrote: > > Thanks for this. I have got it to build within the media_build setup > > but will need to find some windows in the schedule for testing. More > > in a couple of days. Are there specific things you would like me to > > test? > > You

Re: ir-keytable: infinite loops, segfaults

On Tue, Nov 22, 2016 at 06:25:59PM +1100, Vincent McIntyre wrote: > On 11/21/16, Sean Young wrote: > >> > >> Ah. Here we have a problem. The device (/dev/input/event15) > >> doesn't have a corresponding rcX node, see ir-keytable output below. > >> I had it explained to me like

Re: ir-keytable: infinite loops, segfaults

On 11/21/16, Sean Young wrote: >> >> Ah. Here we have a problem. The device (/dev/input/event15) >> doesn't have a corresponding rcX node, see ir-keytable output below. >> I had it explained to me like this: > > As I said you would need to use a raw IR receiver which has rc-core

Re: ir-keytable: infinite loops, segfaults

On Sat, Nov 19, 2016 at 09:01:10AM +1100, Vincent McIntyre wrote: > On Fri, Nov 18, 2016 at 05:40:34PM +, Sean Young wrote: > > > > > > So are you saying that the hex codes in the rc_map_dvico_mce_table > > > struct are invalid (at least in some cases)? > > > > Most likely the remote

Re: ir-keytable: infinite loops, segfaults

On Fri, Nov 18, 2016 at 05:40:34PM +, Sean Young wrote: > > At the moment it's not easy to determine what protocol an remote uses; > I would like to change that but for now, the following is probably > the easiest way. > > cd /sys/class/rc/rc1 # replace rc1 with your receiver > for i in

Re: ir-keytable: infinite loops, segfaults

On Fri, Nov 18, 2016 at 05:40:34PM +, Sean Young wrote: > > > > # ir-keytable > > Found /sys/class/rc/rce0/ (/dev/input/event5) with: > > Driver imon, table rc-imon-mce > > Supported protocols: rc-6 > > Enabled protocols: rc-6 > > Name: iMON Remote (15c2:ffdc) > > bus:

Re: ir-keytable: infinite loops, segfaults

On Fri, Nov 18, 2016 at 05:40:34PM +, Sean Young wrote: > > > > So are you saying that the hex codes in the rc_map_dvico_mce_table > > struct are invalid (at least in some cases)? > > Most likely the remote produces IR in a standard protocol (e.g. rc5, rc6). > If we first get the keymap

Re: ir-keytable: infinite loops, segfaults

On Fri, Nov 18, 2016 at 11:14:25PM +1100, Vincent McIntyre wrote: > On Thu, Nov 17, 2016 at 01:45:26PM +, Sean Young wrote: > > On Wed, Nov 16, 2016 at 09:52:58PM +1100, Vincent McIntyre wrote: > > > I have a fairly old dvico dual digital 4 tuner and remote. > > > There seem to be some issues

Re: ir-keytable: infinite loops, segfaults

On Thu, Nov 17, 2016 at 01:45:26PM +, Sean Young wrote: > On Wed, Nov 16, 2016 at 09:52:58PM +1100, Vincent McIntyre wrote: > > I have a fairly old dvico dual digital 4 tuner and remote. > > There seem to be some issues with support for it, can I help fix them? > > > > I am using ir-keytable

Re: ir-keytable: infinite loops, segfaults

On Wed, Nov 16, 2016 at 09:52:58PM +1100, Vincent McIntyre wrote: > I have a fairly old dvico dual digital 4 tuner and remote. > There seem to be some issues with support for it, can I help fix them? > > I am using ir-keytable 1.10.0-1 on Ubuntu 16.04 LTS, > with kernel 4.4.0-47-generic (package

ir-keytable: infinite loops, segfaults

Hi, I have a fairly old dvico dual digital 4 tuner and remote. There seem to be some issues with support for it, can I help fix them? I am using ir-keytable 1.10.0-1 on Ubuntu 16.04 LTS, with kernel 4.4.0-47-generic (package version 4.4.0-47-generic) The remote's keymapping is the one in