summaryrefslogtreecommitdiff
path: root/rules
Commit message (Collapse)AuthorAgeFilesLines
* rules: Update hwdb from upstream NUTBastien Nocera2023-04-111-0/+1
|
* rules: Update hwdb from upstream NUTBastien Nocera2023-02-211-0/+1
|
* rules: Update hwdb from upstream NUTBastien Nocera2022-11-161-0/+1
|
* rules: Update hwdb from upstream NUTBenjamin Berg2022-05-161-0/+2
|
* rules: Update udev rules and migrate to use hwdbBenjamin Berg2022-04-013-141/+211
| | | | | | | | | This makes rule matching more efficient. We just need to copy the variables over into the hiddev device so that there is no need to change the C code to match the parent USB device. That said, the change in C wouldn't be that hard either. See https://github.com/networkupstools/nut/pull/1342
* build: Remove autotoolsBastien Nocera2021-09-061-13/+0
|
* build: Support building upower with mesonBenjamin Berg2021-09-021-0/+9
|
* data: Also remove HID++ udev rulesBastien Nocera2021-06-172-11/+1
| | | | Now that HID++ user-space support has been removed.
* linux: Remove support for CSR devicesBastien Nocera2021-01-192-22/+0
| | | | | | | Those devices date back from the mid-2000s. If they still work, and somebody is still interested in having them export their battery status, we would recommend moving this information to the appropriate kernel drivers.
* rules: Reduce our list of HID++ devicesBastien Nocera2019-05-091-5/+0
| | | | | | | | Those devices have been supported in the Linux kernel since at least 3.19, so there's no need to try and support those with our user-space handling. Closes: #3
* rules: Split off HID++ rulesBastien Nocera2019-05-073-15/+16
| | | | They should probably have been split off from the start.
* linux: Don't talk to HID++ devices ourselvesBastien Nocera2017-01-231-0/+2
| | | | If the kernel already extract the battery information out of them.
* Update UPower HID rules - supported devices list1.0Arnaud Quette2015-07-291-2/+29
| | | | | | | As per update on the NUT - Network UPS Tools project, this first patch adds some more supported devices to the rules file Signed-off-by: Richard Hughes <richard@hughsie.com>
* Fix HID rules header, as per discussionsArnaud Quette2015-07-291-2/+8
| | | | Signed-off-by: Richard Hughes <richard@hughsie.com>
* rules: Add support for Logitech G700s/G700 Gaming Mousemuzena2015-07-091-0/+1
| | | | https://bugs.freedesktop.org/show_bug.cgi?id=91270
* rules: support Logitech Unifying in Linux 3.19Peter Wu2015-04-021-0/+3
| | | | | | | | Linux 3.19 changed the way in which devices get registered by introducing a hid-logitech-hidpp module. The driver name therefore needs to be adjusted. Signed-off-by: Peter Wu <peter@lekensteyn.nl>
* Remove obsolete battery recall propertiesBastien Nocera2013-10-147-224/+0
| | | | | | | | The recalls for that broken batch of Sony batteries dates back from 2006. All the batteries that could have been recalled have now been recalled, and somebody particularly interested in supporting them can match the batteries using the old rules file, in a user session or a separate daemon.
* rules: Update and correct Toshiba recall listBastien Nocera2013-10-131-3/+10
| | | | | | | The list wrongly contained PA3465U, had all the batteries in duplicate, and didn't contain a number of affected batteries. https://bugs.freedesktop.org/show_bug.cgi?id=44370
* build: detect udev rules dirTom Gundersen2013-05-071-1/+0
| | | | | | | | | | Udev rules may live in either /lib/udev/rules.d or /usr/lib/udev/rules.d depending on the distro. Remove the heuristic for deciding the dir, use pkgconfig to detect the location and allow it to be set manually. v2: fix specifying --with-udevrulesdir Signed-off-by: Richard Hughes <richard@hughsie.com>
* Add support for Logitech Wireless (NonUnifying) devicesArkadiusz Miśkiewicz2013-03-221-0/+1
| | | | | | | | | | | There are Logitech Wireless devices similar to Unifying ones with the difference that device is paired with single dongle and dongle doesn't support pairing multiple devices. Add support for these. Tested with Wireless Mouse M187 and M185/M225. Signed-off-by: Arkadiusz Miśkiewicz <arekm@maven.pl> Signed-off-by: Richard Hughes <richard@hughsie.com>
* Repair vendor handling for Logitech Unifying devicesArkadiusz Miśkiewicz2013-03-221-0/+1
| | | | | | | | Set proper vendor via udev rules for unifying devices and handle that in code. Signed-off-by: Arkadiusz Miśkiewicz <arekm@maven.pl> Signed-off-by: Richard Hughes <richard@hughsie.com>
* Factor out the Logitech Unifying support to support other devicesRichard Hughes2013-01-101-0/+5
|
* Fix device matching for recent kernelsPeter Hurley2012-12-291-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In recent kernels, hiddev* devices now have class "usbmisc", rather than "usb" (see http://www.spinics.net/lists/linux-usb/msg62276.html). This change translates into a change in SUBSYSTEM matching for hiddev* devices. This fix addresses this for recent kernels while retaining existing behavior. For reference, here is an attribute-walk for a CyberPower CPS 1500C on kernel 3.7.0: [Ubuntu bug #1091702: udev rules fail to match hid devices with new kernels] udevadm info --attribute-walk --path=/devices/pci0000:00/0000:00:1d.2/usb4/4-1/4-1:1.0/usbmisc/hiddev0 Udevadm info starts with the device specified by the devpath and then walks up the chain of parent devices. It prints for every device found, all possible attributes in the udev rules key format. A rule to match, can be composed by the attributes of the device and the attributes from one single parent device. looking at device '/devices/pci0000:00/0000:00:1d.2/usb4/4-1/4-1:1.0/usbmisc/hiddev0': KERNEL=="hiddev0" SUBSYSTEM=="usbmisc" DRIVER=="" looking at parent device '/devices/pci0000:00/0000:00:1d.2/usb4/4-1/4-1:1.0': KERNELS=="4-1:1.0" SUBSYSTEMS=="usb" DRIVERS=="usbhid" ATTRS{bInterfaceClass}=="03" ATTRS{bInterfaceSubClass}=="00" ATTRS{bInterfaceProtocol}=="00" ATTRS{bNumEndpoints}=="01" ATTRS{supports_autosuspend}=="1" ATTRS{bAlternateSetting}==" 0" ATTRS{bInterfaceNumber}=="00" looking at parent device '/devices/pci0000:00/0000:00:1d.2/usb4/4-1': KERNELS=="4-1" SUBSYSTEMS=="usb" DRIVERS=="usb" ATTRS{bDeviceSubClass}=="00" ATTRS{bDeviceProtocol}=="00" ATTRS{devpath}=="1" ATTRS{idVendor}=="0764" ATTRS{speed}=="1.5" ATTRS{bNumInterfaces}==" 1" ATTRS{bConfigurationValue}=="1" ATTRS{bMaxPacketSize0}=="8" ATTRS{busnum}=="4" ATTRS{devnum}=="2" ATTRS{configuration}=="" ATTRS{bMaxPower}==" 50mA" ATTRS{authorized}=="1" ATTRS{bmAttributes}=="c0" ATTRS{bNumConfigurations}=="1" ATTRS{maxchild}=="0" ATTRS{bcdDevice}=="0001" ATTRS{avoid_reset_quirk}=="0" ATTRS{quirks}=="0x0" ATTRS{version}==" 1.10" ATTRS{urbnum}=="36" ATTRS{ltm_capable}=="no" ATTRS{manufacturer}=="CPS" ATTRS{removable}=="unknown" ATTRS{idProduct}=="0501" ATTRS{bDeviceClass}=="00" ATTRS{product}==" CP 1500C" looking at parent device '/devices/pci0000:00/0000:00:1d.2/usb4': KERNELS=="usb4" SUBSYSTEMS=="usb" DRIVERS=="usb" ATTRS{bDeviceSubClass}=="00" ATTRS{bDeviceProtocol}=="00" ATTRS{devpath}=="0" ATTRS{idVendor}=="1d6b" ATTRS{speed}=="12" ATTRS{bNumInterfaces}==" 1" ATTRS{bConfigurationValue}=="1" ATTRS{bMaxPacketSize0}=="64" ATTRS{authorized_default}=="1" ATTRS{busnum}=="4" ATTRS{devnum}=="1" ATTRS{configuration}=="" ATTRS{bMaxPower}==" 0mA" ATTRS{authorized}=="1" ATTRS{bmAttributes}=="e0" ATTRS{bNumConfigurations}=="1" ATTRS{maxchild}=="2" ATTRS{bcdDevice}=="0307" ATTRS{avoid_reset_quirk}=="0" ATTRS{quirks}=="0x0" ATTRS{serial}=="0000:00:1d.2" ATTRS{version}==" 1.10" ATTRS{urbnum}=="50" ATTRS{ltm_capable}=="no" ATTRS{manufacturer}=="Linux 3.7.0-030700-generic uhci_hcd" ATTRS{removable}=="unknown" ATTRS{idProduct}=="0001" ATTRS{bDeviceClass}=="09" ATTRS{product}=="UHCI Host Controller" looking at parent device '/devices/pci0000:00/0000:00:1d.2': KERNELS=="0000:00:1d.2" SUBSYSTEMS=="pci" DRIVERS=="uhci_hcd" ATTRS{irq}=="18" ATTRS{subsystem_vendor}=="0x1028" ATTRS{broken_parity_status}=="0" ATTRS{class}=="0x0c0300" ATTRS{consistent_dma_mask_bits}=="32" ATTRS{dma_mask_bits}=="32" ATTRS{local_cpus}=="00000000,00000000,00000000,00000000,00000000,00000000,00000000,000000ff" ATTRS{device}=="0x268a" ATTRS{msi_bus}=="" ATTRS{local_cpulist}=="0-7" ATTRS{vendor}=="0x8086" ATTRS{subsystem_device}=="0x021e" ATTRS{numa_node}=="-1" ATTRS{d3cold_allowed}=="0" looking at parent device '/devices/pci0000:00': KERNELS=="pci0000:00" SUBSYSTEMS=="" DRIVERS=="" Signed-off-by: Peter Hurley <peter@hurleysoftware.com> Signed-off-by: Richard Hughes <richard@hughsie.com>
* Use git.mk and remove the manual .gitignore filesRichard Hughes2011-07-191-0/+1
|
* Update the list of HID UPS devicesArnaud Quette2010-12-011-2/+6
| | | | Signed-off-by: Richard Hughes <richard@hughsie.com>
* Update the list of supported TrippLite HID Power DevicesJoseph Stockman2010-06-021-0/+20
| | | | Signed-off-by: Richard Hughes <richard@hughsie.com>
* trivial: renamed the udev rule filenamesRichard Hughes2010-01-2110-10/+10
|
* trivial: switch to using the new udev attribute names (no ABI or API break)Richard Hughes2010-01-189-187/+187
|
* Update the list of HID UPSArnaud Quette2009-11-201-0/+19
|
* Fix the toshiba battery recal notices by matching up the double quotes properlyRichard Hughes2009-11-171-6/+6
|
* Bug 24262 – incorrect battery recall warning for Lenovo T61Martin Pitt2009-10-201-0/+3
| | | | | | | According to http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=BATT-LENOVO the Sony batteris are only recalled on some particular models.
* Add another UPS device IDArnaud Quette2009-07-311-2/+2
| | | | Signed-off-by: Richard Hughes <richard@hughsie.com>
* Update list of HID UPS devicesArnaud Quette2009-07-271-24/+29
|
* Move the udev rules to thier own directoryRichard Hughes2009-07-0310-0/+313
View Lorry Controller Status