Forum: Applications -> Mobile phone communication: Poseidon to the rescue?

© 2001 - 2014
https://morph.zone

URL for this discussion
https://morph.zone/modules/newbb_plus/viewtopic.php?topic_id=6359&forum=9


Mobile phone communication: Poseidon to the rescue?
by jcmarcos on 2009/6/17 6:01:57

Hi there guys... A couple of days ago, I was toying with the crazy idea of communicating with my Windows Mobile 6 ("WM6") phone. I'm not aiming at having "ActiveSync for MorphOS", but some sort of experiment.

When you plug a WM6 phone into the USB port, Poseidon says it's a "Generic RNDIS device". That is, some sort of network device. Of course, MorphOS' NetStack can't deal with it because we don't have a driver for it. Nor Poseidon has a class for generic RNDIS devices. Fair.

But then, WM6 phones offer an option of "disabling advanced ActiveSync communication", which in turn makes the phone look like a "generic serial" device to Poseidon. And there comes the trick.

Can one expect some kind of communication with this scenario? Poseidon, of course, doesn't bind any class to the phone, but indeed offers the possibility of binding manually. Is there any class that might work? Perhaps "usbserial", or something like that? Would that mean that I could send data through "USBSER:", for example?

Re: Mobile phone communication: Poseidon to the rescue?
by platon42 on 2009/6/19 8:49:58

Well, why not post a UsbDevlister output of the device so we can have a look on what's available in the one mode or the other?
Bye...
Chris Hodges


Re: Mobile phone communication: Poseidon to the rescue?
by jcmarcos on 2009/6/22 5:04:01

Quote:

platon42 wrote:

why not post a UsbDevlister output of the device


Will do Chris, thankyou for your reply. I guess that there's something unavoidable: Writing a program for the mobile phone, for it to listen to Posiedon. That shouldn't be any problem. Now, back to research...

Re: Mobile phone communication: Poseidon to the rescue?
by jcmarcos on 2009/6/25 4:40:14

Finally, here it is, the results of "USBDevLister" in two runs. First, when the phone's "advanced PC communications" are enabled, it shows itself as "Generic RNDIS":

Code:

Poseidon DevID : 'Generic RNDIS-0BB4-0B51-61840a17-58da-d143-f800-0050bf3f5173-00'
Product Name : 'Generic RNDIS' (ID: 0B51, Vers: 0000)
Manufacturer : 'HTC' (Vendor: 0BB4 (High Tech Computer Corp.))
Serial Number : '61840a17-58da-d143-f800-0050bf3f5173' (USBVers: 0200)
Device State : fullspeed connected hasaddress hasdevdesc isconfigured
Device Address : 3 (Port 3 at PCI Root Hub Unit 0)
Class/Sub/Proto : 239/1/1 (Miscellaneous Device)
MaxPktSize EP 0 : 64
Power Check : Supply = 100mA, Drain = 0mA
Current Language: English (United States)
Supported Langs : English (United States)

1 configuration(s):

? Config 1 (Configuration 1)
Attrs : self-powered
MaxPower: 100 mA

2 interface(s) for this config:
? Interface 0 (Miscellaneous Device interface (0)) (ID: '00-00-EF-01-01')
Alternate Setting: 0
Class/Sub/Proto : 239/1/1 (Miscellaneous Device)

1 endpoint(s) for this interface:
? Endpoint 1 (interrupt <-[ IN)
MaxPktSize: 8
Interval : 1 ms

No alternate settings.

? Interface 1 (CDC data interface (1)) (ID: '01-00-0A-00-00')
Alternate Setting: 0
Class/Sub/Proto : 10/0/0 (CDC Data)

2 endpoint(s) for this interface:
? Endpoint 2 (bulk <-[ IN)
MaxPktSize: 64
? Endpoint 3 (bulk OUT ]->)
MaxPktSize: 64

No alternate settings.

Standard Descriptors:
Desc. 01 (Device), 18 bytes
Desc. 02 (Configuration), 9 bytes (Config 1)
Desc. 04 (Interface), 9 bytes (Iface 0/0, Cfg 1)
Desc. 24 (Class-specific Interface), 5 bytes (Iface 0/0, Cfg 1)
00: 05 24 01 00 01
Desc. 24 (Class-specific Interface), 4 bytes (Iface 0/0, Cfg 1)
00: 04 24 02 00
Desc. 24 (Class-specific Interface), 5 bytes (Iface 0/0, Cfg 1)
00: 05 24 02 00 01
Desc. 05 (Endpoint), 7 bytes (EP 1, IF 0/0, Cfg 1)
Desc. 04 (Interface), 9 bytes (Iface 1/0, Cfg 1)
Desc. 05 (Endpoint), 7 bytes (EP 2, IF 1/0, Cfg 1)
Desc. 05 (Endpoint), 7 bytes (EP 3, IF 1/0, Cfg 1)

Google: http://www.google.com/search?q=usb+0x0BB4+0x0B51



Next, with those "advanced options" disabled, the phone shows up as "Generic serial":

Code:

Poseidon DevID : 'Generic Serial-0BB4-0A51-61840a17-58da-d143-f800-0050bf3f5173-00'
Product Name : 'Generic Serial' (ID: 0A51, Vers: 0000)
Manufacturer : 'HTC' (Vendor: 0BB4 (High Tech Computer Corp.))
Serial Number : '61840a17-58da-d143-f800-0050bf3f5173' (USBVers: 0200)
Device State : fullspeed connected hasaddress hasdevdesc isconfigured
Device Address : 3 (Port 3 at PCI Root Hub Unit 0)
Class/Sub/Proto : 0/0/0 (<unknown>)
MaxPktSize EP 0 : 64
Power Check : Supply = 100mA, Drain = 0mA
Current Language: English (United States)
Supported Langs : English (United States)

1 configuration(s):

? Config 1 (Configuration 1)
Attrs : self-powered
MaxPower: 100 mA

1 interface(s) for this config:
? Interface 0 (Vendor interface (0)) (ID: '00-00-FF-FF-FF')
Alternate Setting: 0
Class/Sub/Proto : 255/255/255 (Vendor)

2 endpoint(s) for this interface:
? Endpoint 1 (bulk <-[ IN)
MaxPktSize: 64
? Endpoint 2 (bulk OUT ]->)
MaxPktSize: 64

No alternate settings.

Standard Descriptors:
Desc. 01 (Device), 18 bytes
Desc. 02 (Configuration), 9 bytes (Config 1)
Desc. 04 (Interface), 9 bytes (Iface 0/0, Cfg 1)
Desc. 05 (Endpoint), 7 bytes (EP 1, IF 0/0, Cfg 1)
Desc. 05 (Endpoint), 7 bytes (EP 2, IF 0/0, Cfg 1)

Google: http://www.google.com/search?q=usb+0x0BB4+0x0A51



Like I said, perhaps it's easir to communicate with the phone as a serial port. But I don't know if it can be done forcing a bind with some USB class. Then, I don't expect the phone to listen, because its serial communications might be blocked by its ActiveSync service. Serial ports, traditionally, can't be shared by programs, which effectively lock the port when they make use of it. That wouldn't happen if we used the phone as an RNDIS (network) device, but I guess that would be mucho more difficult. If only a SANA driver existed for "generic RNDIS" devices (through USB!)... Can it be done?

Re: Mobile phone communication: Poseidon to the rescue?
by platon42 on 2009/6/25 9:32:28

Thanks for the output.

In the first mode, the device is in ActiveStink mode, requiring an RNDIS driver *and* the synching application behind it. The RNDIS driver is a bit more complicated than a standard Ethernet driver it seems. Not an easy task.

In second mode uses a vendor specific class ID. Looking at the linux driver, it would be pretty easy to adapt one of the existing class drivers such as serialpl2303 or serialcp210x to the ipaq model. It probably would already work with the rawwrap.class if the ipaq-driver wouldn't need that special init sequence first.

And then, you're still missing the active stink protocol and the app on the other side. However, if you're willing to code the ipaq adaption, I'd gladly provide you the source to the serialcp210x.class, if you want to write an ActiveSync app, too.
Bye...
Chris Hodges


Re: Mobile phone communication: Poseidon to the rescue?
by jcmarcos on 2009/6/25 10:49:46

Quote:

platon42 wrote:

Thanks for the output.


No, really, thank you for your response!

Quote:

In the first mode, the device is in ActiveStink mode, requiring an RNDIS driver *and* the synching application behind it. The RNDIS driver is a bit more complicated than a standard Ethernet driver it seems. Not an easy task.


I had it discarded since the beginning. It's a better way of doing things, but much more complex. So much, in fact, that the word "better" fades away...

Quote:

In second mode uses a vendor specific class ID. Looking at the linux driver, it would be pretty easy to adapt one of the existing class drivers such as serialpl2303 or serialcp210x to the ipaq model. It probably would already work with the rawwrap.class if the ipaq-driver wouldn't need that special init sequence first.


So I would have to write a program that understands the Poseidon framework and, using its "rawwrap" class, I would be able to communicate with the phone? I guess I would only be able to do so if the program talked in the ActievSync language.

Quote:

And then, you're still missing the active stink protocol and the app on the other side.


Sure, that's what I feared. But I had the intention of writing "MorphSync", an application that runs on the phone, and talks to Poseidon.
Now, please correct me, because I'm wrong for sure: I expected that, after starting "MorphSync" on the phone, I could communicate with it from MorphOS through Poseidon's "USBSER:" device.
That's because I gaev for granted the wild guss that, if I have some kind of USB serial port in MorphOS, it would couple to a generic serial port on the phone.
Would it be possible? But we haven't even started to talk about baud rates, parties and stop bits, so go figure how clueless I really am.

Quote:

However, if you're willing to code the ipaq adaption, I'd gladly provide you the source to the serialcp210x.class, if you want to write an ActiveSync app, too.


That sounds scary...

Re: Mobile phone communication: Poseidon to the rescue?
by serge on 2009/6/25 13:37:15

Hi guys, I'm one more to be happy if we could get a good way to communicate with WindowsMobile devices.
I have a "HTC smartphone touch hd blackstone" and I'm on the same case as jcmarcos: no way to communicate easly at this time.

@ jcmarcos: You can use the FTP solution for the moment.
there's FTP clients and servers for WindowsMobile.
Then, you can communicate through your network using wifi on your HTC.

I know, this solution is slowwww, but is better than nothing ;-)

I'm thinking about a better solution:
Having Morphos replacing Windows on HTC devices and using Poseidon/USB connection between the mobile and the desktop  ;-)



[ Edited by serge on 2009/6/25 17:39 ]

Re: Mobile phone communication: Poseidon to the rescue?
by jcmarcos on 2009/6/25 13:44:49

Quote:

serge wrote:

Hi guys, I'm one more to be happy if we could get a good way to communicate with WindowsMobile devices.


I see I'm not alone. Does anybody here remember that AmigaOS program to sync with Symbian devices, ages ago?

Quote:

I'm thinking about a better solution:
Having Morphos replacing Windows on HTC devices


What a cheeky way to ask for an ARM port of MorphOS!

(me ducks)

Re: Mobile phone communication: Poseidon to the rescue?
by Schlonz on 2009/6/26 18:58:57

Maybe WM5torage is useful for you? Install that freeware on your WM device and use it as an massstorage device. I did not try it with MorphOS, but it works fine with Windows.

Re: Mobile phone communication: Poseidon to the rescue?
by HammerD on 2009/6/26 23:47:40

@platon42

any chance you can support tethering on the iPhone 3G?

When yo uplug the iPhone 3G (with 3.0 firmware) into a Windows machine it automatically configures itself and gets a DHCP address and is available for use as a modem. Very cool.

Right now if i plug in my iPhone 3G to my Deneb/OS4 box, it shows up, and charges, but I can only view the photos on the device; it doesn't know anything about tethering.



[ Edited by HammerD on 2009/6/26 21:48 ]
A4000/060/PPC-200MHz, A4000T/060/PPC-233MHz, CD32, MicroA1, Pegasos 2 G4, AMD Phenom Quad Core 2.5GHz, MacMini 1.5GHz/64MB VRam...mwwmwahhh :)


Re: Mobile phone communication: Poseidon to the rescue?
by serge on 2009/6/27 11:43:09

Quote:


Schlonz wrote:
Maybe WM5torage is useful for you? Install that freeware on your WM device and use it as an massstorage device. I did not try it with MorphOS, but it works fine with Windows.


You are write!

It works very nice. THANK YOU !!!

Re: Mobile phone communication: Poseidon to the rescue?
by platon42 on 2009/6/29 6:36:54

Quote:


jcmarcos wrote:

So I would have to write a program that understands the Poseidon framework and, using its "rawwrap" class, I would be able to communicate with the phone? I guess I would only be able to do so if the program talked in the ActievSync language.



Except for the one command that is missing to start up the communication, you could use CMD_READ and CMD_WRITE on the usbraw.device at your will to communicate with the device. I think there even is a DOSDriver for USBRAW under MorphOS.

Quote:


Sure, that's what I feared. But I had the intention of writing "MorphSync", an application that runs on the phone, and talks to Poseidon.
Now, please correct me, because I'm wrong for sure: I expected that, after starting "MorphSync" on the phone, I could communicate with it from MorphOS through Poseidon's "USBSER:" device.



Not with the rawwrap.class. The rawwrap.class technically does not generate a device at runtime that would be of the type serial (not IOSer IORequests but IOStdReq). You could though, use USBRAW:. But then again, as I wrote above, it would be pretty easy to adapt the existing serial drivers to a new "ipaq" driver, which would qualify as a serial.device.

When you're writing your application, you'd probably want to use the pure serial device rather than through a DOSDriver. Makes it easier for the user to handle. The DOSDriver needs more configuration.

Quote:


That's because I gaev for granted the wild guss that, if I have some kind of USB serial port in MorphOS, it would couple to a generic serial port on the phone.
Would it be possible? But we haven't even started to talk about baud rates, parties and stop bits, so go figure how clueless I really am.



Usually baudrates, parities, stop bits and break signalling would be ignored for that type of serial device over USB (it is only used for /real/ USB serial adapters).

Quote:


Quote:

However, if you're willing to code the ipaq adaption, I'd gladly provide you the source to the serialcp210x.class, if you want to write an ActiveSync app, too.


That sounds scary...


So that's a "no"? Because I'm not pretty fond in writing drivers for devices I don't have and therefore cannot test either.
Bye...
Chris Hodges


Re: Mobile phone communication: Poseidon to the rescue?
by platon42 on 2009/6/29 6:38:53

Quote:


jcmarcos wrote:

I see I'm not alone. Does anybody here remember that AmigaOS program to sync with Symbian devices, ages ago?



Symbian? I only remember one for Palm devices and it's called PDALink as lower layer and Spitfire as highlevel app. Poseidon has a class driver for Palm that works with the PDALink stuff. Unfortunately, Spitfire is very flakey and doesn't work well there.
Bye...
Chris Hodges


Re: Mobile phone communication: Poseidon to the rescue?
by platon42 on 2009/6/29 6:39:34

Quote:


HammerD wrote:
@platon42

any chance you can support tethering on the iPhone 3G?

When yo uplug the iPhone 3G (with 3.0 firmware) into a Windows machine it automatically configures itself and gets a DHCP address and is available for use as a modem. Very cool.

Right now if i plug in my iPhone 3G to my Deneb/OS4 box, it shows up, and charges, but I can only view the photos on the device; it doesn't know anything about tethering.



PsdDevlister output please?
Bye...
Chris Hodges


Re: Mobile phone communication: Poseidon to the rescue?
by HammerD on 2009/6/30 4:47:46

Quote:


platon42 wrote:
Quote:






PsdDevlister output please?



Here it is:

Skipping 'ISP1520-0471-3526-n/a-00' (use SHOWROOT to list)
---------------------------------------------------------------------------
Poseidon DevID : 'iPhone-05AC-1292-66316995fb6f42bde2d334cf4f73acd6b8b37d5d-00'
Product Name : 'iPhone' (ID: 1292, Vers: 0001)
Manufacturer : 'Apple Inc.' (Vendor: 05AC (Apple Computer, Inc.))
Serial Number : '66316995fb6f42bde2d334cf4f73acd6b8b37d5d' (USBVers: 0200)
Device State : highspeed connected hasaddress hasdevdesc configured
Device Address : 2 (Port 1 at ISP1520)
Class/Sub/Proto : 0/0/0 (<unknown>)
MaxPktSize EP 0 : 64
Power Check : Supply = 500mA, Drain = 500mA
Current Language: English (United States)
Supported Langs : English (United States)

4 configuration(s):

? Config 1 (PTP)
Attrs : bus-powered
MaxPower: 500 mA

1 interface(s) for this config:
? Interface 0 (Still Images interface (0)) (ID: '00-00-06-01-01')
Alternate Setting: 0
Class/Sub/Proto : 6/1/1 (PTP Camera)

This interface is bound to ptp.class, context 3DD40340.

3 endpoint(s) for this interface:
? Endpoint 2 (bulk OUT ]->)
MaxPktSize: 512
NAK-Rate : 10 ?Frames
? Endpoint 1 (bulk <-[ IN)
MaxPktSize: 512
NAK-Rate : 10 ?Frames
? Endpoint 3 (interrupt <-[ IN)
MaxPktSize: 64
Interval : 512 ?Frames

No alternate settings.

? Config 2 (iPod USB Interface)
Attrs : self-powered
MaxPower: 500 mA

3 interface(s) for this config:
? Interface 0 (Audio interface (0)) (ID: '02-00-00-01-01-00')
Alternate Setting: 0
Class/Sub/Proto : 1/1/0 (Audio Control)

0 endpoint(s) for this interface:

No alternate settings.

? Interface 1 (Audio interface (1)) (ID: '02-01-00-01-02-00')
Alternate Setting: 0
Class/Sub/Proto : 1/2/0 (Audio Streaming)

0 endpoint(s) for this interface:

Alternate settings:

? Interface 1 (Audio interface (1)) (ID: '02-01-01-01-02-00')
Alternate Setting: 1
Class/Sub/Proto : 1/2/0 (Audio Streaming)

1 endpoint(s) for this interface:
? Endpoint 1 (isochronous <-[ IN)
MaxPktSize: 192
Interval : 8 ?Frames
SyncType : no synchronization
UsageType : data

? Interface 2 (HID interface (2)) (ID: '02-02-00-03-00-00')
Alternate Setting: 0
Class/Sub/Proto : 3/0/0 (HID)

1 endpoint(s) for this interface:
? Endpoint 3 (interrupt <-[ IN)
MaxPktSize: 64
Interval : 1 ?Frames

No alternate settings.

? Config 3 (PTP + Apple Mobile Device)
Attrs : self-powered
MaxPower: 500 mA

2 interface(s) for this config:
? Interface 0 (Still Images interface (0)) (ID: '03-00-00-06-01-01')
Alternate Setting: 0
Class/Sub/Proto : 6/1/1 (PTP Camera)

3 endpoint(s) for this interface:
? Endpoint 2 (bulk OUT ]->)
MaxPktSize: 512
NAK-Rate : 10 ?Frames
? Endpoint 1 (bulk <-[ IN)
MaxPktSize: 512
NAK-Rate : 10 ?Frames
? Endpoint 3 (interrupt <-[ IN)
MaxPktSize: 64
Interval : 512 ?Frames

No alternate settings.

? Interface 1 (Vendor interface (1)) (ID: '03-01-00-FF-FE-02')
Alternate Setting: 0
Class/Sub/Proto : 255/254/2 (Vendor)

2 endpoint(s) for this interface:
? Endpoint 4 (bulk OUT ]->)
MaxPktSize: 512
NAK-Rate : 0 ?Frames
? Endpoint 5 (bulk <-[ IN)
MaxPktSize: 512
NAK-Rate : 0 ?Frames

No alternate settings.

? Config 4 (PTP + Apple Mobile Device + Apple USB Ethernet)
Attrs : self-powered
MaxPower: 500 mA

3 interface(s) for this config:
? Interface 0 (Still Images interface (0)) (ID: '04-00-00-06-01-01')
Alternate Setting: 0
Class/Sub/Proto : 6/1/1 (PTP Camera)

3 endpoint(s) for this interface:
? Endpoint 2 (bulk OUT ]->)
MaxPktSize: 512
NAK-Rate : 10 ?Frames
? Endpoint 1 (bulk <-[ IN)
MaxPktSize: 512
NAK-Rate : 10 ?Frames
? Endpoint 3 (interrupt <-[ IN)
MaxPktSize: 64
Interval : 512 ?Frames

No alternate settings.

? Interface 1 (Vendor interface (1)) (ID: '04-01-00-FF-FE-02')
Alternate Setting: 0
Class/Sub/Proto : 255/254/2 (Vendor)

2 endpoint(s) for this interface:
? Endpoint 4 (bulk OUT ]->)
MaxPktSize: 512
NAK-Rate : 0 ?Frames
? Endpoint 5 (bulk <-[ IN)
MaxPktSize: 512
NAK-Rate : 0 ?Frames

No alternate settings.

? Interface 2 (Vendor interface (2)) (ID: '04-02-00-FF-FD-01')
Alternate Setting: 0
Class/Sub/Proto : 255/253/1 (Vendor)

0 endpoint(s) for this interface:

Alternate settings:

? Interface 2 (Vendor interface (2)) (ID: '04-02-01-FF-FD-01')
Alternate Setting: 1
Class/Sub/Proto : 255/253/1 (Vendor)

2 endpoint(s) for this interface:
? Endpoint 6 (bulk <-[ IN)
MaxPktSize: 512
NAK-Rate : 0 ?Frames
? Endpoint 5 (bulk OUT ]->)
MaxPktSize: 512
NAK-Rate : 0 ?Frames

Standard Descriptors:
Desc. 01 (Device), 18 bytes
Desc. 02 (Configuration), 9 bytes (Config 1)
Desc. 04 (Interface), 9 bytes (Iface 0/0, Cfg 1)
Desc. 05 (Endpoint), 7 bytes (EP 2, IF 0/0, Cfg 1)
Desc. 05 (Endpoint), 7 bytes (EP 1, IF 0/0, Cfg 1)
Desc. 05 (Endpoint), 7 bytes (EP 3, IF 0/0, Cfg 1)
Desc. 02 (Configuration), 9 bytes (Config 2)
Desc. 04 (Interface), 9 bytes (Iface 0/0, Cfg 2)
Desc. 24 (Audio Control Header), 9 bytes (Iface 0/0, Cfg 2)
00: 09 24 01 00 01 1E 00 01 01
Desc. 24 (Audio Input Terminal), 12 bytes (Iface 0/0, Cfg 2)
00: 0C 24 02 01 01 02 02 02 03 00 00 00
Desc. 24 (Audio Output Terminal), 9 bytes (Iface 0/0, Cfg 2)
00: 09 24 03 02 01 01 01 01 00
Desc. 04 (Interface), 9 bytes (Iface 1/0, Cfg 2)
Desc. 04 (Interface), 9 bytes (Iface 1/1, Cfg 2)
Desc. 24 (Audio Stream General), 7 bytes (Iface 1/1, Cfg 2)
00: 07 24 01 02 01 01 00
Desc. 24 (Audio Stream Format Type), 35 bytes (Iface 1/1, Cfg 2)
00: 23 24 02 01 02 02 10 09 40 1F 00 11 2B 00 E0 2E
10: 00 80 3E 00 22 56 00 C0 5D 00 00 7D 00 44 AC 00
20: 80 BB 00
Desc. 05 (Endpoint), 9 bytes (EP 1, IF 1/1, Cfg 2)
Desc. 25 (Audio Generic Endpoint), 7 bytes (EP 1, IF 1/1, Cfg 2)
00: 07 25 01 01 00 00 00
Desc. 04 (Interface), 9 bytes (Iface 2/0, Cfg 2)
Desc. 21 (HID), 9 bytes (Iface 2/0, Cfg 2)
00: 09 21 11 01 00 01 22 D0 00
Desc. 05 (Endpoint), 7 bytes (EP 3, IF 2/0, Cfg 2)
Desc. 02 (Configuration), 9 bytes (Config 3)
Desc. 04 (Interface), 9 bytes (Iface 0/0, Cfg 3)
Desc. 05 (Endpoint), 7 bytes (EP 2, IF 0/0, Cfg 3)
Desc. 05 (Endpoint), 7 bytes (EP 1, IF 0/0, Cfg 3)
Desc. 05 (Endpoint), 7 bytes (EP 3, IF 0/0, Cfg 3)
Desc. 04 (Interface), 9 bytes (Iface 1/0, Cfg 3)
Desc. 05 (Endpoint), 7 bytes (EP 4, IF 1/0, Cfg 3)
Desc. 05 (Endpoint), 7 bytes (EP 5, IF 1/0, Cfg 3)
Desc. 02 (Configuration), 9 bytes (Config 4)
Desc. 04 (Interface), 9 bytes (Iface 0/0, Cfg 4)
Desc. 05 (Endpoint), 7 bytes (EP 2, IF 0/0, Cfg 4)
Desc. 05 (Endpoint), 7 bytes (EP 1, IF 0/0, Cfg 4)
Desc. 05 (Endpoint), 7 bytes (EP 3, IF 0/0, Cfg 4)
Desc. 04 (Interface), 9 bytes (Iface 1/0, Cfg 4)
Desc. 05 (Endpoint), 7 bytes (EP 4, IF 1/0, Cfg 4)
Desc. 05 (Endpoint), 7 bytes (EP 5, IF 1/0, Cfg 4)
Desc. 04 (Interface), 9 bytes (Iface 2/0, Cfg 4)
Desc. 04 (Interface), 9 bytes (Iface 2/1, Cfg 4)
Desc. 05 (Endpoint), 7 bytes (EP 6, IF 2/1, Cfg 4)
Desc. 05 (Endpoint), 7 bytes (EP 5, IF 2/1, Cfg 4)

Google: http://www.google.com/search?q=usb+0x05AC+0x1292
---------------------------------------------------------------------------
A4000/060/PPC-200MHz, A4000T/060/PPC-233MHz, CD32, MicroA1, Pegasos 2 G4, AMD Phenom Quad Core 2.5GHz, MacMini 1.5GHz/64MB VRam...mwwmwahhh :)


Re: Mobile phone communication: Poseidon to the rescue?
by platon42 on 2009/7/1 6:14:41

Man... I never have seen a more sophisticated USB device than this iPhone thingy. The iPod already was one out of two devices that I ever saw coming with more than one Configuration, but the iPhone has *four*, which is kinda cool.

What's not so cool though, that the Apple Mobile Device + Apple USB Ethernet interfaces are vendor specific and as of now, there's no information available about it. But you could try a forced binding to the ethwrap.class. If you're lucky, this works.

Due to the fact that no device ever needed to select a specific configuration from the end users point, Poseidon does not provide this via the UI. So by default, it will bind to the first configuration with a fitting class. Therefore, you need to do some tricks to get it bind to the other configs.

You need to create some dummy forced *interface* bindings (context menu iin the specific device information *window* on the interfaces):

Config 1 Interface 1 (PTP): forced interface binding to say, hub.class (won't work, as it only accepts device bindings).

Config 2 Interface 0 (USBAudio): forced interface binding to hub.class
Config 2 Interface 2 (HID): forced interface binding to hub.class

Config 3 Interface 0 (PTP): forced interface binding to hub.class

It will then still bind to Config 4 Interface 0 (PTP), which is fine.

Config 4 Interface 2, Alternate 1 (Ethernet): forced interface binding to ethwrap.class

Then click on unbind, click on Class Scan and see what happens. Post a UsdDevlister and UsbErrorlog.
Bye...
Chris Hodges


USB Audio Codec
by skipp604 on 2009/7/13 16:23:13

Hello Chris & the rest,

I was hoping you can tell me if we can use something like that on our beloved MorphOS and Poseidon:

http://skipp.cps.pl/usb-behringer.png

Now, this is what UsbDevLister output says:

---------------------------------------------------------------------------
Poseidon DevID : 'USB Audio CODEC -08BB-2902-n/a-00'
Product Name : 'USB Audio CODEC' (ID: 2902, Vers: 0100)
Manufacturer : 'Burr-Brown from TI' (Vendor: 08BB (Texas Instruments Japan))
Serial Number : 'n/a' (USBVers: 0110)
Device State : fullspeed connected hasaddress hasdevdesc isconfigured
Device Address : 5 (Port 2 at PCI Root Hub Unit 0)
Class/Sub/Proto : 0/0/0 (<unknown>)
MaxPktSize EP 0 : 8
Power Check : Supply = 500mA, Drain = 100mA
Current Language: English (United States)
Supported Langs : English (United States)

1 configuration(s):

Ě Config 1 (Configuration 1)
Attrs : bus-powered
MaxPower: 100 mA

4 interface(s) for this config:
Ě Interface 0 (Audio interface (0)) (ID: '00-00-01-01-00')
Alternate Setting: 0
Class/Sub/Proto : 1/1/0 (Audio Control)

0 endpoint(s) for this interface:

No alternate settings.

Ě Interface 1 (Audio interface (1)) (ID: '01-00-01-02-00')
Alternate Setting: 0
Class/Sub/Proto : 1/2/0 (Audio Streaming)

0 endpoint(s) for this interface:

Alternate settings:

Ě Interface 1 (Audio interface (1)) (ID: '01-01-01-02-00')
Alternate Setting: 1
Class/Sub/Proto : 1/2/0 (Audio Streaming)

1 endpoint(s) for this interface:
Ě Endpoint 2 (isochronous OUT ]->)
MaxPktSize: 192
Interval : 1 ms
SyncType : adaptive
UsageType : data

Ě Interface 1 (Audio interface (1)) (ID: '01-02-01-02-00')
Alternate Setting: 2
Class/Sub/Proto : 1/2/0 (Audio Streaming)

1 endpoint(s) for this interface:
Ě Endpoint 2 (isochronous OUT ]->)
MaxPktSize: 96
Interval : 1 ms
SyncType : adaptive
UsageType : data

Ě Interface 1 (Audio interface (1)) (ID: '01-03-01-02-00')
Alternate Setting: 3
Class/Sub/Proto : 1/2/0 (Audio Streaming)

1 endpoint(s) for this interface:
Ě Endpoint 2 (isochronous OUT ]->)
MaxPktSize: 96
Interval : 1 ms
SyncType : adaptive
UsageType : data

Ě Interface 1 (Audio interface (1)) (ID: '01-04-01-02-00')
Alternate Setting: 4
Class/Sub/Proto : 1/2/0 (Audio Streaming)

1 endpoint(s) for this interface:
Ě Endpoint 2 (isochronous OUT ]->)
MaxPktSize: 48
Interval : 1 ms
SyncType : adaptive
UsageType : data

Ě Interface 1 (Audio interface (1)) (ID: '01-05-01-02-00')
Alternate Setting: 5
Class/Sub/Proto : 1/2/0 (Audio Streaming)

1 endpoint(s) for this interface:
Ě Endpoint 2 (isochronous OUT ]->)
MaxPktSize: 96
Interval : 1 ms
SyncType : adaptive
UsageType : data

Ě Interface 1 (Audio interface (1)) (ID: '01-06-01-02-00')
Alternate Setting: 6
Class/Sub/Proto : 1/2/0 (Audio Streaming)

1 endpoint(s) for this interface:
Ě Endpoint 2 (isochronous OUT ]->)
MaxPktSize: 48
Interval : 1 ms
SyncType : adaptive
UsageType : data

Ě Interface 2 (Audio interface (2)) (ID: '02-00-01-02-00')
Alternate Setting: 0
Class/Sub/Proto : 1/2/0 (Audio Streaming)

0 endpoint(s) for this interface:

Alternate settings:

Ě Interface 2 (Audio interface (2)) (ID: '02-01-01-02-00')
Alternate Setting: 1
Class/Sub/Proto : 1/2/0 (Audio Streaming)

1 endpoint(s) for this interface:
Ě Endpoint 4 (isochronous <-[ IN)
MaxPktSize: 196
Interval : 1 ms
SyncType : asynchronous
UsageType : data

Ě Interface 2 (Audio interface (2)) (ID: '02-02-01-02-00')
Alternate Setting: 2
Class/Sub/Proto : 1/2/0 (Audio Streaming)

1 endpoint(s) for this interface:
Ě Endpoint 4 (isochronous <-[ IN)
MaxPktSize: 98
Interval : 1 ms
SyncType : asynchronous
UsageType : data

Ě Interface 2 (Audio interface (2)) (ID: '02-03-01-02-00')
Alternate Setting: 3
Class/Sub/Proto : 1/2/0 (Audio Streaming)

1 endpoint(s) for this interface:
Ě Endpoint 4 (isochronous <-[ IN)
MaxPktSize: 180
Interval : 1 ms
SyncType : asynchronous
UsageType : data

Ě Interface 2 (Audio interface (2)) (ID: '02-04-01-02-00')
Alternate Setting: 4
Class/Sub/Proto : 1/2/0 (Audio Streaming)

1 endpoint(s) for this interface:
Ě Endpoint 4 (isochronous <-[ IN)
MaxPktSize: 90
Interval : 1 ms
SyncType : asynchronous
UsageType : data

Ě Interface 2 (Audio interface (2)) (ID: '02-05-01-02-00')
Alternate Setting: 5
Class/Sub/Proto : 1/2/0 (Audio Streaming)

1 endpoint(s) for this interface:
Ě Endpoint 4 (isochronous <-[ IN)
MaxPktSize: 132
Interval : 1 ms
SyncType : asynchronous
UsageType : data

Ě Interface 2 (Audio interface (2)) (ID: '02-06-01-02-00')
Alternate Setting: 6
Class/Sub/Proto : 1/2/0 (Audio Streaming)

1 endpoint(s) for this interface:
Ě Endpoint 4 (isochronous <-[ IN)
MaxPktSize: 66
Interval : 1 ms
SyncType : asynchronous
UsageType : data

Ě Interface 2 (Audio interface (2)) (ID: '02-07-01-02-00')
Alternate Setting: 7
Class/Sub/Proto : 1/2/0 (Audio Streaming)

1 endpoint(s) for this interface:
Ě Endpoint 4 (isochronous <-[ IN)
MaxPktSize: 92
Interval : 1 ms
SyncType : asynchronous
UsageType : data

Ě Interface 2 (Audio interface (2)) (ID: '02-08-01-02-00')
Alternate Setting: 8
Class/Sub/Proto : 1/2/0 (Audio Streaming)

1 endpoint(s) for this interface:
Ě Endpoint 4 (isochronous <-[ IN)
MaxPktSize: 46
Interval : 1 ms
SyncType : asynchronous
UsageType : data

Ě Interface 2 (Audio interface (2)) (ID: '02-09-01-02-00')
Alternate Setting: 9
Class/Sub/Proto : 1/2/0 (Audio Streaming)

1 endpoint(s) for this interface:
Ě Endpoint 4 (isochronous <-[ IN)
MaxPktSize: 68
Interval : 1 ms
SyncType : asynchronous
UsageType : data

Ě Interface 2 (Audio interface (2)) (ID: '02-0A-01-02-00')
Alternate Setting: 10
Class/Sub/Proto : 1/2/0 (Audio Streaming)

1 endpoint(s) for this interface:
Ě Endpoint 4 (isochronous <-[ IN)
MaxPktSize: 34
Interval : 1 ms
SyncType : asynchronous
UsageType : data

Ě Interface 2 (Audio interface (2)) (ID: '02-0B-01-02-00')
Alternate Setting: 11
Class/Sub/Proto : 1/2/0 (Audio Streaming)

1 endpoint(s) for this interface:
Ě Endpoint 4 (isochronous <-[ IN)
MaxPktSize: 34
Interval : 1 ms
SyncType : asynchronous
UsageType : data

Ě Interface 2 (Audio interface (2)) (ID: '02-0C-01-02-00')
Alternate Setting: 12
Class/Sub/Proto : 1/2/0 (Audio Streaming)

1 endpoint(s) for this interface:
Ě Endpoint 4 (isochronous <-[ IN)
MaxPktSize: 17
Interval : 1 ms
SyncType : asynchronous
UsageType : data

Ě Interface 2 (Audio interface (2)) (ID: '02-0D-01-02-00')
Alternate Setting: 13
Class/Sub/Proto : 1/2/0 (Audio Streaming)

1 endpoint(s) for this interface:
Ě Endpoint 4 (isochronous <-[ IN)
MaxPktSize: 18
Interval : 1 ms
SyncType : asynchronous
UsageType : data

Ě Interface 2 (Audio interface (2)) (ID: '02-0E-01-02-00')
Alternate Setting: 14
Class/Sub/Proto : 1/2/0 (Audio Streaming)

1 endpoint(s) for this interface:
Ě Endpoint 4 (isochronous <-[ IN)
MaxPktSize: 9
Interval : 1 ms
SyncType : asynchronous
UsageType : data

Ě Interface 2 (Audio interface (2)) (ID: '02-0F-01-02-00')
Alternate Setting: 15
Class/Sub/Proto : 1/2/0 (Audio Streaming)

1 endpoint(s) for this interface:
Ě Endpoint 4 (isochronous <-[ IN)
MaxPktSize: 48
Interval : 1 ms
SyncType : synchronous
UsageType : data

Ě Interface 2 (Audio interface (2)) (ID: '02-10-01-02-00')
Alternate Setting: 16
Class/Sub/Proto : 1/2/0 (Audio Streaming)

1 endpoint(s) for this interface:
Ě Endpoint 4 (isochronous <-[ IN)
MaxPktSize: 24
Interval : 1 ms
SyncType : synchronous
UsageType : data

Ě Interface 2 (Audio interface (2)) (ID: '02-11-01-02-00')
Alternate Setting: 17
Class/Sub/Proto : 1/2/0 (Audio Streaming)

1 endpoint(s) for this interface:
Ě Endpoint 4 (isochronous <-[ IN)
MaxPktSize: 24
Interval : 1 ms
SyncType : synchronous
UsageType : data

Ě Interface 2 (Audio interface (2)) (ID: '02-12-01-02-00')
Alternate Setting: 18
Class/Sub/Proto : 1/2/0 (Audio Streaming)

1 endpoint(s) for this interface:
Ě Endpoint 4 (isochronous <-[ IN)
MaxPktSize: 12
Interval : 1 ms
SyncType : synchronous
UsageType : data

Ě Interface 3 (HID interface (3)) (ID: '03-00-03-00-00')
Alternate Setting: 0
Class/Sub/Proto : 3/0/0 (HID)

This interface is bound to hid.class, context 2152F70C.

1 endpoint(s) for this interface:
Ě Endpoint 5 (interrupt <-[ IN)
MaxPktSize: 1
Interval : 10 ms

No alternate settings.

Standard Descriptors:
Desc. 01 (Device), 18 bytes
Desc. 02 (Configuration), 9 bytes (Config 1)
Desc. 04 (Interface), 9 bytes (Iface 0/0, Cfg 1)
Desc. 24 (Audio Control Header), 10 bytes (Iface 0/0, Cfg 1)
00: 0A 24 01 00 01 3E 00 02 01 02
Desc. 24 (Audio Input Terminal), 12 bytes (Iface 0/0, Cfg 1)
00: 0C 24 02 01 01 01 00 02 03 00 00 00
Desc. 24 (Audio Output Terminal), 9 bytes (Iface 0/0, Cfg 1)
00: 09 24 03 02 01 03 00 03 00
Desc. 24 (Audio Feature Unit), 10 bytes (Iface 0/0, Cfg 1)
00: 0A 24 06 03 01 01 01 02 02 00
Desc. 24 (Audio Input Terminal), 12 bytes (Iface 0/0, Cfg 1)
00: 0C 24 02 04 01 02 00 02 03 00 00 00
Desc. 24 (Audio Output Terminal), 9 bytes (Iface 0/0, Cfg 1)
00: 09 24 03 05 01 01 00 04 00
Desc. 04 (Interface), 9 bytes (Iface 1/0, Cfg 1)
Desc. 04 (Interface), 9 bytes (Iface 1/1, Cfg 1)
Desc. 24 (Audio Stream General), 7 bytes (Iface 1/1, Cfg 1)
00: 07 24 01 01 00 01 00
Desc. 24 (Audio Stream Format Type), 17 bytes (Iface 1/1, Cfg 1)
00: 11 24 02 01 02 02 10 03 00 7D 00 44 AC 00 80 BB
10: 00
Desc. 05 (Endpoint), 9 bytes (EP 2, IF 1/1, Cfg 1)
Desc. 25 (Audio Generic Endpoint), 7 bytes (EP 2, IF 1/1, Cfg 1)
00: 07 25 01 00 02 00 02
Desc. 04 (Interface), 9 bytes (Iface 1/2, Cfg 1)
Desc. 24 (Audio Stream General), 7 bytes (Iface 1/2, Cfg 1)
00: 07 24 01 01 00 01 00
Desc. 24 (Audio Stream Format Type), 17 bytes (Iface 1/2, Cfg 1)
00: 11 24 02 01 01 02 10 03 00 7D 00 44 AC 00 80 BB
10: 00
Desc. 05 (Endpoint), 9 bytes (EP 2, IF 1/2, Cfg 1)
Desc. 25 (Audio Generic Endpoint), 7 bytes (EP 2, IF 1/2, Cfg 1)
00: 07 25 01 00 02 00 02
Desc. 04 (Interface), 9 bytes (Iface 1/3, Cfg 1)
Desc. 24 (Audio Stream General), 7 bytes (Iface 1/3, Cfg 1)
00: 07 24 01 01 00 01 00
Desc. 24 (Audio Stream Format Type), 17 bytes (Iface 1/3, Cfg 1)
00: 11 24 02 01 02 01 08 03 00 7D 00 44 AC 00 80 BB
10: 00
Desc. 05 (Endpoint), 9 bytes (EP 2, IF 1/3, Cfg 1)
Desc. 25 (Audio Generic Endpoint), 7 bytes (EP 2, IF 1/3, Cfg 1)
00: 07 25 01 00 02 00 02
Desc. 04 (Interface), 9 bytes (Iface 1/4, Cfg 1)
Desc. 24 (Audio Stream General), 7 bytes (Iface 1/4, Cfg 1)
00: 07 24 01 01 00 01 00
Desc. 24 (Audio Stream Format Type), 17 bytes (Iface 1/4, Cfg 1)
00: 11 24 02 01 01 01 08 03 00 7D 00 44 AC 00 80 BB
10: 00
Desc. 05 (Endpoint), 9 bytes (EP 2, IF 1/4, Cfg 1)
Desc. 25 (Audio Generic Endpoint), 7 bytes (EP 2, IF 1/4, Cfg 1)
00: 07 25 01 00 02 00 02
Desc. 04 (Interface), 9 bytes (Iface 1/5, Cfg 1)
Desc. 24 (Audio Stream General), 7 bytes (Iface 1/5, Cfg 1)
00: 07 24 01 01 00 02 00
Desc. 24 (Audio Stream Format Type), 17 bytes (Iface 1/5, Cfg 1)
00: 11 24 02 01 02 01 08 03 00 7D 00 44 AC 00 80 BB
10: 00
Desc. 05 (Endpoint), 9 bytes (EP 2, IF 1/5, Cfg 1)
Desc. 25 (Audio Generic Endpoint), 7 bytes (EP 2, IF 1/5, Cfg 1)
00: 07 25 01 00 02 00 02
Desc. 04 (Interface), 9 bytes (Iface 1/6, Cfg 1)
Desc. 24 (Audio Stream General), 7 bytes (Iface 1/6, Cfg 1)
00: 07 24 01 01 00 02 00
Desc. 24 (Audio Stream Format Type), 17 bytes (Iface 1/6, Cfg 1)
00: 11 24 02 01 01 01 08 03 00 7D 00 44 AC 00 80 BB
10: 00
Desc. 05 (Endpoint), 9 bytes (EP 2, IF 1/6, Cfg 1)
Desc. 25 (Audio Generic Endpoint), 7 bytes (EP 2, IF 1/6, Cfg 1)
00: 07 25 01 00 02 00 02
Desc. 04 (Interface), 9 bytes (Iface 2/0, Cfg 1)
Desc. 04 (Interface), 9 bytes (Iface 2/1, Cfg 1)
Desc. 24 (Audio Stream General), 7 bytes (Iface 2/1, Cfg 1)
00: 07 24 01 05 00 01 00
Desc. 24 (Audio Stream Format Type), 11 bytes (Iface 2/1, Cfg 1)
00: 0B 24 02 01 02 02 10 01 80 BB 00
Desc. 05 (Endpoint), 9 bytes (EP 4, IF 2/1, Cfg 1)
Desc. 25 (Audio Generic Endpoint), 7 bytes (EP 4, IF 2/1, Cfg 1)
00: 07 25 01 00 02 00 00
Desc. 04 (Interface), 9 bytes (Iface 2/2, Cfg 1)
Desc. 24 (Audio Stream General), 7 bytes (Iface 2/2, Cfg 1)
00: 07 24 01 05 00 01 00
Desc. 24 (Audio Stream Format Type), 11 bytes (Iface 2/2, Cfg 1)
00: 0B 24 02 01 01 02 10 01 80 BB 00
Desc. 05 (Endpoint), 9 bytes (EP 4, IF 2/2, Cfg 1)
Desc. 25 (Audio Generic Endpoint), 7 bytes (EP 4, IF 2/2, Cfg 1)
00: 07 25 01 00 02 00 00
Desc. 04 (Interface), 9 bytes (Iface 2/3, Cfg 1)
Desc. 24 (Audio Stream General), 7 bytes (Iface 2/3, Cfg 1)
00: 07 24 01 05 00 01 00
Desc. 24 (Audio Stream Format Type), 11 bytes (Iface 2/3, Cfg 1)
00: 0B 24 02 01 02 02 10 01 44 AC 00
Desc. 05 (Endpoint), 9 bytes (EP 4, IF 2/3, Cfg 1)
Desc. 25 (Audio Generic Endpoint), 7 bytes (EP 4, IF 2/3, Cfg 1)
00: 07 25 01 00 02 00 00
Desc. 04 (Interface), 9 bytes (Iface 2/4, Cfg 1)
Desc. 24 (Audio Stream General), 7 bytes (Iface 2/4, Cfg 1)
00: 07 24 01 05 00 01 00
Desc. 24 (Audio Stream Format Type), 11 bytes (Iface 2/4, Cfg 1)
00: 0B 24 02 01 01 02 10 01 44 AC 00
Desc. 05 (Endpoint), 9 bytes (EP 4, IF 2/4, Cfg 1)
Desc. 25 (Audio Generic Endpoint), 7 bytes (EP 4, IF 2/4, Cfg 1)
00: 07 25 01 00 02 00 00
Desc. 04 (Interface), 9 bytes (Iface 2/5, Cfg 1)
Desc. 24 (Audio Stream General), 7 bytes (Iface 2/5, Cfg 1)
00: 07 24 01 05 00 01 00
Desc. 24 (Audio Stream Format Type), 11 bytes (Iface 2/5, Cfg 1)
00: 0B 24 02 01 02 02 10 01 00 7D 00
Desc. 05 (Endpoint), 9 bytes (EP 4, IF 2/5, Cfg 1)
Desc. 25 (Audio Generic Endpoint), 7 bytes (EP 4, IF 2/5, Cfg 1)
00: 07 25 01 00 02 00 00
Desc. 04 (Interface), 9 bytes (Iface 2/6, Cfg 1)
Desc. 24 (Audio Stream General), 7 bytes (Iface 2/6, Cfg 1)
00: 07 24 01 05 00 01 00
Desc. 24 (Audio Stream Format Type), 11 bytes (Iface 2/6, Cfg 1)
00: 0B 24 02 01 01 02 10 01 00 7D 00
Desc. 05 (Endpoint), 9 bytes (EP 4, IF 2/6, Cfg 1)
Desc. 25 (Audio Generic Endpoint), 7 bytes (EP 4, IF 2/6, Cfg 1)
00: 07 25 01 00 02 00 00
Desc. 04 (Interface), 9 bytes (Iface 2/7, Cfg 1)
Desc. 24 (Audio Stream General), 7 bytes (Iface 2/7, Cfg 1)
00: 07 24 01 05 00 01 00
Desc. 24 (Audio Stream Format Type), 11 bytes (Iface 2/7, Cfg 1)
00: 0B 24 02 01 02 02 10 01 22 56 00
Desc. 05 (Endpoint), 9 bytes (EP 4, IF 2/7, Cfg 1)
Desc. 25 (Audio Generic Endpoint), 7 bytes (EP 4, IF 2/7, Cfg 1)
00: 07 25 01 00 02 00 00
Desc. 04 (Interface), 9 bytes (Iface 2/8, Cfg 1)
Desc. 24 (Audio Stream General), 7 bytes (Iface 2/8, Cfg 1)
00: 07 24 01 05 00 01 00
Desc. 24 (Audio Stream Format Type), 11 bytes (Iface 2/8, Cfg 1)
00: 0B 24 02 01 01 02 10 01 22 56 00
Desc. 05 (Endpoint), 9 bytes (EP 4, IF 2/8, Cfg 1)
Desc. 25 (Audio Generic Endpoint), 7 bytes (EP 4, IF 2/8, Cfg 1)
00: 07 25 01 00 02 00 00
Desc. 04 (Interface), 9 bytes (Iface 2/9, Cfg 1)
Desc. 24 (Audio Stream General), 7 bytes (Iface 2/9, Cfg 1)
00: 07 24 01 05 00 01 00
Desc. 24 (Audio Stream Format Type), 11 bytes (Iface 2/9, Cfg 1)
00: 0B 24 02 01 02 02 10 01 80 3E 00
Desc. 05 (Endpoint), 9 bytes (EP 4, IF 2/9, Cfg 1)
Desc. 25 (Audio Generic Endpoint), 7 bytes (EP 4, IF 2/9, Cfg 1)
00: 07 25 01 00 02 00 00
Desc. 04 (Interface), 9 bytes (Iface 2/10, Cfg 1)
Desc. 24 (Audio Stream General), 7 bytes (Iface 2/10, Cfg 1)
00: 07 24 01 05 00 01 00
Desc. 24 (Audio Stream Format Type), 11 bytes (Iface 2/10, Cfg 1)
00: 0B 24 02 01 01 02 10 01 80 3E 00
Desc. 05 (Endpoint), 9 bytes (EP 4, IF 2/10, Cfg 1)
Desc. 25 (Audio Generic Endpoint), 7 bytes (EP 4, IF 2/10, Cfg 1)
00: 07 25 01 00 02 00 00
Desc. 04 (Interface), 9 bytes (Iface 2/11, Cfg 1)
Desc. 24 (Audio Stream General), 7 bytes (Iface 2/11, Cfg 1)
00: 07 24 01 05 00 01 00
Desc. 24 (Audio Stream Format Type), 11 bytes (Iface 2/11, Cfg 1)
00: 0B 24 02 01 02 01 08 01 80 3E 00
Desc. 05 (Endpoint), 9 bytes (EP 4, IF 2/11, Cfg 1)
Desc. 25 (Audio Generic Endpoint), 7 bytes (EP 4, IF 2/11, Cfg 1)
00: 07 25 01 00 02 00 00
Desc. 04 (Interface), 9 bytes (Iface 2/12, Cfg 1)
Desc. 24 (Audio Stream General), 7 bytes (Iface 2/12, Cfg 1)
00: 07 24 01 05 00 01 00
Desc. 24 (Audio Stream Format Type), 11 bytes (Iface 2/12, Cfg 1)
00: 0B 24 02 01 01 01 08 01 80 3E 00
Desc. 05 (Endpoint), 9 bytes (EP 4, IF 2/12, Cfg 1)
Desc. 25 (Audio Generic Endpoint), 7 bytes (EP 4, IF 2/12, Cfg 1)
00: 07 25 01 00 02 00 00
Desc. 04 (Interface), 9 bytes (Iface 2/13, Cfg 1)
Desc. 24 (Audio Stream General), 7 bytes (Iface 2/13, Cfg 1)
00: 07 24 01 05 00 01 00
Desc. 24 (Audio Stream Format Type), 11 bytes (Iface 2/13, Cfg 1)
00: 0B 24 02 01 02 01 08 01 40 1F 00
Desc. 05 (Endpoint), 9 bytes (EP 4, IF 2/13, Cfg 1)
Desc. 25 (Audio Generic Endpoint), 7 bytes (EP 4, IF 2/13, Cfg 1)
00: 07 25 01 00 02 00 00
Desc. 04 (Interface), 9 bytes (Iface 2/14, Cfg 1)
Desc. 24 (Audio Stream General), 7 bytes (Iface 2/14, Cfg 1)
00: 07 24 01 05 00 01 00
Desc. 24 (Audio Stream Format Type), 11 bytes (Iface 2/14, Cfg 1)
00: 0B 24 02 01 01 01 08 01 40 1F 00
Desc. 05 (Endpoint), 9 bytes (EP 4, IF 2/14, Cfg 1)
Desc. 25 (Audio Generic Endpoint), 7 bytes (EP 4, IF 2/14, Cfg 1)
00: 07 25 01 00 02 00 00
Desc. 04 (Interface), 9 bytes (Iface 2/15, Cfg 1)
Desc. 24 (Audio Stream General), 7 bytes (Iface 2/15, Cfg 1)
00: 07 24 01 05 00 01 00
Desc. 24 (Audio Stream Format Type), 11 bytes (Iface 2/15, Cfg 1)
00: 0B 24 02 01 02 02 10 01 11 2B 00
Desc. 05 (Endpoint), 9 bytes (EP 4, IF 2/15, Cfg 1)
Desc. 25 (Audio Generic Endpoint), 7 bytes (EP 4, IF 2/15, Cfg 1)
00: 07 25 01 00 02 00 00
Desc. 04 (Interface), 9 bytes (Iface 2/16, Cfg 1)
Desc. 24 (Audio Stream General), 7 bytes (Iface 2/16, Cfg 1)
00: 07 24 01 05 00 01 00
Desc. 24 (Audio Stream Format Type), 11 bytes (Iface 2/16, Cfg 1)
00: 0B 24 02 01 01 02 10 01 11 2B 00
Desc. 05 (Endpoint), 9 bytes (EP 4, IF 2/16, Cfg 1)
Desc. 25 (Audio Generic Endpoint), 7 bytes (EP 4, IF 2/16, Cfg 1)
00: 07 25 01 00 02 00 00
Desc. 04 (Interface), 9 bytes (Iface 2/17, Cfg 1)
Desc. 24 (Audio Stream General), 7 bytes (Iface 2/17, Cfg 1)
00: 07 24 01 05 00 01 00
Desc. 24 (Audio Stream Format Type), 11 bytes (Iface 2/17, Cfg 1)
00: 0B 24 02 01 02 01 08 01 11 2B 00
Desc. 05 (Endpoint), 9 bytes (EP 4, IF 2/17, Cfg 1)
Desc. 25 (Audio Generic Endpoint), 7 bytes (EP 4, IF 2/17, Cfg 1)
00: 07 25 01 00 02 00 00
Desc. 04 (Interface), 9 bytes (Iface 2/18, Cfg 1)
Desc. 24 (Audio Stream General), 7 bytes (Iface 2/18, Cfg 1)
00: 07 24 01 05 00 01 00
Desc. 24 (Audio Stream Format Type), 11 bytes (Iface 2/18, Cfg 1)
00: 0B 24 02 01 01 01 08 01 11 2B 00
Desc. 05 (Endpoint), 9 bytes (EP 4, IF 2/18, Cfg 1)
Desc. 25 (Audio Generic Endpoint), 7 bytes (EP 4, IF 2/18, Cfg 1)
00: 07 25 01 00 02 00 00
Desc. 04 (Interface), 9 bytes (Iface 3/0, Cfg 1)
Desc. 21 (HID), 9 bytes (Iface 3/0, Cfg 1)
00: 09 21 00 01 00 01 22 1F 00
Desc. 05 (Endpoint), 7 bytes (EP 5, IF 3/0, Cfg 1)

Google: http://www.google.com/search?q=usb+0x08BB+0x2902
---------------------------------------------------------------------------


I was hoping you can help me get the sound out of it somehow ;) I am aware that it probably will need the AHI driver, but can you comment on the device itself and wheter it would be useful on MorphOS+Poseidon at all?

Thanks in advance (and big thanks for all your hard work so far!)



[ Edited by skipp604 on 2009/7/13 19:24 ]
bplan Efika 5200B, ATi Radeon 9250 / 256 MB, MorphOS 2.4


Re: USB Audio Codec
by Golem on 2009/7/14 13:47:55

@skipp604
That would need isochronous transfers which is currently only supported by the Deneb, so perhaps if you're running MorphOS PowerUp.

Re: USB Audio Codec
by skipp604 on 2009/7/29 20:11:28

Quote:


Golem wrote:
@skipp604
That would need isochronous transfers which is currently only supported by the Deneb, so perhaps if you're running MorphOS PowerUp.


No, I only use MorphOS 2.x on my Efika, since I don't have any PowerAmiga...

So there's no way it can work at all?

Can you explain why only Deneb supports this? I missed this information somehow.
bplan Efika 5200B, ATi Radeon 9250 / 256 MB, MorphOS 2.4


Re: USB Audio Codec
by platon42 on 2009/7/30 9:41:35

Quote:


skipp604 wrote:
Quote:


Golem wrote:
@skipp604
That would need isochronous transfers which is currently only supported by the Deneb, so perhaps if you're running MorphOS PowerUp.


No, I only use MorphOS 2.x on my Efika, since I don't have any PowerAmiga...

So there's no way it can work at all?

Can you explain why only Deneb supports this? I missed this information somehow.


One of the unique selling propositions of the Deneb is the cheap access and use of USB soundcards on Amiga Classic Machines, where the users would have to spend >100 EUR for a Zorro or clockport soundcard instead. On Pegasos you have onboard sound, hence there is not much of commercial sense to put a lot of work and effort into implementing iso transfers for the lowlevel driver that would only be necessary for this special use case of USB audio on the Peg. There is no technical limitation that would inhibit the implementation for pciusb.device.
Bye...
Chris Hodges



© 2001 - 2014
https://morph.zone

URL for this discussion
https://morph.zone/modules/newbb_plus/viewtopic.php?topic_id=6359&forum=9