Bug 1172669

Summary: Update hal-info remapping rules for Toshiba laptops
Product: Red Hat Enterprise Linux 6 Reporter: Benjamin Tissoires <btissoir>
Component: hal-infoAssignee: Benjamin Tissoires <btissoir>
Status: CLOSED ERRATA QA Contact: Desktop QE <desktop-qa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.6CC: mbarta, mboisver, tpelka, vsharapo
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: hal-info-20090716-5.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-07-22 05:36:03 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1146711    
Attachments:
Description Flags
30-keymap-module-toshiba-acpi.fdi none

Description Benjamin Tissoires 2014-12-10 14:20:07 UTC
Description of problem:

To support the various Fn-keys found on the latest Toshiba laptops, we need to introduce a remapping from the provided kernel keycode to a keycode compatible with X.

For instance KEY_TOUCHPAD_TOGGLE has to be remapped to F21 for X to be able to deliver Xf86TouchpadToggle.


Version-Release number of selected component (if applicable):
6.6

How reproducible:
Always

Steps to Reproduce:
1. run xev
2. hit the corresponding touchpad toggle key 
3. see the xev output

Actual results:

xev does not show Xf86TouchpadToggle

Expected results:

xev should show Xf86TouchpadToggle

Additional info:

Comment 1 Benjamin Tissoires 2014-12-18 15:41:59 UTC
Created attachment 970629 [details]
30-keymap-module-toshiba-acpi.fdi

Attached is the policy key mapping required for the Toshiba laptops.
Only Touchpad toggle needs to be remapped from what I can see on the keyboard.

Comment 7 errata-xmlrpc 2015-07-22 05:36:03 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-1268.html