* AKAI EIE PRO
@ 2014-09-06 7:44 Martin Svensson
2014-09-06 11:48 ` Daniel Mack
0 siblings, 1 reply; 9+ messages in thread
From: Martin Svensson @ 2014-09-06 7:44 UTC (permalink / raw)
To: Alsa-devel
Dont know if its ok to ask a question here so please let me know if its
not ok then i wont ask again ;)
i just bought an external usb AKAI EIE PRO sound card, is there any
future plans to implement it in Alsa?
Sincerally
Martin aka "ztealmax"
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: AKAI EIE PRO
2014-09-06 7:44 AKAI EIE PRO Martin Svensson
@ 2014-09-06 11:48 ` Daniel Mack
2014-09-07 11:30 ` humbert.olivier.1
0 siblings, 1 reply; 9+ messages in thread
From: Daniel Mack @ 2014-09-06 11:48 UTC (permalink / raw)
To: Martin Svensson, Alsa-devel
On 09/06/2014 09:44 AM, Martin Svensson wrote:
> Dont know if its ok to ask a question here so please let me know if its
> not ok then i wont ask again ;)
>
> i just bought an external usb AKAI EIE PRO sound card, is there any
> future plans to implement it in Alsa?
Please send the output of 'lsusb -v' with this device connected. In best
case, we only have to add a quirk table entry.
Daniel
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: AKAI EIE PRO
2014-09-06 11:48 ` Daniel Mack
@ 2014-09-07 11:30 ` humbert.olivier.1
2014-09-07 11:39 ` Daniel Mack
0 siblings, 1 reply; 9+ messages in thread
From: humbert.olivier.1 @ 2014-09-07 11:30 UTC (permalink / raw)
To: Alsa-devel; +Cc: Martin Svensson, Daniel Mack
>On 09/06/2014 09:44 AM, Martin Svensson wrote:
>> Dont know if its ok to ask a question here so please let me know if its
>> not ok then i wont ask again ;)
>>
>> i just bought an external usb AKAI EIE PRO sound card, is there any
>> future plans to implement it in Alsa?
>
>Daniel Mack wrote:
>Please send the output of 'lsusb -v' with this device connected. In best
>case, we only have to add a quirk table entry.
Hi Daniel,
if that can help, we had an user on http://www.linuxmao.org with an EIE PRO.
Here you have his lsusb -v :
Bus 001 Device 006: ID 09e8:0010 AKAI Professional M.I. Corp.
Couldn't open device, some information will be missing
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 255 Vendor Specific Class
bDeviceSubClass 255 Vendor Specific Subclass
bDeviceProtocol 255 Vendor Specific Protocol
bMaxPacketSize0 64
idVendor 0x09e8 AKAI Professional M.I. Corp.
idProduct 0x0010
bcdDevice 2.00
iManufacturer 1
iProduct 2
iSerial 3
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 80
bNumInterfaces 2
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x40
(Missing must-be-set bit!)
Self Powered
MaxPower 0mA
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 0
bAlternateSetting 1
bNumEndpoints 3
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 5
Transfer Type Isochronous
Synch Type Asynchronous
Usage Type Data
wMaxPacketSize 0x009c 1x 156 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 4
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x04 EP 4 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 4
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 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 5
Transfer Type Isochronous
Synch Type Asynchronous
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 4
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x86 EP 6 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 1
Source: http://www.linuxmao.org/forumthread51851?comments_offset=20 (in french).
Hope that helps,
Olivier
^ permalink raw reply [flat|nested] 9+ messages in thread* Re: AKAI EIE PRO
2014-09-07 11:30 ` humbert.olivier.1
@ 2014-09-07 11:39 ` Daniel Mack
2014-09-07 12:26 ` humbert.olivier.1
` (2 more replies)
0 siblings, 3 replies; 9+ messages in thread
From: Daniel Mack @ 2014-09-07 11:39 UTC (permalink / raw)
To: humbert.olivier.1, Alsa-devel; +Cc: Martin Svensson
On 09/07/2014 01:30 PM, humbert.olivier.1@free.fr wrote:
> if that can help, we had an user on http://www.linuxmao.org with an EIE PRO.
> Here you have his lsusb -v :
>
> Bus 001 Device 006: ID 09e8:0010 AKAI Professional M.I. Corp.
> Couldn't open device, some information will be missing
> Device Descriptor:
> bLength 18
> bDescriptorType 1
> bcdUSB 2.00
> bDeviceClass 255 Vendor Specific Class
> bDeviceSubClass 255 Vendor Specific Subclass
> bDeviceProtocol 255 Vendor Specific Protocol
According to the tech specs, this should be a USB hub, but it isn't. Or
is this just one of the sub-devices? What does 'lsusb -t' say, and does
Linux see something like a mouse or mass storage device when connected
to one of the hub ports?
Assuming that's just the audio part ...
> Endpoint Descriptor:
> bLength 7
> bDescriptorType 5
> bEndpointAddress 0x02 EP 2 OUT
> bmAttributes 5
> Transfer Type Isochronous
> Synch Type Asynchronous
> Usage Type Data
> wMaxPacketSize 0x009c 1x 156 bytes
> bInterval 1
> Endpoint Descriptor:
> bLength 7
> bDescriptorType 5
> bEndpointAddress 0x83 EP 3 IN
> bmAttributes 2
> Transfer Type Bulk
> Synch Type None
> Usage Type Data
> wMaxPacketSize 0x0200 1x 512 bytes
> bInterval 4
> Endpoint Descriptor:
> bLength 7
> bDescriptorType 5
> bEndpointAddress 0x04 EP 4 OUT
> bmAttributes 2
> Transfer Type Bulk
> Synch Type None
> Usage Type Data
> wMaxPacketSize 0x0200 1x 512 bytes
> bInterval 4
So at least, they're not trying to hide class-specific endpoint
descriptors here, which what I've been hoping for.
I guess someone has to trace the traffic spoken to this device by the
Windows driver. I take it this thing doesn't work on OS X with a 3rd
party driver?
Daniel
^ permalink raw reply [flat|nested] 9+ messages in thread* Re: AKAI EIE PRO
2014-09-07 11:39 ` Daniel Mack
@ 2014-09-07 12:26 ` humbert.olivier.1
2014-09-08 21:43 ` Michal Rydlo
2014-11-16 16:09 ` humbert.olivier.1
2 siblings, 0 replies; 9+ messages in thread
From: humbert.olivier.1 @ 2014-09-07 12:26 UTC (permalink / raw)
To: Alsa-devel; +Cc: Martin Svensson, Daniel Mack
Daniel, I've been asking to the interface owners on our website if they can provide the information you requested I'll keep you updated if I have answers there.
Re: driver on OSX, given http://www.akaipro.com/product/eiepro#downloads , I think you're right.
Best,
Olivier
PS: (apologise for the message sent twice Daniel)
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: AKAI EIE PRO
2014-09-07 11:39 ` Daniel Mack
2014-09-07 12:26 ` humbert.olivier.1
@ 2014-09-08 21:43 ` Michal Rydlo
2014-11-16 16:09 ` humbert.olivier.1
2 siblings, 0 replies; 9+ messages in thread
From: Michal Rydlo @ 2014-09-08 21:43 UTC (permalink / raw)
To: Daniel Mack; +Cc: Alsa-devel, humbert.olivier.1, Martin Svensson
Hello there!
On Sun, Sep 7, 2014 at 1:39 PM, Daniel Mack <daniel@zonque.org> wrote:
>
> On 09/07/2014 01:30 PM, humbert.olivier.1@free.fr wrote:
> > if that can help, we had an user on http://www.linuxmao.org with an EIE PRO.
> > Here you have his lsusb -v :
> >
> > Bus 001 Device 006: ID 09e8:0010 AKAI Professional M.I. Corp.
> > Couldn't open device, some information will be missing
> > Device Descriptor:
> > bLength 18
> > bDescriptorType 1
> > bcdUSB 2.00
> > bDeviceClass 255 Vendor Specific Class
> > bDeviceSubClass 255 Vendor Specific Subclass
> > bDeviceProtocol 255 Vendor Specific Protocol
>
> According to the tech specs, this should be a USB hub, but it isn't. Or
> is this just one of the sub-devices? What does 'lsusb -t' say, and does
> Linux see something like a mouse or mass storage device when connected
> to one of the hub ports?
>
> Assuming that's just the audio part ...
>
> > Endpoint Descriptor:
> > bLength 7
> > bDescriptorType 5
> > bEndpointAddress 0x02 EP 2 OUT
> > bmAttributes 5
> > Transfer Type Isochronous
> > Synch Type Asynchronous
> > Usage Type Data
> > wMaxPacketSize 0x009c 1x 156 bytes
> > bInterval 1
> > Endpoint Descriptor:
> > bLength 7
> > bDescriptorType 5
> > bEndpointAddress 0x83 EP 3 IN
> > bmAttributes 2
> > Transfer Type Bulk
> > Synch Type None
> > Usage Type Data
> > wMaxPacketSize 0x0200 1x 512 bytes
> > bInterval 4
> > Endpoint Descriptor:
> > bLength 7
> > bDescriptorType 5
> > bEndpointAddress 0x04 EP 4 OUT
> > bmAttributes 2
> > Transfer Type Bulk
> > Synch Type None
> > Usage Type Data
> > wMaxPacketSize 0x0200 1x 512 bytes
> > bInterval 4
>
> So at least, they're not trying to hide class-specific endpoint
> descriptors here, which what I've been hoping for.
>
> I guess someone has to trace the traffic spoken to this device by the
> Windows driver. I take it this thing doesn't work on OS X with a 3rd
> party driver?
I have analyzed the protocol more than a half year ago. I even tried to
create a linux driver around it but had to stop due to lack of time.
I hope I can continue working on it in November again.
I have published what I have done so far to github few seconds ago if
anyone wants to have a look or perhaps contribute.
https://github.com/mmm444/eie-pro-linux
I can write more text about the protocol if someone is interested.
Regards,
Michal
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: AKAI EIE PRO
2014-09-07 11:39 ` Daniel Mack
2014-09-07 12:26 ` humbert.olivier.1
2014-09-08 21:43 ` Michal Rydlo
@ 2014-11-16 16:09 ` humbert.olivier.1
2014-11-20 5:09 ` humbert.olivier.1
2 siblings, 1 reply; 9+ messages in thread
From: humbert.olivier.1 @ 2014-11-16 16:09 UTC (permalink / raw)
To: Daniel Mack; +Cc: michal.rydlo, Alsa-devel, Martin Svensson
On 09/07/2014 01:30 PM, humbert.olivier.1@free.fr wrote:
>> if that can help, we had an user on http://www.linuxmao.org with an EIE PRO.
>> Here you have his lsusb -v :
>>
>> Bus 001 Device 006: ID 09e8:0010 AKAI Professional M.I. Corp.
>> Couldn't open device, some information will be missing
>> Device Descriptor:
>> bLength 18
>> bDescriptorType 1
>> bcdUSB 2.00
>> bDeviceClass 255 Vendor Specific Class
>> bDeviceSubClass 255 Vendor Specific Subclass
>> bDeviceProtocol 255 Vendor Specific Protocol
>
> According to the tech specs, this should be a USB hub, but it isn't. Or
> is this just one of the sub-devices? What does 'lsusb -t' say, and does
> Linux see something like a mouse or mass storage device when connected
> to one of the hub ports?
[...zip...]
Hi Daniel and all,
An linuxmao.org user gave answers to these questions today. Here you go:
maxime@Ubuntu-MAO:~$ lsusb -t
/: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M
|__ Port 2: Dev 4, If 0, Class=Hub, Driver=hub/4p, 480M
|__ Port 4: Dev 5, If 0, Class=Vendor Specific Class, Driver=, 480M
|__ Port 4: Dev 5, If 1, Class=Vendor Specific Class, Driver=, 480M
|__ Port 3: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M
|__ Port 3: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M
|__ Port 2: Dev 6, If 0, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 2: Dev 6, If 1, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 3: Dev 5, If 0, Class=Video, Driver=uvcvideo, 480M
|__ Port 3: Dev 5, If 1, Class=Video, Driver=uvcvideo, 480M
maxime@Ubuntu-MAO:~$ dmesg | tail
[12078.955863] usb 3-2: New USB device found, idVendor=0409, idProduct=005a
[12078.955870] usb 3-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[12078.956401] hub 3-2:1.0: USB hub found
[12078.956452] hub 3-2:1.0: 4 ports detected
[12079.243626] usb 3-2.4: new high-speed USB device number 7 using xhci_hcd
[12079.348372] usb 3-2.4: New USB device found, idVendor=09e8, idProduct=0010
[12079.348379] usb 3-2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[12079.348383] usb 3-2.4: Product: EIE pro
[12079.348386] usb 3-2.4: Manufacturer: Akai Professional, LP
[12079.348389] usb 3-2.4: SerialNumber: no serial number
I'll be asking him to try connecting a mouse to one of the hub port and to get a dmesg from there.
Hope that can help in any way. If you would need some more information, please let me know.
Olivier
source : http://www.linuxmao.org/tiki-view_forum_thread.php?forumId=2&comments_parentId=56440#threadId58184
^ permalink raw reply [flat|nested] 9+ messages in thread* Re: AKAI EIE PRO
2014-11-16 16:09 ` humbert.olivier.1
@ 2014-11-20 5:09 ` humbert.olivier.1
0 siblings, 0 replies; 9+ messages in thread
From: humbert.olivier.1 @ 2014-11-20 5:09 UTC (permalink / raw)
To: Alsa-devel; +Cc: michal rydlo, Martin Svensson, Daniel Mack
On 09/07/2014 01:30 PM, humbert.olivier.1@free.fr wrote:
>>> if that can help, we had an user on http://www.linuxmao.org with an EIE PRO.
>>> Here you have his lsusb -v :
>>>
>>> Bus 001 Device 006: ID 09e8:0010 AKAI Professional M.I. Corp.
>>> Couldn't open device, some information will be missing
>>> Device Descriptor:
>>> bLength 18
>>> bDescriptorType 1
>>> bcdUSB 2.00
>>> bDeviceClass 255 Vendor Specific Class
>>> bDeviceSubClass 255 Vendor Specific Subclass
>>> bDeviceProtocol 255 Vendor Specific Protocol
>>
>> According to the tech specs, this should be a USB hub, but it isn't. Or
>> is this just one of the sub-devices? What does 'lsusb -t' say, and does
>> Linux see something like a mouse or mass storage device when connected
>> to one of the hub ports?
>
>[...zip...]
>
>Hi Daniel and all,
>
>A linuxmao.org user gave answers to these questions today. Here you go:
>
>maxime@Ubuntu-MAO:~$ lsusb -t
>/: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
>/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M
> |__ Port 2: Dev 4, If 0, Class=Hub, Driver=hub/4p, 480M
> |__ Port 4: Dev 5, If 0, Class=Vendor Specific Class, Driver=, 480M
> |__ Port 4: Dev 5, If 1, Class=Vendor Specific Class, Driver=, 480M
> |__ Port 3: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M
> |__ Port 3: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M
>/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M
> |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M
>/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M
> |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M
> |__ Port 2: Dev 6, If 0, Class=Human Interface Device, Driver=usbhid, 12M
> |__ Port 2: Dev 6, If 1, Class=Human Interface Device, Driver=usbhid, 12M
> |__ Port 3: Dev 5, If 0, Class=Video, Driver=uvcvideo, 480M
> |__ Port 3: Dev 5, If 1, Class=Video, Driver=uvcvideo, 480M
>
>
>maxime@Ubuntu-MAO:~$ dmesg | tail
>[12078.955863] usb 3-2: New USB device found, idVendor=0409, idProduct=005a
>[12078.955870] usb 3-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
>[12078.956401] hub 3-2:1.0: USB hub found
>[12078.956452] hub 3-2:1.0: 4 ports detected
>[12079.243626] usb 3-2.4: new high-speed USB device number 7 using xhci_hcd
>[12079.348372] usb 3-2.4: New USB device found, idVendor=09e8, idProduct=0010
>[12079.348379] usb 3-2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
>[12079.348383] usb 3-2.4: Product: EIE pro
>[12079.348386] usb 3-2.4: Manufacturer: Akai Professional, LP
>[12079.348389] usb 3-2.4: SerialNumber: no serial number
>
>I'll be asking him to try connecting a mouse to one of the hub port and to get a dmesg from there.
>
>Hope that can help in any way. If you would need some more information, please let me know.
>
>Olivier
>
>source : http://www.linuxmao.org/tiki-view_forum_thread.php?forumId=2&comments_parentId=56440#threadId58184
Hi to everyone,
I've been asking the user to test the USB hub thing. He did and it worked as usual. He tried twice, once with a mouse and the other with an external hard-drive.
Hope that helps.
Olivier
^ permalink raw reply [flat|nested] 9+ messages in thread
* AKAI EIE PRO
@ 2014-11-28 18:58 Loki Harfagr
0 siblings, 0 replies; 9+ messages in thread
From: Loki Harfagr @ 2014-11-28 18:58 UTC (permalink / raw)
To: alsa-devel
(hope that's correct to post that way through email since I'm just adding an
answer to a specific question in a specific thread), here we go:
> Daniel Mack daniel at zonque.org
> Sun Sep 7 13:39:12 CEST 2014
> Previous message: [alsa-devel] AKAI EIE PRO
> Next message: [alsa-devel] AKAI EIE PRO
> Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
> On 09/07/2014 01:30 PM, humbert.olivier.1 at free.fr wrote:
> > if that can help, we had an user on http://www.linuxmao.org with an EIE PRO.
> > Here you have his lsusb -v :
> >
> > Bus 001 Device 006: ID 09e8:0010 AKAI Professional M.I. Corp.
> > Couldn't open device, some information will be missing
> > Device Descriptor:
> > bLength 18
> > bDescriptorType 1
> > bcdUSB 2.00
> > bDeviceClass 255 Vendor Specific Class
> > bDeviceSubClass 255 Vendor Specific Subclass
> > bDeviceProtocol 255 Vendor Specific Protocol
>
> According to the tech specs, this should be a USB hub, but it isn't. Or
> is this just one of the sub-devices? What does 'lsusb -t' say, and does
> Linux see something like a mouse or mass storage device when connected
> to one of the hub ports?
To test accordingly to the question a USB device (Webcam C905) is plugged in one of the EIE Pro. hub ports
1) AKAI EIE Pro *OFF*:
-------------------
$ lsusb
Bus 002 Device 002: ID 152d:0551 JMicron Technology Corp. / JMicron USA Technology Corp.
Bus 005 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 006 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 003: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Bus 005 Device 004: ID 174c:5106 ASMedia Technology Inc. Transcend StoreJet 25M3
Bus 006 Device 003: ID 058f:6362 Alcor Micro Corp. Flash Card Reader/Writer
Bus 005 Device 006: ID 046d:c318 Logitech, Inc. Illuminated Keyboard
Bus 005 Device 007: ID 047d:1020 Kensington Expert Mouse Trackball
Bus 005 Device 012: ID 058f:9254 Alcor Micro Corp. Hub
-------------------
2) AKAI EIE Pro *ON*:
-------------------
$ lsusb
Bus 002 Device 002: ID 152d:0551 JMicron Technology Corp. / JMicron USA Technology Corp.
Bus 005 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub ven. nov. 28 19:27:58 CET 2014
Bus 006 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 003: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Bus 005 Device 004: ID 174c:5106 ASMedia Technology Inc. Transcend StoreJet 25M3
Bus 005 Device 018: ID 0409:005a NEC Corp. HighSpeed Hub
Bus 006 Device 003: ID 058f:6362 Alcor Micro Corp. Flash Card Reader/Writer
Bus 005 Device 006: ID 046d:c318 Logitech, Inc. Illuminated Keyboard
Bus 005 Device 007: ID 047d:1020 Kensington Expert Mouse Trackball
Bus 005 Device 012: ID 058f:9254 Alcor Micro Corp. Hub
Bus 005 Device 019: ID 046d:080a Logitech, Inc. Portable Webcam C905
Bus 005 Device 020: ID 09e8:0010 AKAI Professional M.I. Corp.
-------------------
-------------------
$ lsusb -t
/: Bus 06.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/8p, 480M
|__ Port 7: Dev 3, If 0, Class=Mass Storage, Driver=usb-storage, 480M
/: Bus 05.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M
|__ Port 1: Dev 3, If 0, Class=Hub, Driver=hub/4p, 480M
|__ Port 1: Dev 6, If 0, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 1: Dev 6, If 1, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 2: Dev 7, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
|__ Port 3: Dev 12, If 0, Class=Hub, Driver=hub/4p, 12M
|__ Port 2: Dev 4, If 0, Class=Mass Storage, Driver=usb-storage, 480M
|__ Port 4: Dev 18, If 0, Class=Hub, Driver=hub/4p, 480M
|__ Port 1: Dev 19, If 0, Class=Video, Driver=uvcvideo, 480M
|__ Port 1: Dev 19, If 1, Class=Video, Driver=uvcvideo, 480M
|__ Port 1: Dev 19, If 2, Class=Audio, Driver=snd-usb-audio, 480M
|__ Port 1: Dev 19, If 3, Class=Audio, Driver=snd-usb-audio, 480M
|__ Port 4: Dev 20, If 0, Class=Vendor Specific Class, Driver=, 480M
|__ Port 4: Dev 20, If 1, Class=Vendor Specific Class, Driver=, 480M
/: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 5000M
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 5000M
|__ Port 2: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M
-------------------
3) Then, the Webcam plugged in the EIE Pro. has been unplugged:
-------------------
$ lsusb -t
/: Bus 06.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/8p, 480M
|__ Port 7: Dev 3, If 0, Class=Mass Storage, Driver=usb-storage, 480M
/: Bus 05.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M
|__ Port 1: Dev 3, If 0, Class=Hub, Driver=hub/4p, 480M
|__ Port 1: Dev 6, If 0, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 1: Dev 6, If 1, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 2: Dev 7, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
|__ Port 3: Dev 12, If 0, Class=Hub, Driver=hub/4p, 12M
|__ Port 2: Dev 4, If 0, Class=Mass Storage, Driver=usb-storage, 480M
|__ Port 4: Dev 18, If 0, Class=Hub, Driver=hub/4p, 480M
|__ Port 4: Dev 20, If 0, Class=Vendor Specific Class, Driver=, 480M
|__ Port 4: Dev 20, If 1, Class=Vendor Specific Class, Driver=, 480M
/: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 5000M
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 5000M
|__ Port 2: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M
-------------------
-------------------
$ lsusb
Bus 002 Device 002: ID 152d:0551 JMicron Technology Corp. / JMicron USA Technology Corp.
Bus 005 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 006 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 003: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Bus 005 Device 004: ID 174c:5106 ASMedia Technology Inc. Transcend StoreJet 25M3
Bus 005 Device 018: ID 0409:005a NEC Corp. HighSpeed Hub
Bus 006 Device 003: ID 058f:6362 Alcor Micro Corp. Flash Card Reader/Writer
Bus 005 Device 006: ID 046d:c318 Logitech, Inc. Illuminated Keyboard
Bus 005 Device 007: ID 047d:1020 Kensington Expert Mouse Trackball
Bus 005 Device 012: ID 058f:9254 Alcor Micro Corp. Hub
Bus 005 Device 020: ID 09e8:0010 AKAI Professional M.I. Corp.
-------------------
Sincerely hoping it'll help to include full support in ALSA for the AKAI EIE Pro
as it's very good stuff, nicely built and convenient (for its hub) to USB ports
eaters as we're all in the music phylum :-)
Cheers!
--
<
°/_
/|
¹
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2014-11-28 18:59 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-09-06 7:44 AKAI EIE PRO Martin Svensson
2014-09-06 11:48 ` Daniel Mack
2014-09-07 11:30 ` humbert.olivier.1
2014-09-07 11:39 ` Daniel Mack
2014-09-07 12:26 ` humbert.olivier.1
2014-09-08 21:43 ` Michal Rydlo
2014-11-16 16:09 ` humbert.olivier.1
2014-11-20 5:09 ` humbert.olivier.1
-- strict thread matches above, loose matches on Subject: below --
2014-11-28 18:58 Loki Harfagr
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).