Hi Sarah,
>> 2. Clear Halt of EP
>
> Also note that the xHCI hardware will only allow the Reset Endpoint to
> complete if the endpoint was actually halted due to a stall, babble,
> transfer error, etc. It won't reset the endpoint toggles or sequence
> number at arbitrary points, so we can't reset
I'm trying to update my project which uses libusbx 1.0.12 to 1.0.14 but
I'm experiencing some problem which where not present before. For
instance in my application I'm discovering all the devices with a known
VID PID, opening them to read some more information and then closing
them again.
Afte
On 10/3/2012 12:56 PM, Xiaofan Chen wrote:
On Wed, Oct 3, 2012 at 6:42 PM, Ramon Zambelli
wrote:
I'm trying to update my project which uses libusbx 1.0.12 to 1.0.14 but I'm
experiencing some problem which where not present before. For instance in my
application I'm discovering all the devices w
On 2012.10.03 11:42, Ramon Zambelli wrote:
> [ 0.203012] [17f0] libusbx: debug [get_api_type] upper filter
> driver(s): libusb0
> [ 0.203012] [17f0] libusbx: debug [get_api_type] matched driver name
> against WinUSB API
Using the libusb-win32 filter driver on top of WinUSB is knwon not to
On 2012.10.03 17:35, Frank Hibbeln wrote:
> I am doing essentially the same thing and experiencing the same problem.
> My environment is WinXP and the driver for my device is WinUSB.sys.
OK. You don't seem to have the filter driver, and I have just been able
to reproduce the issue in xusb, with t
Should be fixed with latest git.
https://github.com/libusbx/libusbx/commit/09759d5836766fb3b886824cd669bc0dfc149d00
Regards,
/Pete
--
Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy New R
