On Thu, Jan 24, 2013 at 10:30 PM, Xiaofan Chen <xiaof...@gmail.com> wrote: > On Thu, Jan 24, 2013 at 6:27 PM, Wander Lairson Costa > <wander.lair...@gmail.com> wrote: >> If you look the code for the Benchmark firmware, you will see that for >> OUT bulk and interrupt transfers, the code calls a GetLength function >> to know how many bytes it received, but for isochronous transfers, it >> always assume it received "packet size" bytes. >> > > I believe this is a simplified design for the isochronous OUT transfer. > Technically it may receive less bytes than the wMaxPacketSize > of the ISOC OUT Endpoint. > > This may have something to do with limitation of libusb0.sys' > isochronous capability as well. It is not as good as libusbK.sys. > libusb-win32 currently only supports fixed user-defined ISOC > packet size per transfer. >
libusbK does have more advanced ISOC API. http://libusbk.sourceforge.net/UsbK3/group__isok.html Thiis may be more in line with libusbx's isochronous API. So in the future, it may be possible to add isochronous support to libusbx's Windows backend. http://libusbx.sourceforge.net/api-1.0/group__asyncio.html -- Xiaofan ------------------------------------------------------------------------------ Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. ON SALE this month only -- learn more at: http://p.sf.net/sfu/learnnow-d2d _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel
