Re: [PATCH] [RFC] rc-core: report protocol information to userspace

2017-05-01 Thread Sean Young
On Mon, May 01, 2017 at 02:49:57PM +0200, David Härdeman wrote: > On Mon, May 01, 2017 at 11:38:30AM +0100, Sean Young wrote: > >On Sat, Apr 29, 2017 at 12:52:12PM +0200, David Härdeman wrote: > >> Whether we decide to go for any new keytable ioctl():s or not in rc-core, > >> we > >> should

Re: [PATCH] [RFC] rc-core: report protocol information to userspace

2017-05-01 Thread David Härdeman
On Mon, May 01, 2017 at 11:38:30AM +0100, Sean Young wrote: >On Sat, Apr 29, 2017 at 12:52:12PM +0200, David Härdeman wrote: >> Whether we decide to go for any new keytable ioctl():s or not in rc-core, we >> should provide the protocol information of keypresses to userspace. >> >> Note that this

Re: [PATCH] [RFC] rc-core: report protocol information to userspace

2017-05-01 Thread Sean Young
On Sat, Apr 29, 2017 at 12:52:12PM +0200, David Härdeman wrote: > Whether we decide to go for any new keytable ioctl():s or not in rc-core, we > should provide the protocol information of keypresses to userspace. > > Note that this means that the RC_TYPE_* definitions become part of the >

[PATCH] [RFC] rc-core: report protocol information to userspace

2017-04-29 Thread David Härdeman
Whether we decide to go for any new keytable ioctl():s or not in rc-core, we should provide the protocol information of keypresses to userspace. Note that this means that the RC_TYPE_* definitions become part of the userspace <-> kernel API/ABI (meaning a full patch should maybe move those