Re: [RFC] Infrared Keycode standardization

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

 



Em Thu, 27 Aug 2009 13:17:57 -0400
Devin Heitmueller <dheitmueller@xxxxxxxxxxxxxx> escreveu:

> On Thu, Aug 27, 2009 at 1:06 PM, Peter
> Brouwer<pb.maillists@xxxxxxxxxxxxxx> wrote:
> > Mauro Carvalho Chehab wrote:
> >
> > Hi Mauro, All
> >
> > Would it be an alternative to let lirc do the mapping and just let the
> > driver pass the codes of the remote to the event port.

For most devices, this is already allowed, via the standard
EVIOCGKEYCODE/EVIOCSKEYCODE ioctl. 

There's a small application showing how to change the keycodes. It is called
"keytable", and it is avalable at v4l2-apps/util directory at our development
tree:
	http://linuxtv.org/hg/v4l-dvb

Yet, there are some DVB-only devices that use a different way to support event
interface that doesn't allow userspace to replace the IR tables. I've looked on
the dvb-usb code recently. While a patch for it is not trivial, it shouldn't be
that hard to change it to support the key GET/SET ioctls, but a patch for it
requires some care, since it will touch on several different places and drivers.

I'll probably try to address this later.

Cheers,
Mauro
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[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