Hi, 2005/11/3, Alex Kanavin <[EMAIL PROTECTED]>: > 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?
Right. nokia-dku2 driver should also work with this endpoint, though. > > - 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. Why do you think so? I admit that I don't fully understand the lsusb output and I don't know the driver details but is seems to me by short analysing this output and driver source: - subclass 254 has no endpoints - FBUS port should have endpoints - when looking for FBUS port the condition serial->interface->num_altsetting == 2 is checked (not sure yet what it means) - there's some harcode parameter depending on endpoint address passed to usb_set_interface() I'll check with Nokia 6170 which one should be chosen. But I suspect this is one of class 10, subclass 0. Of course I may be wrong. At this moment it was guessing. take care, pkot -- Pawel Kot http://www.gnokii.org/ ------------------------------------------------------- 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
