Hi,
I have Boss GT-10 device which connects through USB and is identified
as a sound card. Recently I upgraded from openSUSE 11.2 to openSUSE 11.3
(the former probably being based on 2.6.31 kernel, the latter - 2.6.34). From
this moment I am not able to configure the device. Though its visible in the
system it does not seem to be identified as providing audio inputs.
$ cat /proc/asound/cards
0 [Intel ]: HDA-Intel - HDA Intel
HDA Intel at 0xf9ff8000 irq 29
1 [GT10 ]: USB-Audio - GT-10
BOSS corp. GT-10 at usb-0000:00:1d.1-1, full speed
$ ls /proc/asound/card1/
id midi0 oss_mixer usbbus usbid
dmesg shows the following lines after the processor is plugged in:
[ 4109.160018] usb 7-1: new full speed USB device using uhci_hcd and address 4
[ 4109.331108] usb 7-1: New USB device found, idVendor=0582, idProduct=00da
[ 4109.331112] usb 7-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 4109.331115] usb 7-1: Product: GT-10
[ 4109.331117] usb 7-1: Manufacturer: BOSS corp.
[ 4109.340113] ALSA usbaudio.c:2943: 4:0:1 : unknown interface protocol 0002
[ 4109.341107] ALSA usbaudio.c:2943: 4:1:1 : unknown interface protocol 0001
The last two look quite interesting so I checked the offending usbaudio.c:2943
line which turned out to be located in parse_audio_endpoints function. Here is a
simplified snippet from the function that shows the problematic code:
switch (protocol) {
case UAC_VERSION_1: {
// ...
break;
}
case UAC_VERSION_2: {
// ...
break;
}
default:
snd_printk(KERN_ERR "%d:%u:%d : unknown interface protocol %04x\n",
dev->devnum, iface_no, altno, protocol); // line 2943
continue;
}
As I understand the device returns either 1 or 2 as bInterfaceProtocol value
whereas the current code accepts only UAC_VERSION_1 (0) or UAC_VERSION_2 (0x20).
>From what I can see, prior to 2.6.34 it was UAC_VERSION_1 code being executed
in all cases without checking bInterfaceProtocol value at all (so 1
and 2 were not
reported as erroneous). UAC_VERSION_2 handling is a newer addition, though
not local to this single function.
I'm wondering if this issue may be responsible for problems with the device
configuration. If that is the case, is there a fix or workaround possible?
Or maybe I should look for some other causes?
Thanks,
Andrzej Zawadzki
------------------------------------------------------------------------------
The Palm PDK Hot Apps Program offers developers who use the
Plug-In Development Kit to bring their C/C++ apps to Palm for a share
of $1 Million in cash or HP Products. Visit us here for more details:
http://p.sf.net/sfu/dev2dev-palm
_______________________________________________
Alsa-user mailing list
Alsa-user@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/alsa-user
