Re: Input Device Key Mapping (driver authoring advice?)

[Vojtech P. <vo...@su...>]

On Mon, Jul 04, 2005 at 01:36:54AM -0500, Dmitry Torokhov wrote:
> On Friday 01 July 2005 18:40, James Simmons wrote:
> > 
> > I CC you with Dmitry. Him and Vojtech are the main input guys now.
> > 
> 
> Unfortunately I haven't got into USB (and especially HID) side of input
> subsystem, at least not yet. Vojetch is your best chance here, although
> people on linux-usb-devel might be of help too. 
> 
> > 
> > On Tue, 28 Jun 2005, Micah F. Galizia wrote:
> > 
> > > Hello all,
> > > 
> > > Recently I came into possession of a Logitech UltraX Media Remote.  It
> > > has a USB RF receiver, and when I plug it in, it shows up as two hid
> > > devices (normal keys and media keys).  The normal keys
> > > (letters/numbers/arrows/etc) all work as they should, but some of the
> > > special buttons on the second device are unknown (though they still show
> > > up) or need to be mapped correctly.
> > > 
> > > I would like to fix this.  I had a quick look through the docs and on
> > > the list, and didn't see much on how to tackle this problem.  So, if
> > > someone could enlighten me, I would like to know what the best approach
> > > is...

The assignment of HID usages to Linux input events is done in the
hid-input.c file. Change the #undef DEBUG in there to a #define DEBUG,
and take a look at (or send me) the resulting 'dmesg' output. There
you'll see which HID usages it didn't understand and how it assigned the
others.

> > > Does this require a completely separate driver?

No.

> > > I wouldn't imagine so
> > > since all the keys generate an event, just not always the right event.
> > > If not, is there somewhere in the input system I can tune the key map,
> > > or provide one specific to this device?  Assuming neither is correct,
> > > what should I be doing, and where should I be looking for docs/examples?
 

-- 
Vojtech Pavlik
SuSE Labs, SuSE CR