| Summary: | WISH: evdev doesn't match Bluetooth device via Uniq attribute | ||
|---|---|---|---|
| Product: | xorg | Reporter: | CIJOML CIJOMLovic CIJOMLov <cijoml> |
| Component: | Input/evdev | Assignee: | Zephaniah E. Hull <warp-spam+fdo> |
| Status: | RESOLVED WONTFIX | QA Contact: | Xorg Project Team <xorg-team> |
| Severity: | major | ||
| Priority: | high | ||
| Version: | git | ||
| Hardware: | Other | ||
| OS: | Linux (All) | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
| Bug Depends on: | |||
| Bug Blocks: | 17677 | ||
On Sat, Jun 21, 2008 at 09:19:08AM -0700, bugzilla-daemon@freedesktop.org wrote: > I tried bind evdev configuration to Uniq attribute in /proc/bus/input/devices > which is wold's uniq number of device, but driver responds no device specified > unloading evdev module > I tried git from 20080621 evdev doesn't support Vendor, Product or Uniq options. I'd be happy though to review a patch to add this functionality. Could we add this to the wish list then...? PLEASE? :) > --- Comment #2 from CIJOML CIJOMLovic CIJOMLov <cijoml@volny.cz> 2008-06-26 15:55:03 PST ---
> Could we add this to the wish list then...? PLEASE? :)
patches welcome :)
This bug should be converted at least to WISH any reason why that couldn't be done with HAL + udev? Hi Peter, this is only parameter which evdev module doesn't match against. So it is more likely wish for complete support of /proc/bus/input/devices in recent kernels I don't quite understand. Evdev only takes Device and Path options, and the latter is identical to the Device option anyway. Other than that, evdev doesn't do any matching against the device, and - IMHO - it should do anyway. You can easily set up HAL or udev to point the driver at the right device. Adding Uniq to the supported options means we have to start running through /dev/input/event* again (like evdev 1.2 did) and I'd rather avoid that behaviour. WONTFIX. Let the lower levels (i.e. HAL) deal with custom matching, not the driver. |
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.
Hello, I tried bind evdev configuration to Uniq attribute in /proc/bus/input/devices which is wold's uniq number of device, but driver responds no device specified unloading evdev module I tried git from 20080621 As you can see I also tried match against Vendor and Product, but also without any luck :( Thanks a lot for fixing this bug. I: Bus=0005 Vendor=046d Product=b003 Version=4310 N: Name="Logitech Bluetooth Mouse" P: Phys=00:1E:37:65:44:A1 S: Sysfs=/class/input/input8 U: Uniq=00:07:61:3E:70:11 H: Handlers=mouse2 event8 B: EV=17 B: KEY=ffff0000 0 0 0 0 0 0 0 0 B: REL=143 B: MSC=10 I: Bus=0005 Vendor=046d Product=b307 Version=2307 N: Name="Logitech Bluetooth Keyboard" P: Phys=00:1E:37:65:44:A1 S: Sysfs=/class/input/input9 U: Uniq=00:07:61:3E:1C:09 H: Handlers=kbd event9 B: EV=10001f B: KEY=37fff 2c3027 bf004444 0 0 1 10f84 8a27c007 ffe67bfa d941dfff febeffdf ffefffff ffffffff fffffffe B: REL=40 B: ABS=301 0 B: MSC=10 Section "InputDevice" Identifier "Configured Mouse" Driver "evdev" #Option "Vendor" "0x046d" #Option "Product" "0xb003" #Option "Name" "Logitech Bluetooth Mouse" Option "Uniq" "00:07:61:3E:70:11" Option "CorePointer" EndSection