Age | Commit message (Collapse) | Author |
|
|
|
|
|
Automounters may need information like this to e.g. allow unprivileged
applications to mount filesystems from a CF card but not from
other ATA devices. See https://bugzilla.redhat.com/show_bug.cgi?id=734191
Signed-off-by: David Zeuthen <davidz@redhat.com>
|
|
This keyboard have 16 "multimedia" keys plus a "4-way turbo scroll pad" which
is essentially a round up/down/left/right button. Unfortunately most of these
keys emit non-standard scancodes in a range 495-508 which does not make any
sense. I tried to remap those to the best of my knowledge.
Note the keyboard comes up as two event devices, second one is multimedia
keys, so I ended up adding ENV{ID_USB_INTERFACE_NUM}=="01" to avoid
unnecessary initialization of the "main" keyboard.
|
|
New mappings were needed when the mechanical keyboard was
introduced, and GNOME was made a peer to the sugar desktop.
see http://lists.laptop.org/pipermail/devel/2010-July/029384.html
|
|
On a ThinkPad X220 there is a microphone mute button which generates
ACPI event "ibm/hotkey HKEY 00000080 0000101b". As there is no key like
"micmute", map it to prog2.
|
|
Prefer reading keymaps from /etc/udev/keymaps/ so that it's easy to just
locally fix a key or two by copying the existing keymap file from
/lib/udev/keymaps/. This works similarly to udev rules.
http://bugs.debian.org/556045
|
|
https://launchpad.net/bugs/637695
|
|
|
|
|
|
|
|
Skip event devices which don't have ID_INPUT_KEY set, to avoid running the long
list of rules more than necessary.
Note that we don't limit ourselves to ID_INPUT_KEYBOARD, as we might want to
fix extra buttons on e. g. fancy mouses or tablet screens, too.
|
|
|
|
|
|
We have not shipped it anyway, and is not necessary any more these days.
|
|
We need to tag the power input button for multi-seat.
|
|
|
|
|
|
|
|
https://bugzilla.redhat.com/show_bug.cgi?id=444440
|
|
Thanks to Paolo Gherpelli <gherpelli@libero.it>!
|
|
|
|
|
|
Signed-off-by: Martin Pitt <martin.pitt@ubuntu.com>
|
|
MSI machines have some different vendor name, and the refix on those vendor
name are "MICRO-STAR" or "Micro-Star". So, merge the original two rules to
one, and use asterisk on dmi vendor name for support more MSI machines.
Tested on MSI U270 netbook.
Signed-off-by: Martin Pitt <martin.pitt@ubuntu.com>
|
|
http://bugs.debian.org/629647
|
|
Show an error message so that it's possible to determine why the
HDIO_GET_IDENTITY ioctl has failed.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Lun numbers < 256 are displayed as "lun-x". Lun numbers >= 256 use
the lun number format previously used in fibre channel by-path
links, 0xabcd012300000000. This lun numbering scheme is implemented
for sas, fibre channel, iscsi.
I want it to be clearly understood that this patch changes the
/dev/disk/by-path names for fc devices. Here is an example of the
change:
Old: pci-0000:0c:00.1-fc-0x204700a0b81130aa:0x00fa000000000000
New: pci-0000:0c:00.1-fc-0x204700a0b81130aa-lun-250
|
|
http://bugs.debian.org/623153
|
|
|
|
|
|
|
|
|
|
The XT2 has a rocker (up/down/enter) and back button on the side
in tablet mode, none of which work currently. Add entries for
these keys.
There is some overlap here with scan codes used in other Dell
models, so these buttons are put in a new file specific to this
model.
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
Signed-off-by: Martin Pitt <martin.pitt@ubuntu.com>
|
|
When the CD tray door is locked and the hardware eject button is pressed, newer
kernels (2.6.38+) will send out a change event with a DISK_EJECT_REQUEST==1
property. Do not run cdrom_id and blkid in this case, as the media state and
contents does not change, and this only needlessly spins up the drive again
right before ejection.
|
|
Acer Aspire One ZG8's bluetooth HW key emit 0xD9 scancode, it must map
to KEY_BLUETOOTH like Acer Aspire 5720. So, add rule for Acer Aspire One
ZG8 use acer-aspire_5720 keymap.
Tested on Acer Aspire One ZG8 netbook.
Signed-off-by: Lee, Chun-Yi <jlee@novell.com>
Signed-off-by: Martin Pitt <martin.pitt@ubuntu.com>
|
|
Reading of keymaps is aborted when EINVAL is returned from EVIOCGETKEYCODE.
Scan codes are not always continuous ranges of values starting at 0, so this
can result in not getting the full keymap for a device. Instead, continue
processing if EINVAL is returned.
|
|
|
|
|
|
|
|
We previously only tested the "key" capabilities for keys between 0 and 255 to
determine ID_INPUT_KEY. If there are none, also check for keys in the upper
block (KEY_OK/0x160 to KEY_TOUCHPAD_OFF/0x214).
|