On Tue, Mar 19, 2019 at 08:14:45PM -0400, Adam Di Carlo wrote:
> Sean Young writes:
> > Adam wrote:
> >> Rather than document all this, isn't better to clean it up in the
> >> source? I can probably come up with a patch for this issue in fairly
> >> short order, if that's welcome.
> >
> > You're
Sean Young writes:
> Adam wrote:
>> Rather than document all this, isn't better to clean it up in the
>> source? I can probably come up with a patch for this issue in fairly
>> short order, if that's welcome.
>
> You're right, this is broken. For this to work it would have to get all
> the detail
On Mon, Mar 18, 2019 at 08:19:42PM -0400, Adam Di Carlo wrote:
>
> There seems to be known issue with ir-keytable such that while
>
> ./ir-keytable -p rc5
>
> works, this one won't:
>
> ./ir-keytable -d /dev/input/event24 -p rc5
>
> Reading the source, it looks like the internal 'rc_dev' s
There seems to be known issue with ir-keytable such that while
./ir-keytable -p rc5
works, this one won't:
./ir-keytable -d /dev/input/event24 -p rc5
Reading the source, it looks like the internal 'rc_dev' struct is really
only filled out (get_attribs()) in the case where the device isn't
