Re: which handlers should bind to a device

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, 2011-03-11 at 16:24 +0100, Oliver Neukum wrote:
> Hi,
> 
> I have a set of USB speakers which also implement HID:
<snip>
> According to the Usage Page the device is not a keyboard, yet the keyboard handler
> binds. Is this really sensible?
> I: Bus=0003 Vendor=0471 Product=0104 Version=0100
> N: Name="Philips Electronics Philips USB Digital Speaker System"
> P: Phys=usb-0000:00:1d.0-1/input2
> S: Sysfs=/devices/pci0000:00/0000:00:1d.0/usb6/6-1/6-1:1.2/input/input15
> U: Uniq=
> H: Handlers=kbd event11 
> B: PROP=0
> B: EV=13
> B: KEY=e000000000000 0
> B: MSC=10

As long as it's not the only thing that binds. We're just missing udev
level information to be able to match the audio device and the sound
device, so that pressing the buttons would change the volume on that
device. See:
https://bugzilla.gnome.org/show_bug.cgi?id=340720

Cheers

--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Media Devel]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Linux Wireless Networking]     [Linux Omap]

  Powered by Linux