On Wed, Oct 30, 2013 at 09:24:11PM -0200, Wander Lairson Costa wrote:
> 2013/10/30 Johannes Stezenbach :
>
> >> >> >> > [2249737.372143] usb 1-1.1: usbfs: process 32478 (python) did not
> >> >> >> > claim interface 0 before use
> >> >> >> >
> >> >> >>
> >> >> >> Interface claiming, in another han
2013/10/30 Johannes Stezenbach :
>> >> >> > [2249737.372143] usb 1-1.1: usbfs: process 32478 (python) did not
>> >> >> > claim interface 0 before use
>> >> >> >
>> >> >>
>> >> >> Interface claiming, in another hand, is handled internally by PyUSB,
>> >> >> this might be a bug.
>> >> >
>> >> > usb
On Tue, Oct 29, 2013 at 06:06:43PM -0200, Wander Lairson Costa wrote:
> 2013/10/29 Johannes Stezenbach :
> > On Tue, Oct 29, 2013 at 02:58:45PM -0200, Wander Lairson Costa wrote:
> >
> > I was testing with a Linux based device and gadget g_zero, and
> > the EPIPE error stuck unless I added either i
On Tue, Oct 29, 2013 at 08:13:45PM -0200, Wander Lairson Costa wrote:
> 2013/10/29 Tormod Volden :
> > On Tue, Oct 29, 2013 at 9:06 PM, Wander Lairson Costa wrote:
> >> 2013/10/29 Johannes Stezenbach:
> >>> On Tue, Oct 29, 2013 at 02:58:45PM -0200, Wander Lairson Costa wrote:
> 2013/10/29 Joha
I have a USB 3.0 (bladeRF) device that is correctly recognized as SuperSpeed
device in Windows 7 using Renesas stack.
That same device is incorrectly detected as HiSpeed device in Windows 8.1 using
Microsoft stack.
The problem seems due to Windows 8.1 API. Please see:
http://social.msdn.micros
