Hi, 2005/11/4, Alex Kanavin <[EMAIL PROTECTED]>: > Right. However, the subclass 254 interface contains a CDC union descriptor > which points to the data interface with FBUS endpoints. Those two are > called master and slave interfaces. The driver should first check the > subclass value if it's 254 and then parse the union descriptor for the > pointer to the slave interface.
Sounds sane. Thanks for the explanation. > > - when looking for FBUS port the condition > > serial->interface->num_altsetting == 2 is checked (not sure yet what > > it means) > > The slave interface has two settings: active (which contains endpoints) > and idle. The driver sets it to the active setting. As far as I can see you can distinct that just by looking at numEndpoints. If it equals 0, it's idle. Otherwise it's active. Is that right? Thanks for clarifying! I'll prepare the needed changes to the driver by tomorrow. 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
