summaryrefslogtreecommitdiff
path: root/hwdb
AgeCommit message (Collapse)Author
2015-05-21hwdb: add MS Arc Touch Mouse SEPeter Hutterer
https://bugs.freedesktop.org/show_bug.cgi?id=90540
2015-05-20hwdb: add Logitech M570 trackballPeter Hutterer
http://www.logitech.com/en-us/product/wireless-trackball-m570#specs https://bugzilla.redhat.com/show_bug.cgi?id=1217881
2015-05-18hwdb: Add trackpoint sensitivity setting for Thinkpad X230 tabletHans de Goede
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
2015-04-28hwdb: coalesce same pointingstick entries into oneZbigniew Jędrzejewski-Szmek
Multiple models in the same hardware series are likely to have similar specs. We should use organization similar to hwdb/60-evdev.
2015-04-28udev: hwdb: Add trackpoint sensitivity settings for Lenovo X240 and 540pHans de Goede
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.
2015-04-23hwdb: fix typo - "sort by by..." -> "sort by..."Peter Hutterer
2015-04-23hwdb: add HP X1000 DPI infoPeter Hutterer
Device name is PixArt, but it's sold as a HP brand. https://bugs.freedesktop.org/show_bug.cgi?id=90142
2015-04-21hwdb: add Chromebook pixel (2015) resolution fixBenjamin Tissoires
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.
2015-04-21hwdb: add evdev entry for the Lenovo X230 series touchpadBenjamin Tissoires
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.
2015-04-21hwdb: Add entries for the pointingstick on 2 Dell LatitudesHans de Goede
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.
2015-04-21hwdb: Add entries for the trackpoint on 2 ThinkpadsHans de Goede
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.
2015-04-21udev: keyboard-builtin: Add support for setting IBM trackpoint sensitivityHans de Goede
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.
2015-04-21udev: Add hwdb file for setting pointingstick propertiesHans de Goede
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.
2015-04-13hwdb: Fix wireless switch on Dell LatitudeMartin Pitt
It does not generate a release event. https://launchpad.net/bugs/1441849
2015-04-11hwdb: add Samsung ATIV Book 6 / 8Gavin Li
This adds support for the keyboard illumination keys and fixes Fn+F1.
2015-04-11hwdb: set the resolution for a couple of bcm5974 touchpadsPeter Hutterer
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>
2015-04-11udev: builtin-keyboard: add support for EVDEV_ABS_*Peter Hutterer
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.
2015-04-09hwdb: mouse DPI data, Roccat Lua (ROC-11-310)Blaž Tomažič
https://bugs.freedesktop.org/show_bug.cgi?id=89743
2015-03-31hwdb: Update database of Bluetooth company identifiersMarcel Holtmann
2015-03-19hwdb: add HP ProBook 450G0Zbigniew Jędrzejewski-Szmek
https://bugs.freedesktop.org/show_bug.cgi?id=89684
2015-03-16rules: keyboard - prefix "atkbd" match strings like we prefix the "name" stringsKay Sievers
2015-03-16Revert "hwdb: merge atkbd into platform matches"David Herrmann
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.
2015-03-16rules: keyboard - remove "platform" from commentsKay Sievers
2015-03-16hwdb: merge atkbd into platform matchesDavid Herrmann
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.
2015-03-16hwdb: convert to generic input-modalias matchesDavid Herrmann
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.
2015-03-12hwdb: updateKay Sievers
2015-03-06hwdb: add Lenovo W451 to TOUCHPAD_HAS_TRACKPOINT_BUTTONS listPeter Hutterer
2015-03-05hwdb: add Logitech G5 Laser MouseJonathon Gilbert
2015-03-04hwdb: fix Dell XPS12 9Q33 key nameZbigniew Jędrzejewski-Szmek
https://bugs.freedesktop.org/show_bug.cgi?id=84437
2015-03-04hwdb: add pnpid for the T450s touchpadPeter Hutterer
https://bugs.freedesktop.org/show_bug.cgi?id=89411
2015-02-27hwdb: add sdio identifiers for Broadcom WLAN cardsArend van Spriel
This patch adds the sdio identifiers known to be supported by the brcmfmac open-source driver.
2015-02-25hwdb: Update database of Bluetooth company identifiersMarcel Holtmann
2015-02-19hwdb: fix ThinkPad X* Tablet special keysLubomir Rintel
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
2015-02-16hwdb: Update database of Bluetooth company identifiersMarcel Holtmann
2015-02-16hwdb: updateLennart Poettering
2015-02-16hwdb: fix syntaxLennart Poettering
2015-02-14hwdb: Microsoft Microsoft 3-Button MouseLukas Märdian
https://bugs.freedesktop.org/show_bug.cgi?id=89149
2015-02-13hwdb: update name databasesLennart Poettering
2015-02-10keymap: Add microphone mute keymap for several HP laptopsHui Wang
On these several HP laptops, the microphone mute hotkey is "Fn+F8" and the scancode for this hotkey is 0x81, but this scancode was mapped to fn_esc in the HP generic keymap section. To fix this problem, we add a machine specific keymap section to add the correct keymap rule. BugLink: https://bugs.launchpad.net/bugs/1409721 BugLink: https://bugs.launchpad.net/bugs/1334968 Signed-off-by: Hui Wang <hui.wang@canonical.com>
2015-02-04hwdb: Bind "toolbox" buttons to the Windows keyBastien Nocera
One would expect pressing the button to go to an overview / show applications mode, we thus map it to leftmeta, the Windows key. See https://bugzilla.gnome.org/show_bug.cgi?id=658602#c17
2015-02-02hwdb: Update database of Bluetooth company identifiersMarcel Holtmann
2015-01-29hwdb: add a touchpad hwdbPeter Hutterer
Currently used to tag devices in the new Lenovo *50 series and the X1 Carbon 3rd. These laptops re-introduced the physical trackpoint buttons that were missing from the *40 series but those buttons are now wired up to the touchpad. The touchpad now sends BTN_0, BTN_1 and BTN_2 for the trackpoint. The same button codes were used in older touchpads that had dedicated scroll up/down buttons. Input drivers need to work around this and thus know what they're dealing with. For the previous gen we introduced INPUT_PROP_TOPBUTTONPAD in the kernel, but the resulting mess showed that these per-device quirks should really live in userspace. The list currently includes the X1 Carbon 3rd PNPID, others will be added as get to know which PNPID they have.
2015-01-17hwdb: restore comments about MSI devicesMaxim Mikityanskiy
Some time ago 95-keymap.rules was replaced by 60-keyboard.hwdb. Original comments for MSI laptops (that were in 95-keymap.rules) were removed, but I think they are important for understanding what's going on. https://bugs.freedesktop.org/show_bug.cgi?id=88412
2015-01-16hwbd: add click angle for the Logitech M325Peter Hutterer
This device has 18 stops per rotation == 20 degree angle. Advertised as "Micro-precise scrolling"
2015-01-15hwdb: add MOUSE_WHEEL_CLICK_ANGLE as propertyPeter Hutterer
Most mice have a wheel click angle of 15 degrees, i.e. 24 clicks per full wheel rotation. Some mice, like the Logitech M325 have a larger angle. To allow userspace to make use of that knowledge, add a property to the hwdb. This allows for better predictive scrolling. e.g. a mouse that has a smaller click angle will scroll faster, with this value you can accommodate this where needed. Likewise, using "half turn of the wheel" or "full turn of the wheel" as a UI element becomes possible. This addition is mainly driven by libinput 0.8, having the angle enables libinput to provide an API that distinguishes between a physical distance (like touchpad scrolling does) and discrete steps (wheel clicks). Callers can choose what they prefer based on the device.
2015-01-09hwdb: add Kay's Laser Mouse to the dpi databaseLennart Poettering
2015-01-09hwdb: add missing line between the G400 entriesPeter Hutterer
Error, DATA expected but got 'mouse:usb:v046dpc24c:name:Logitech G400s Optical Gaming Mouse:' in '/etc/udev/hwdb.d/70-mouse.hwdb': Error, MATCH expected but got ' MOUSE_DPI=400@1000 *800@1000 2000@1000 4000@1000' in '/etc/udev/hwdb.d/70-mouse.hwdb': Introduced in 6366e349
2015-01-09hwdb: note that we care about the maximum frequency in MOUSE_DPIPeter Hutterer
Devices with dynamic frequency scaling adjust the frequency as needed. For those we only care about the maximum frequency, not the various in betweens. https://bugs.freedesktop.org/show_bug.cgi?id=87435#c8
2015-01-08hwdb: adjust max frequency of Logitech RX 250Zbigniew Jędrzejewski-Szmek
https://bugs.freedesktop.org/show_bug.cgi?id=87435
2015-01-07hwdb: mouse DPI data, Logitech Gaming Mouse G400Jonas Ådahl