Age | Commit message (Collapse) | Author |
|
DDC_DEVICEs are control points for high-end monitors such as the
HP DreamColor. The DDC/CI interface allows userspace applications
to upload custom colorspaces and interact with the display without
using the monitor hardware controls.
|
|
We should do only do classes of devices, not individual pieces
of hardware.
There is no way for us to manage this in the long term, and it needs
to be thought through what we want here, but it surely isn't a list of
smartphones in the udev source tarball installed on all systems.
|
|
|
|
|
|
|
|
|
|
|
|
When a custom rule sets ACL_MANAGE to 0 to disable ACL management for a
particular device, handle this as "disabled", by explicitly checking against
"1" instead of "nonempty".
Thanks to RafaĆ Rzepecki for pointing this out.
|
|
https://qa.mandriva.com/show_bug.cgi?id=55836
|
|
|
|
|
|
There doesn't seem to be any special class for their developer
interface, so match by Vendor and Device id like we do for things
like fingerprint readers.
This is better than their current 0666 suggestion <g>
Signed-off-by: Scott James Remnant <scott@ubuntu.com>
|
|
ID_CLASS is deprecated for input devices. Use new ID_INPUT_JOYSTICK instead.
|
|
|
|
User needs read-write access to joystick devices in order to use force
feedback features.
|
|
gnupg, psc-lite, etc. will ship udev rules for supported smartcard readers
soon. Add the ACL management bit.
Thanks to Michael Bienia!
|
|
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.
|
|
The build of extras with larger external dependencies is wrapped in:
--enable-extras
|