On Thu, 3 Nov 2005, Pawel Kot wrote:
For what it's worth:
- 0x82 is AT modem endpoint
It's taken care of by cdc_acm driver, right?
- 0x83, 0x84, 0x85, 0x86 are the possible FBUS endpoints; varying
across the phone models (0x83 is with Nokia 6230i, 0x86 is with 7600)
Ah, I see. Seems like Nokia changes these FBUS endpoint addresses all the
time. I think the right way for the dku2 driver would be to identify the
FBUS interface by the interface subclass which seems to be 254
(vendor-specific) always, and maybe also by this unrecognized 05 24 ab 05
33 functional descriptor (see below). That way the driver won't
erronesouly take over wrong interfaces (such as OBEX), which happens now.
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 3
bAlternateSetting 0
bNumEndpoints 0
bInterfaceClass 2 Communications
bInterfaceSubClass 254
bInterfaceProtocol 0
iInterface 0
CDC Header:
bcdCDC 1.10
UNRECOGNIZED: 05 24 ab 05 33
CDC Union:
bMasterInterface 3
bSlaveInterface 4
Alexander
Homepage: http://www.sensi.org/~ak/
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
[email protected]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
