Age | Commit message (Collapse) | Author |
|
Thanks Aleksander Kowalski <aleksander.kowalski.1@gmail.com>!
|
|
https://launchpad.net/bugs/1271163
|
|
https://launchpad.net/bugs/1272658
|
|
Thanks to Stefan Nagy <public@stefan-nagy.at>.
|
|
|
|
https://launchpad.net/bugs/665918
|
|
https://bugs.freedesktop.org/show_bug.cgi?id=71929
|
|
keyboardbrightnessup/down are not even real keys.
https://bugs.freedesktop.org/show_bug.cgi?id=72311
|
|
https://bugs.freedesktop.org/show_bug.cgi?id=72311
|
|
The Key codes didn't match with the described key. Also the key
identifier strings were missing. I hope I chose appropriate ones.
https://bugs.freedesktop.org/show_bug.cgi?id=70296
|
|
Move common keys into generic Acer table, and factorize the model specific
exceptions.
|
|
Signed-off-by: Martin Pitt <martinpitt@gnome.org>
|
|
https://launchpad.net/bugs/1245189
|
|
So that they are together in the file.
|
|
It appears that it's not really the 900 vs. 940 or the X3 vs X4, but the
A/B/C/D suffix after that which makes the difference between the keymaps. On a
NP900X3C-A04RU you get
MODALIAS=dmi:bvn*:bvr*:bd*:svnSAMSUNGELECTRONICSCO.,LTD.:pn900X3C/900X3D/900X4C/900X4D:*
So change the matches to use AB vs. CDG as the differentiator.
Thanks to Anatoly Markov for reporting and testing!
|
|
https://launchpad.net/bugs/1229936
|
|
These days, F21/F22/F23 mean Touchpad toggle/on/off. Clean up other assignments
to that from ancient times which belong to keys like "Auto Brightness" (which
doesn't have a keycode and is usually hardwired) or some "launch vendor tool"
key.
https://bugs.freedesktop.org/show_bug.cgi?id=62953
|
|
Also consolidate the wlan key into the "all Samsung" rule to avoid repetition.
Thanks to Mauro Carvalho Chehab!
https://bugzilla.redhat.com/show_bug.cgi?id=989103
|
|
|
|
Contributed by Guillermo Dominguez Duarte <guillermod84@gmail.com>.
|
|
We need to override the TOUCHPAD_TOGGLE to F21 to make it useful under X, as
for other models.
|
|
Without this, the hwdb trie gets mis-sorted to match the more specific rules
first, as ":pvr" is lexicographically after ":pn". So ensure that all our
matches have some ":pn" match to avoid this trap.
|
|
We actually want to match the product name, "pn:" makes no sense.
|
|
Spaces get dropped from DMI modaliases. Replace them with '*' to make them
robust against future changes in space escaping.
|
|
Spaces are dropped from vendor and product names in DMI modaliases, so a match
like "svnDell Inc.:" will never happen. Also, some machines use "Dell", some
"Dell Inc", some "Dell Inc.", so just match on "Dell*" to avoid all these
traps.
https://launchpad.net/bugs/1218433
|
|
Don't use "KEYBOARD_KEY_xx=!" assignments (i. e. only enabling force-release)
if more general matches already explicitly set a key code before, to not
override the previously set value.
https://launchpad.net/bugs/1218433
|
|
By Albrecht Kolthoff <kolthoff@gmx.net> via linux-hotplug@.
|
|
https://launchpad.net/bugs/1203853
|
|
I'm using Ubuntu 13.04 on a Samsung Series 5 computer and found that that
Fn hotkeys does not work.
|
|
Information supplied by Ludvig <enthymeme@lavabit.com>.
|
|
|
|
<dvdhrm> kay, hwdb/60-keyboard.hwdb line 147 it says KEYBOARD_KEY_ee=screenlock"
with a " at the end. I guess that's a typo?
|
|
KEY_ definitions
|
|
https://bugs.freedesktop.org/show_bug.cgi?id=67651
|
|
https://bugs.freedesktop.org/show_bug.cgi?id=66178
|
|
|
|
Add missing '='.
|
|
These add back are the remaining 3 udev keymap rules which used name based
instead of ID based matching.
|
|
|
|
|
|
|
|
|
|
Do not enable/install it now, until we switch over from the current
keymap tool.
|