| Age | Commit message (Collapse) | Author |
|---|
|
Since gtk-mkhtml is executed in a sub-directory of the build directory, and
make does not know of that, the $(buildir) variable will still be "." and
the $(srcdir) will not properly be found. For this reason, use the absolute
variants for the two functions, which won't be changing.
|
|
Since the check-keymaps.sh script checks for validity the source directory
and the Makefile.am file, instead of running it during user-oriented “make
check”, run it during developed-oriented “make distcheck”.
An invalid keymap will abort the execution which will prevent shipping
an incomplete Makefile.am.
To properly support out-of-source builds, pass as single parameter to the
test the path to the source directory.
|
|
The Introspection rules are not tested yet; more touch-ups have been made
for them.
|
|
Slight adjustment around the tests and the rules for the new working
directory.
|
|
|
|
Instead of using multiple recursive Makefile.am files, use a single
Makefile.am that sets and builds all the basic suite of libraries and
binaries for udev. This reduces the number of files in the source tree, and
also reduces drastically the build time when using parallel-make.
With this setup, all the compile steps will be executed in parallel, and
just the linking stage will be (partially) serialised on the libraries
creation.
|
|
See https://launchpad.net/bugs/407940
|
|
Reported by Dirk Thierbach <dthierbach@gmx.de> on hal ML.
|
|
|
|
User needs read-write access to joystick devices in order to use force
feedback features.
|
|
|
|
We must never access random devices in /dev which do not belong to
the event we are handling. Hard-coding /dev/hidrawX, and looping over all
devices is absolutely not acceptable --> hook into hidraw events.
We can not relay on (rather random) properties merged into the parent
device by earlier rules --> use libudev to find the sibling device
with a matching interface.
Libusb does not fit into udev's use case. We never want want to scan
and open() all usb devices in the system, just to find the device
we are already handling the event for --> put all the stupid scanning
into a single function and prepare for a fixed libusb or drop it later.
|
|
|
|
The keymap table has some holes in it, which caused the interactive mode to
crash for unknown keys. In these cases, print the numeric key code instead.
|
|
What's odd is that this is a huawei modem, not an option modem, so one would
expect it to work better with usb_modeswitch and it's -H (huawei) mode - but
that's not the case, I've tested that as well.
https://launchpad.net/bugs/401655
|
|
|
|
|
|
|
|
|
|
Reported on hal ML by Sergey Astanin <s.astanin@gmail.com>.
|
|
|
|
https://launchpad.net/bugs/48547
|
|
https://launchpad.net/bugs/35382 shows that may Evo N* models share the same
keymap, so generalize the existing rule.
|
|
https://launchpad.net/bugs/20223
|
|
|
|
Do not complain about missing keymap files when giving scancode/keyname pairs
on the keymap command line in the rules.
|
|
Remove key map files which have only one override. Instead, use keymap tools'
new feature of specifying scancode/keyname pairs directly at the command line.
Also add a comment to 95-keymap.rules about how to specify key mappings in the
rules.
|
|
This avoids having to create and parse an entire keymap file for cases where
just one or two keys have to be remapped.
|
|
Do not duplicate help strings, and add missing calling variant for
interactivity.
|
|
https://launchpad.net/bugs/198530
|
|
Reported in https://launchpad.net/bugs/400921
|
|
Reported on https://launchpad.net/bugs/400252
|
|
Reported as hal-info patch by Németh Márton <nm127@freemail.hu> on hal ML.
|
|
The callers of prepend_vendor_model both expect < 0 to be returned on
error and the index to be returned otherwise. However
prepend_vendor_model actually returns 1 on error. Fix this by correctly
returning -1.
Older kernels (before e5b3cd42: "SCSI: sanitize INQUIRY strings")
truncated the model field in sysfs (or propagated bad results from the
target) to less than the expected/required 16 characters which meant
that the SCSI id was mangled into:
# /sbin/scsi_id -g -s /block/sdg
S146cee20VIRTUAL-DISK
when it should have been:
# /sbin/scsi_id -g -s /block/sdg
SIET VIRTUAL-DISK 146cee20
Notice how the serial number has been pasted over the vendor+model at
index 1 instead of being added at the end.
In the former case:
# cat /sys/devices/platform/host5/session1/target5:0:0/5:0:0:1/model | od -t c -t x1
0000000 V I R T U A L - D I S K \n
56 49 52 54 55 41 4c 2d 44 49 53 4b 0a
But it should have been:
# cat /sys/devices/platform/host5/session1/target5:0:0/5:0:0:1/model | od -t c -t x1
0000000 V I R T U A L - D I S K
56 49 52 54 55 41 4c 2d 44 49 53 4b 20 20 20 20
0000020 \n
0a
Signed-off-by: Ian Campbell <ijc@hellion.org.uk>
|
|
|
|
gnupg, psc-lite, etc. will ship udev rules for supported smartcard readers
soon. Add the ACL management bit.
Thanks to Michael Bienia!
|
|
We currently search /lib/firmware and /lib/firmware/`uname -r` for firmware
files for device drivers loaded by the currently running kernel. These are
often packaged by distributions as a subpackage of the kernel or as a
separate package containing firmware. But these files cannot easily be
updated by third parties or sysadmins independently of that package.
This patch causes udev to also look for firmware files in an "updates"
directory, which is almost identical in purpose to the module-init-tools
"updates" directories insomuch as local changes can go in here and will
take preference over firmware supplied by any distribution.
|
|
|
|
ID_SERIAL is the full serial number used for the links, ID_SERIAL_SHORT
is the device serial number.
|
|
|
|
The previous rules just checked bInterfaceProtocol but not the actual device
and interface class. This caused the hci rules to be applied for Dell USB hubs
and attached input devices like keyboards and mouses as well, breaking them
completely.
Tighten the match to also check device and interface class/subclass.
https://launchpad.net/bugs/392144
|
|
|
|
Recent commit 3b338b6 moved findkeyboards from /usr/share/udev to /lib/udev/.
Update documentation accordingly.
|
|
hplip tools need user access to the devices for checking ink levels and
user-level configuration. This was formerly done with hal FDIs.
As per discussion with Till Kamppeter.
|
|
|
|
These are mostly dummy man pages, without real content, some even
outdated. None of these tools are part of any offered public interface,
and they should not pretend to be by offering a man page.
|
|
findkeyboards is now in /usr/share/udev/ after the migration to udev proper.
Update path in README.keymap.txt.
|
|
|
|
|
|
Fn+F5 was previously assigned to "radio" which is fairly useless under X.
Switch it to "wlan".
Reported in http://bugs.debian.org/504643
|
