On Sun, Feb 10, 2013 at 2:15 AM, Kustaa Nyholm <kustaa.nyh...@planmeca.com> wrote: > I'm sure many here also watch the libusb-devel list, > > perhaps excluding Pete. > > They have made some progress in defining the hotplug > API...what is our standing on this? > > Do we want to have a look at their vision, pick on it, > or what? > > Has anyone actually had a peek?
I have asked the other admins to take a look at Nathan's proposal. Hans has given one feedback. I think the hotplug API proposed there is not complete and I am sure Pete will have some different ideas about the API. libusbx and libusb will probably diverge on the Hotplug API. As for the implementation, you can see that Peter is not satisfied with the Linux implementation. He has a good point about udev not always available, especially among Android and other embedded Linux platform. > As I'm not actively coding for libusbx I've not had > the time or motivation to hava a look at the actual > code. > > What's our idea when we can get down to doing start > on the hot plug? The milestone is not cast in stone, but it can give you an idea as our current roadmap. https://github.com/libusbx/libusbx/issues/milestones Of course I agree that hotplug is an important feature and the milestones can be changed if the community thinks that hotplug is more important than 2.0/2.1 and the admins agree with that, hotplug (Milestone 3.0) can be merged with Milestone 2.1 (some Milestone 2.1 features can be delayed as well). > For those who have not followed libusb-devel, Nathan > seem to report he has picked WinCE and most other > things from us, except 'the HID crap'. I think his pull is not complete. And do not worry, Peter wil sure drag the leg of Nathan and make sure the next libusb release to be a present for 2013 Christmas. :-) He wants to change the Linux implementation, and he wants to get the Windows hotplug implementation done before the next release. All sounds good but then in the end he has no time... That being said, libusbx is a independent project from libusb. Down the road, the API will diverge and I support Pete's vision to change the header file and library name to libusbx to differentiate from libusb post 2.0 release (at the same time, Hans wanted to maintain an API compatible 1.x series if that is possible, see milestone 1.0.16 which is to be compatible with 2.1 but with no API breakage). -- Xiaofan ------------------------------------------------------------------------------ Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel
