Bug 8469 - make multimedia keys map as keys and not buttons
Summary: make multimedia keys map as keys and not buttons
Status: RESOLVED INVALID
Alias: None
Product: xorg
Classification: Unclassified
Component: Input/evdev (show other bugs)
Version: git
Hardware: x86 (IA32) Linux (All)
: high normal
Assignee: Zephaniah E. Hull
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords: patch
Depends on:
Blocks:
 
Reported: 2006-09-30 18:12 UTC by Olivier Crête
Modified: 2008-12-04 22:21 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:


Attachments
patch-against the current git tree (851 bytes, patch)
2006-09-30 18:12 UTC, Olivier Crête
no flags Details | Splinter Review

Description Olivier Crête 2006-09-30 18:12:34 UTC
On my MX3100 keyboard, some multimedia keys emit event numbers that the current
driver maps to mouse buttons.. I change the range to make it smaller, and it
works. There should probably be min/max options so users can change them
depending on the type of hardware they have.

Also, many of those events have ids over 256, and Xorg seems to do
keycode%256... and its not very convenient because they get mapped as regular
letters. So I added another patch that does 256-(keycode%256) so they get mapped
onto unused keycodes.
There should probably also be an option for this..
Comment 1 Olivier Crête 2006-09-30 18:12:59 UTC
Created attachment 7223 [details] [review]
patch-against the current git tree
Comment 2 Peter Hjalmarsson 2006-11-17 03:37:49 UTC
I tried this patch agains xf86-input-evdev-1.1.4 but it does not seems to work
anymore. xev gave me "buttons" before, but now xev gives me nothing.
Comment 3 Daniel Stone 2007-02-27 01:33:46 UTC
Sorry about the phenomenal bug spam, guys.  Adding xorg-team@ to the QA contact so bugs don't get lost in future.
Comment 4 Peter Hutterer 2008-06-28 03:52:55 UTC
I just checked the sources for evdev 2.0  and the first half of your patch is
basically in there, so the button mapping issue should be fixed. Can you
confirm this please?

As for the solutions to keycodes > 255 - no. The correct method would be to
switch the keyboard mapping and then send the event % 256.
Comment 5 Peter Hutterer 2008-12-04 22:21:56 UTC
No feedback from reporter for 6 months. Closing.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.