summaryrefslogtreecommitdiff
path: root/hwdb
Commit message (Collapse)AuthorAgeFilesLines
* hwdb: Update database of Bluetooth company identifiersMarcel Holtmann2015-07-071-0/+66
|
* hwdb: updateKay Sievers2015-07-053-205/+613
|
* Revert "hwdb: add a touchpad hwdb"Peter Hutterer2015-06-261-43/+0
| | | | | | | | | | | | The main purpose of this hwdb was to tag touchpads that have the physical trackstick buttons wired to the touchpad (Lenovo Carbon X1 3rd, Lenovo *50 series). This hwdb is not required on kernels 4.0 and above, the kernel now re-routes button presses through the trackstick's device node. Userspace does not need to do anything. See kernel commit cdd9dc195916ef5644cfac079094c3c1d1616e4c. This reverts commit 001a247324b44c0e0b8fdba41a6fc66e7465b8b6.
* hwdb: move a couple of entries to expected sort orderPeter Hutterer2015-06-231-12/+12
|
* hwdb: add Logitech MX RevolutionPeter Hutterer2015-06-231-0/+4
|
* hwdb: update databases from upstreamLennart Poettering2015-06-173-382/+868
|
* hwdb: Update database of Bluetooth company identifiersMarcel Holtmann2015-06-151-0/+39
|
* hwdb: add support for Alienware graphics amplifierMario Limonciello2015-06-141-0/+6
| | | | | | | | | | Unplugging and plugging in the cable will create various scancodes on the keyboard controller. Userspace within X should be able to interact with these to show interesting messages. Assign them to generic prog1/prog2. (David: add comment to hwdb explaining that these keycodes are reserved)
* keymap: Add Samsung NP350V and NP670Zdslul2015-06-101-0/+2
| | | | | | typo keymap: Add Samsung NP350V and NP670Z
* hwdb: update Logitech's unifying receiver devicesPeter Hutterer2015-06-101-0/+7
| | | | | | | Since 3.19, the devices have the proper vid/pid and the model number in the name. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
* hwdb: add Logitech TrackMan Marble Wheel USBPeter Hutterer2015-06-091-0/+2
| | | | | DPI is guesswork, no specs found on the web and calculating DPIs on a trackball is tedious.
* hwdb: add Apple MagicMouse entryPeter Hutterer2015-06-041-0/+10
|
* hwdb: updateKay Sievers2015-06-022-84/+285
|
* hwdb: Update database of Bluetooth company identifiersMarcel Holtmann2015-06-021-1/+160
|
* update hardware databasesLennart Poettering2015-05-213-377/+2540
|
* hwdb: add MS Arc Touch Mouse SEPeter Hutterer2015-05-211-0/+4
| | | | https://bugs.freedesktop.org/show_bug.cgi?id=90540
* hwdb: add Logitech M570 trackballPeter Hutterer2015-05-201-0/+4
| | | | | http://www.logitech.com/en-us/product/wireless-trackball-m570#specs https://bugzilla.redhat.com/show_bug.cgi?id=1217881
* hwdb: Add trackpoint sensitivity setting for Thinkpad X230 tabletHans de Goede2015-05-181-0/+2
| | | | | This model needs the trackpoint sensitivity to be boosted to not be too slow to be usable, see: https://bugzilla.redhat.com/show_bug.cgi?id=1200717
* hwdb: coalesce same pointingstick entries into oneZbigniew Jędrzejewski-Szmek2015-04-281-14/+10
| | | | | Multiple models in the same hardware series are likely to have similar specs. We should use organization similar to hwdb/60-evdev.
* udev: hwdb: Add trackpoint sensitivity settings for Lenovo X240 and 540pHans de Goede2015-04-281-0/+10
| | | | | | | Like the T440s these need the sensitity to be set significantly higher then the default of 128 for the trackpoint to be usable. Like with the T440s 200 seems to be a good value to get a reasonable but not too high sensitivity.
* hwdb: fix typo - "sort by by..." -> "sort by..."Peter Hutterer2015-04-232-2/+2
|
* hwdb: add HP X1000 DPI infoPeter Hutterer2015-04-231-0/+8
| | | | | | Device name is PixArt, but it's sold as a HP brand. https://bugs.freedesktop.org/show_bug.cgi?id=90142
* hwdb: add Chromebook pixel (2015) resolution fixBenjamin Tissoires2015-04-211-0/+11
| | | | | | | | The atmel driver sets a default resolution of 20 for each touchpads it creates. On this model, 10 is more appropriate. The resolution is not set for the touchscreen by the kernel, so match the name to both touchpad and touchscreen.
* hwdb: add evdev entry for the Lenovo X230 series touchpadBenjamin Tissoires2015-04-211-0/+16
| | | | | | The Lenovo X230 advertize a vertical resolution of 136, which gives a true size of 31 mm. The actual physical size of the touchpad is 40 mm, so override the resolution to 100.
* hwdb: Add entries for the pointingstick on 2 Dell LatitudesHans de Goede2015-04-211-0/+12
| | | | | | The pointingstick of the Dell Latitude E6400 is somewhat slow by default, whereas the pointingstick of the Dell Latitude D620 is much too fast by default, set POINTINGSTICK_CONST_ACCEL for both of them to adjust for this.
* hwdb: Add entries for the trackpoint on 2 ThinkpadsHans de Goede2015-04-211-0/+17
| | | | | | | | | | | Lenovo has changed the sensitivity of the trackpoint on the x240 / T440s / T540 generation of Thinkpads, making them somewhat insensitive by default, add a hwdb entry to tweak the sensitivity setting. The ThinkPad X200s is way way too slow by default and unless you push the trackpoint quite hard only sends delta events in the 1-2 range, tweak the sensitivity to make it send a wider range of deltas and apply a const accel factor to make it have a more reasonable speed by default.
* udev: keyboard-builtin: Add support for setting IBM trackpoint sensitivityHans de Goede2015-04-211-0/+12
| | | | | | | | | | | | | | IBM / Lenovo trackpoints allow specifying a sensitivity setting through a ps/2 command, which changes the range of the deltas sent when using the trackpoint. On some models with normal usage only deltas of 1 or 2 are send, resulting in there only being 2 mouse cursor movement speeds, rather than the expected fluid scale. Changing the sensitivity to a higher level than the bootup default fixes this. This commit adds support for setting a POINTINGSTICK_SENSITIVITY value in hwdb to allow changing the sensitivity on boot through udev / hwdb.
* udev: Add hwdb file for setting pointingstick propertiesHans de Goede2015-04-211-0/+58
| | | | | | | | | | | | There is quite a wide spread in the delta events generated by pointingsticks, some generate deltas of 1-2 under normal use, while others generate deltas from 1-20. This commit adds a hwdb file which allows specifying a per model POINTINGSTICK_CONST_ACCEL value which can be used by the userspace input stack to normalize the deltas so that all pointingsticks get the same feeling ootb. The hwdb matching re-uses the existing 60-evdev.rules.
* hwdb: Fix wireless switch on Dell LatitudeMartin Pitt2015-04-131-0/+1
| | | | | | It does not generate a release event. https://launchpad.net/bugs/1441849
* hwdb: add Samsung ATIV Book 6 / 8Gavin Li2015-04-111-0/+6
| | | | | This adds support for the keyboard illumination keys and fixes Fn+F1.
* hwdb: set the resolution for a couple of bcm5974 touchpadsPeter Hutterer2015-04-111-0/+40
| | | | | | | | | | | | Verified for the 5,1 Macbook, the others are guesses based on the list of supported devices of the moshi trackpad protector. http://www.moshi.com/trackpad-protector-trackguard-macbook-pro#silver Resolution calculated based on the min/max settings set in the kernel driver, divided by the physical size. This is probably slightly off, but still better than no resolution at all. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
* udev: builtin-keyboard: add support for EVDEV_ABS_*Peter Hutterer2015-04-112-180/+217
| | | | | | | | | | | | | | | | | | | | | | | | | Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
* hwdb: mouse DPI data, Roccat Lua (ROC-11-310)Blaž Tomažič2015-04-091-0/+9
| | | | https://bugs.freedesktop.org/show_bug.cgi?id=89743
* hwdb: Update database of Bluetooth company identifiersMarcel Holtmann2015-03-311-0/+36
|
* hwdb: add HP ProBook 450G0Zbigniew Jędrzejewski-Szmek2015-03-191-0/+2
| | | | https://bugs.freedesktop.org/show_bug.cgi?id=89684
* rules: keyboard - prefix "atkbd" match strings like we prefix the "name" stringsKay Sievers2015-03-161-135/+135
|
* Revert "hwdb: merge atkbd into platform matches"David Herrmann2015-03-161-138/+143
| | | | | | | | | This reverts commit ba76ee29bc02879fb42c048132af8889b00220d5. As it turns out, we need to match on driver=atkbd to not load the fixups on any plugged USB devices. That is, whenever you use "name:<name>:dmi:<dmi>" style matches, you better provide a name or you're screwing things up.
* rules: keyboard - remove "platform" from commentsKay Sievers2015-03-161-1/+1
|
* hwdb: merge atkbd into platform matchesDavid Herrmann2015-03-161-144/+139
| | | | | | | | | | | | | | | | Currently, we always run hwdb 'keyboard:name:$attr{name}:$attr{[dmi/id]modalias}' as last step to match keyboards. Therefore, if nothing else matched so far, we still try the device-name+dmi combination. However, we have a special atkbd rule which is only run for atkbd as: hwdb 'keyboard:$attr{[dmi/id]modalias}' This is redundant, as we already pass the same information to hwdb in the last fallback step. This patch converts the hwdb "keyboard:dmi:*" matches to "keyboard:name:*:dmi:*" matches and drops the redundant rule.
* hwdb: convert to generic input-modalias matchesDavid Herrmann2015-03-161-18/+20
| | | | | | | | | | | | | | | | There is no reason to match on usb-modaliases, if we can use the input-modalias to achieve the same. This commit changes the keyboard-lookups to not be restricted to USB, but pass all modaliases to the hwdb. Furthermore, we convert all usb:* matches to input:* matches, thus getting rid of any ambiguity if multiple usb devices are chained (or a bluetooth device / etc. is on top). Note that legacy keyboard:usb:* matches are still supported, but deprecated. If possible, please use keyboard:input:* matches instead. This is a required step to make other input devices work with 60-keyboard.hwdb. Other bus-types are often chained on usb and we want to avoid any ambiguity here if we incorrectly match on a USB hub.
* hwdb: updateKay Sievers2015-03-124-334/+1060
|
* hwdb: add Lenovo W451 to TOUCHPAD_HAS_TRACKPOINT_BUTTONS listPeter Hutterer2015-03-061-0/+2
|
* hwdb: add Logitech G5 Laser MouseJonathon Gilbert2015-03-051-0/+2
|
* hwdb: fix Dell XPS12 9Q33 key nameZbigniew Jędrzejewski-Szmek2015-03-041-1/+1
| | | | https://bugs.freedesktop.org/show_bug.cgi?id=84437
* hwdb: add pnpid for the T450s touchpadPeter Hutterer2015-03-041-0/+2
| | | | https://bugs.freedesktop.org/show_bug.cgi?id=89411
* hwdb: add sdio identifiers for Broadcom WLAN cardsArend van Spriel2015-02-271-0/+10
| | | | | This patch adds the sdio identifiers known to be supported by the brcmfmac open-source driver.
* hwdb: Update database of Bluetooth company identifiersMarcel Holtmann2015-02-251-0/+42
|
* hwdb: fix ThinkPad X* Tablet special keysLubomir Rintel2015-02-191-2/+1
| | | | | | | | | | | | | | | ThinkPad tablet firmware has DMI product name and version reversed: Handle 0x0001, DMI type 1, 27 bytes System Information Manufacturer: LENOVO Product Name: 7762AS1 Version: ThinkPad X61 Tablet Serial Number: LKZCDH2 UUID: 6ADBC681-4FC9-11CB-844F-B47CB9210BE2 Wake-up Type: Power Switch SKU Number: Not Specified Family: ThinkPad X61 Tablet
* hwdb: Update database of Bluetooth company identifiersMarcel Holtmann2015-02-161-0/+57
|
* hwdb: updateLennart Poettering2015-02-162-15/+921
|
View Lorry Controller Status