> What is the libusb/libusbx merge? Pulling changes from libusb into libusbx,
> or the other way, or both?
It's merging libusbx and libusb back together into a single website, git
repository and so on. This is something that we'd said we'd do more than 9
month ago, so now's probably a good time to try to keep our word... ;)
> Is there some dependency between hotplug support and isoc that I'm not aware
> of?
Not really. The issue here is that there's currently only one official libusbx
Windows maintainer (me), who started looking at the [Windows hotplug
patch](https://github.com/libusbx/libusbx/issues/9) that was submitted quite a
few months ago now, and then had little choice but to move to non-libusb things
before I sould push things further for official integration. So the integration
of this patch has been in limbo for about 2 months now, and I don't think it
would be fair for the person who submitted it, and is still waiting on its
integration, if a brand new major feature, such as libusbK isoc was integrated
first. For what is worth, I do try to review/test submitted patches before
integrating them, especially if they are major features, so it's not just a
matter of pushing the "Merge pull request" button.
However I will be the first to admit that this can create a major bottleneck,
and actually wouldn't mind seeing someone taking over Windows maintenance
altogether, if they have the time, to avoid this kind of damaging situation.
Now, considering that we already had a milestone set for January for the libusb
merge (which existed before you submitted your patch), and know that there are
a bunch of our users waiting on this to happen that's what I'm planning to
spend my time on next.
Then, as it's probable that Manuel must be despairing to ever see his work
integrated, Windows hotplug is what I'll turn to after that.
Only once that's sorted out am I planning to take a closer look at your patch.
Maybe it'll take 5 minutes to review and integrate (though I sure would like to
take a quick look at WinUSB 8.1 ISOC while I do so), but processing stuff
submitted to us more or less in a FIFO fashion does look like the fairer
approach to me.
d
> Are you suggesting WinUSB isoc support would be merged before Windows
> hotplug, libusb/libusbx merge?
No.
What I'm saying is (Not trying to play the busier-than-thou card here -- pretty
sure you are probably as busy as I am, and would like see this thing gone ASAP,
so that you can move on to some other things), since I'm also planning to have
releases of other stuff (namely Rufus, libwdi & Zadig) over the coming couple
of months, with yet-to-be-coded features, and since libusb merge & Windows
hoptplug take precedence, I'm just trying to warn you that you're probably
better off counting that not much happen with your patch for the next couple of
months __if I'm the one tasked to integrate it__. And thus you might want to
use that time to add a related feature, if you have the scope.
/Pete
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/pull/164#issuecomment-30462654
------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't have a clear picture of how application performance
affects their revenue. With AppDynamics, you get 100% visibility into your
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
_______________________________________________
libusbx-devel mailing list
libusbx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libusbx-devel
