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

[Micah F. G. <mfg...@uw...>]

Hello,

I've attached the patch that makes all keys on the Logitech UltraX Media
Remote work nicely.  I will verify that the previous patch correctly
assigns the channel keys in the consumer page, however, I cannot give
props to the mapping of props (sorry).  0x209 on this remote says
"Info/EPG", but it has been assigned to KEY_PROPS.  Maybe I'm just not
understanding the meaning of "props."  This patch does reassign KEY_INFO
to 0x209 in the consumer page; it that was the wrong thing to do, I'll
resubmit.

I used my best judgement when assigning keys, since the text on the
device does not always match up with a key defined in input.h.  Here is
a list of the potentially ambiguous or incorrect mappings:

Start->KEY_RED
Pictures->KEY_MEDIA
DVD Menu->KEY_MENU
SAP->KEY_AUDIO
Repeat->KEY_AGAIN
CC/Teletext->KEY_SUBTITLE
Music->KEY_MP3

Allow me to justify the silly ones.  The start key is big and red,
Google told me SAP stands for "Secondary Audio Program", and there is no
key close to pictures/graphics/image.

On Tue, 2005-05-07 at 11:04 +0200, Vojtech Pavlik wrote:
[really big snip]
> 
> Please try with this patch:
> 
[another snip]

The patch failed on account of HID_UP_LOGIVENDOR not being defined.  I
fixed two hunks manually, so it should work fine with your tree,
Vojtech.

Thanks again for all your help.  Please keep me posted if something is
wrong.
-- 
Micah F. Galizia
mfg...@uw...

"The mark of an immature man is that he wants to die
nobly for a cause, while the mark of the mature man is
that he wants to live humbly for one."   --W. Stekel