On 2013.08.06 22:14, Peter Stuge wrote: > This changed with their specification of "WinUSB Devices"
If we're talking about making sure that the right information goes out, surely Microsoft's overview of WinUSB Devices [1] or the very hands-on page I wrote about WCID Devices [2] (since a WinUSB device is just a subset of a WCID device) that you should be well aware of and that contains things like firmware sample, USB traces and whatnot, may have deserved a link, no? For the sake of information completion, it should also be worth noting that the WinUSB driver from Microsoft does have quite a few limitations [3], and that other drivers, such as the Open Source libusb-win32 [4] or libusbK [5] ones (which can also be used as WCID, though with a bit less convenience as long as nobody tries to push their WCID incarnation through WHQL) might work better for some, if they are looking for "excellent usability and portability". Regards, /Pete [1] http://msdn.microsoft.com/en-us/library/windows/hardware/hh450799.aspx [2] https://github.com/pbatard/libwdi/wiki/WCID-Devices [3] https://github.com/libusbx/libusbx/wiki/Windows-Backend#wiki-Known_Restrictions [4] http://sourceforge.net/apps/trac/libusb-win32/wiki [5] http://libusbk.sourceforge.net/UsbK3/index.html ------------------------------------------------------------------------------ Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
