Re: ir-keytable known bug -- fails to work when device specified

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Mar 19, 2019 at 08:14:45PM -0400, Adam Di Carlo wrote:
> Sean Young <sean@xxxxxxxx> 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 details for the all the rc devices and find the one that has an
> > input device with that name.
> >
> > That command line above implies that the protocol is a property of the
> > input device which it is not. Actually I think the whole -d option is
> > misleading and not really useful. I think the right solution is to just
> > remove it completely.
> 
> Ok, the patch looks good, I definately think this is a step in the right
> direction.
> 
> In cases where there is multiple devices, one would select it with, for
> instance, '-s rc1' -- is that the intent?

That's right. I'm not sure that `ir-keytable --help` or the man page
expresses that very clearly, though. Not sure what it should read..


Sean



[Index of Archives]     [Linux Input]     [Video for Linux]     [Gstreamer Embedded]     [Mplayer Users]     [Linux USB Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]

  Powered by Linux