Bug 86257 - RFE: hwdb extension for tracking if certain keyboard models have CapsLock/NumLock LED
Summary: RFE: hwdb extension for tracking if certain keyboard models have CapsLock/Num...
Status: RESOLVED WONTFIX
Alias: None
Product: systemd
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: systemd-bugs
QA Contact: systemd-bugs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-11-13 16:27 UTC by Bastien Nocera
Modified: 2017-03-09 01:41 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:

Attachments
input_id: Detect whether keyboards have lock LEDs (2.89 KB, patch)
2014-11-13 16:28 UTC, Bastien Nocera 		Details | Splinter Review
Show Obsolete (1) View All

Description Bastien Nocera 2014-11-13 16:27:47 UTC 
Originally from:
https://bugzilla.gnome.org/show_bug.cgi?id=722437

Possible patch attached. It doesn't seem to work as well as it used to, probably kernel regressions :/
Comment 1 Bastien Nocera 2014-11-13 16:28:03 UTC 
Created attachment 109430 [details] [review]
input_id: Detect whether keyboards have lock LEDs

Use capabilities/led whether to detect whether keyboards have NumLock
and/or CapsLock LEDs. This allows desktops to show an OSD when the
CapsLock/NumLock status changes if the keyboard doesn't have any such
LEDs.
Comment 2 Bastien Nocera 2014-11-13 18:24:53 UTC 
Looks like we won't be able to use this to detect whether keyboards have LEDs or not... We'll probably need to tag the devices "by hand" a-la keyboard hwdb.
Comment 3 Lennart Poettering 2014-12-08 23:34:12 UTC 
Yeah, the hwdb is the right place for such information. We can certainly add that, modelled after the mouse dpi logic.
Comment 4 Peter Hutterer 2017-03-09 01:26:13 UTC 
closing, systemd doesn't use this bugzilla anymore, please file in github if it's still an issue.
Comment 5 Bastien Nocera 2017-03-09 01:41:35 UTC 
Moved to:
https://github.com/systemd/systemd/issues/5559

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.