Hi Alexander, > there's now a webpage with information about using USB OBEX interfaces > under Linux: > > http://members.dodo.com.au/~joaniemrc/nokia/Nokia-6670-USB.html > > Note that the obexftp patch offered from there is only a temporary hack, > and I'm planning to write a proper patch when Marcel reviews and hopefully > includes my USB transport patch into openobex. Soon, I hope.
I am mostly fine with all your changes, but "struct usb_obex_intf" worries me a little bit. Is it possible to create a string from it that represents all the needed information and hide all other stuff inside the USB transport layer. From my current view I think the OBEX API should be as simple as possible. So less structs are better. Another thing is that the different transport layers should be loaded on demand by dlopen() and realized as plugins. The dependencies with the USB and Bluetooth libraries are maybe too complex for some systems. Regards Marcel ------------------------------------------------------- This SF.Net email is sponsored by: NEC IT Guy Games. Get your fingers limbered up and give it your best shot. 4 great events, 4 opportunities to win big! Highest score wins.NEC IT Guy Games. Play to win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20 _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
