Hi, Sorry for the long no-answer -- I was on 3 week vacation away from the computer.
2005/11/9, Alexander Kanavin <[EMAIL PROTECTED]>: > usb-serial can claim both interfaces then, same way as cdc_acm does. > That's probably too much extra code for just one special case though. So for the kernel driver option there are two ways to implement the driver (if I understand correctly): - make it independent from usb-serial and implement similiar to cdc-ether - claim more than one interface for FBUS communication Both don't look trivial at least for me. > Anyway, another and probably the best option is to do it entirely in > userspace via libusb, same way as we do for USB transport in OpenOBEX. > Good news for Pawel here is that he can copy-paste most of my USB patch > for openobex, because OBEX and FBUS interfaces are set up in exactly the > same way. I looked at the code shortly. Does the code autodetect interface which should be used? What I mean is that this approach would ignore port option in gnokiirc file (which might be good). take care, pkot -- Pawel Kot http://www.gnokii.org/ ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_idv37&alloc_id865&op=click _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
