diff options
author | Phillip Michael Jordan <phil@philjordan.eu> | 2008-08-05 11:01:00 +0200 |
---|---|---|
committer | Jaroslav Kysela <perex@perex.cz> | 2008-08-06 15:40:19 +0200 |
commit | b9c196e1452e1d4cbf0a1499f1e9c1b3edf59320 (patch) | |
tree | 050a0ba9c57a02723e900c26327e8d587da0c064 /block | |
parent | 0e0e16a87a0b973702feb572c2552d82e1aec5b9 (diff) | |
download | linux-3.10-b9c196e1452e1d4cbf0a1499f1e9c1b3edf59320.tar.gz linux-3.10-b9c196e1452e1d4cbf0a1499f1e9c1b3edf59320.tar.bz2 linux-3.10-b9c196e1452e1d4cbf0a1499f1e9c1b3edf59320.zip |
ALSA: snd_usb_audio: fix SB Extigy IR Remote regression
The support for the SB Extigy's remote seems to be broken in all
recent ALSA versions, including 1.0.17. The driver detects the event
correctly, then submits a URB to query the RC code. On the Extigy, the
URB is submitted with a length of 2 bytes. My hardware, however, only
replies with 1 byte, containing the correct RC button code. The
current implementation discards this as being too short. (line 1784 of
usbmixer.c)
This patch specifies a "minimum packet length" in the remote control
configuration. I've left the values for the Audigy 2/Live! the same as
the packet length, as I'm assuming the existing code works with them.
(I don't have the hardware to confirm) This fixes the Extigy RC
support, e.g. for use with Lirc.
Signed-off-by: Phillip Michael Jordan <phil@philjordan.eu>
Signed-off-by: Takashi Iwai <tiwai@suse.de>
Signed-off-by: Jaroslav Kysela <perex@perex.cz>
Diffstat (limited to 'block')
0 files changed, 0 insertions, 0 deletions