| Summary: | events from remote control not mapped correctly to X events | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | xorg | Reporter: | Paul Menzel <paulepanter> | ||||||
| Component: | Input/evdev | Assignee: | Peter Hutterer <peter.hutterer> | ||||||
| Status: | RESOLVED WONTFIX | QA Contact: | Xorg Project Team <xorg-team> | ||||||
| Severity: | normal | ||||||||
| Priority: | medium | CC: | halsmit | ||||||
| Version: | 7.5 (2009.10) | ||||||||
| Hardware: | All | ||||||||
| OS: | All | ||||||||
| Whiteboard: | |||||||||
| i915 platform: | i915 features: | ||||||||
| Attachments: |
|
||||||||
|
Description
Paul Menzel
2010-04-08 00:24:10 UTC
Created attachment 34799 [details]
keymap
(In reply to comment #0) > > I guess it boils down to the questions what X events should be used. For > example XF86AudioPause or Pause and that stop for example should be mapped to > XF86AudioStop. Right. In the keymap, you would have to change for example this line: key <STOP> { [ Cancel ] }; to this: key <STOP> { [ XF86AudioStop ] }; The general approach for a button is as follows (with examples for the Stop Button): - Note the keycode from the xev output state 0x0, keycode 136 (keysym 0xff69, Cancel), - Get the symbolic name from the top of the keymap <STOP> = 136; - Find the keysym section for the key and adapt it key <STOP> { [ XF86AudioStop ] }; Then load the result with xkbcomp your-edited-keymap.xkb ${DISPLAY} The problem is that the multimedia-key of a keyboard would generate the keycode 174 (StopCd), while your RC generates keycode 136 (Stop). The buttons above 255 are not accessible because of bug 11227. On Thu, Apr 08, 2010 at 08:46:41AM -0700, bugzilla-daemon@freedesktop.org wrote: > --- Comment #2 from Dirk Wallenstein <halsmit@t-online.de> 2010-04-08 08:46:40 PDT --- > (In reply to comment #0) > > I guess it boils down to the questions what X events should be used. For > > example XF86AudioPause or Pause and that stop for example should be mapped to > > XF86AudioStop. > > Right. > In the keymap, you would have to change for example this line: > key <STOP> { [ Cancel ] }; > to this: > key <STOP> { [ XF86AudioStop ] }; > > The general approach for a button is as follows (with examples for the > Stop Button): > - Note the keycode from the xev output > state 0x0, keycode 136 (keysym 0xff69, Cancel), > - Get the symbolic name from the top of the keymap > <STOP> = 136; > - Find the keysym section for the key and adapt it > key <STOP> { [ XF86AudioStop ] }; > > Then load the result with > xkbcomp your-edited-keymap.xkb ${DISPLAY} > > The problem is that the multimedia-key of a keyboard would generate the > keycode 174 (StopCd), while your RC generates keycode 136 (Stop). Hm. Is there a list around of IR remote controls and the keycodes they generate? If so, it'd be great to get a set of keymaps that could be fed to the kernel so that everyone (including but not limited to the X server) could get the correct keycodes through evdev. (In reply to comment #3) > Hm. Is there a list around of IR remote controls and the keycodes they > generate? If so, it'd be great to get a set of keymaps that could be fed > to the kernel so that everyone (including but not limited to the X > server) could get the correct keycodes through evdev. Not that I know of. I have read the on the mailing list referred article at http://lwn.net/Articles/364515/ some time ago but haven't followed the topic. The interesting (though partly argued) parts seem to be that LIRC works out the quirks and the kernel provides a high level interface through evdev. Maybe they disambiguate such things like STOP / STOPCD, too. (In reply to comment #3) > On Thu, Apr 08, 2010 at 08:46:41AM -0700, bugzilla-daemon@freedesktop.org > wrote: > > --- Comment #2 from Dirk Wallenstein <halsmit@t-online.de> 2010-04-08 08:46:40 PDT --- > > (In reply to comment #0) > > > I guess it boils down to the questions what X events should be used. For > > > example XF86AudioPause or Pause and that stop for example should be mapped to > > > XF86AudioStop. > > > > Right. > > In the keymap, you would have to change for example this line: > > key <STOP> { [ Cancel ] }; > > to this: > > key <STOP> { [ XF86AudioStop ] }; > > > > The general approach for a button is as follows (with examples for the > > Stop Button): > > - Note the keycode from the xev output > > state 0x0, keycode 136 (keysym 0xff69, Cancel), > > - Get the symbolic name from the top of the keymap > > <STOP> = 136; > > - Find the keysym section for the key and adapt it > > key <STOP> { [ XF86AudioStop ] }; > > > > Then load the result with > > xkbcomp your-edited-keymap.xkb ${DISPLAY} > > > > The problem is that the multimedia-key of a keyboard would generate the > > keycode 174 (StopCd), while your RC generates keycode 136 (Stop). > > Hm. Is there a list around of IR remote controls and the keycodes they > generate? If so, it'd be great to get a set of keymaps that could be fed > to the kernel so that everyone (including but not limited to the X > server) could get the correct keycodes through evdev. I can ask on the LIRC and VDR list for samples if you tell me what you need. The output of `evtest`? This is a mass change of bugs. Bugs assigned to me that haven't been updated in the last 3 years are closed as WONTFIX, because, well, let's at least be honest about it. Please do not re-open unless you have a really good reason to do so (e.g. you're fixing it yourself). If it hasn't been fixed in the last 3 years, it probably won't be fixed anytime soon either. Sorry. |
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.