[alsa-devel] Status of the Tascam US-122mkII???

[Daniel Mack]

(please don't remove any addresses from Cc:)

On Sat, Jun 19, 2010 at 01:58:02PM -0400, jordan johnston wrote:
>     Interface Descriptor:
>       bLength                 9
>       bDescriptorType         4
>       bInterfaceNumber        0
>       bAlternateSetting       0
>       bNumEndpoints           0
>       bInterfaceClass       255 Vendor Specific Class
>       bInterfaceSubClass      0
>       bInterfaceProtocol      0
>       iInterface              0
>     Interface Descriptor:
>       bLength                 9
>       bDescriptorType         4
>       bInterfaceNumber        1
>       bAlternateSetting       0
>       bNumEndpoints           0
>       bInterfaceClass       255 Vendor Specific Class
>       bInterfaceSubClass      0
>       bInterfaceProtocol      0
>       iInterface              0
>     Interface Descriptor:
>       bLength                 9
>       bDescriptorType         4
>       bInterfaceNumber        1
>       bAlternateSetting       1
>       bNumEndpoints           4
>       bInterfaceClass       255 Vendor Specific Class
>       bInterfaceSubClass      0
>       bInterfaceProtocol      0
>       iInterface              0

I just wanted to know whether they switched to class compliance
interfaces, but as you can see here, that's not the case.

> you will notice it is using usb 1.1 (i unbinded the usb2, as i am told
> it doesn't work with it)

How did you do this? And you modified the driver to match this device
ID, right?

> usb 4-1: new full speed USB device using uhci_hcd and address 3
> usb 4-1: New USB device found, idVendor=0644, idProduct=8021
> usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
> usb 4-1: Product: US-122 MKII
> usb 4-1: Manufacturer: TASCAM
> usb 4-1: SerialNumber: no serial number
> ALSA sound/usb/usx2y/usb_stream.c:603: status=-2
> ALSA sound/usb/usx2y/usb_stream.c:603: status=-2
> ALSA sound/usb/usx2y/us122l.c:365: us122l_start error -14
> snd-usb-us122l: probe of 4-1:1.1 failed with error -22
> usbcore: registered new interface driver snd-usb-us122l

Sorry, I can't help here. Maybe Karsten, die author of this driver,
has any clue (put to Cc: now). Otherwise, you would need to trace the
USB traffic using TASCAM's driver for Windows or MacOSX, and then
reverse-engineer the protocol ...

HTH,
Daniel