Alex Kanavin schrieb: > 2008/12/3 Hendrik Sattler <[EMAIL PROTECTED]>: > >>> To avoid such things, I'd like to redo the USB API in openobex 2 (if >>> there will be one), and perhaps move from libusb to usbfs2 (if that >>> project gets going). >> Don't switch to non-portable stuff, please. Instead only that list traversal >> stuff should be changed to something more stable. > > Non-portable stuff would allow precise identification of devices, but > I agree that it's best to keep things portable.
Besides that: if usbfs2 (that site has the last entry in Nov 2007!) ever gets going again, I'm sure that libusb will adapt to it. It also did for other changes in usb linux kernel interface. > The only problem is > that if two or more identical USB OBEX-capable devices are connected > at the same time, there is no way to distinguish them with the current > API. How does lsusb show the device:port combination then? Doesn't that also use libusb? Something like that would be nice to address devices without prior enumeration. > As for the list traversal, I'm thinking to replace > int OBEX_FindInterfaces(obex_t *self, obex_interface_t **intf); > with > int OBEX_NumInterfaces(obex_t *self); > obex_inteface_t* OBEX_InterfaceInfo(obex_t *self, int n); OBEX_EnumerateInterfaces() and OBEX_GetInterfacByIndex() could be one possibility. Something like the -s option of lsusb should be another one: OBEX_GetInterfaceByAddress() Is this possible? HS ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Openobex-users mailing list Openobex-users@lists.sourceforge.net http://lists.sourceforge.net/lists/listinfo/openobex-users
