2013-10-31 3:58 GMT-02:00 Johannes Stezenbach :
> 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
s://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/usb/core/devio.c#n765
>
>
I don't have time right now, but I need to look further into this, as
it might be a problem with PyUSB. Thanks to pointing this out.
For now, what if you explicitly claim the interface (with
us
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 Johannes Stezenbach:
>>> We're run
2013/10/29 Johannes Stezenbach :
> On Tue, Oct 29, 2013 at 02:58:45PM -0200, Wander Lairson Costa wrote:
>> 2013/10/29 Johannes Stezenbach :
>> > On Tue, Oct 29, 2013 at 12:16:51PM -0200, Wander Lairson Costa wrote:
>> >> 2013/10/29 Johannes Stezenbach :
>> >
2013/10/29 Johannes Stezenbach :
> On Tue, Oct 29, 2013 at 12:16:51PM -0200, Wander Lairson Costa wrote:
>> 2013/10/29 Johannes Stezenbach :
>> >
>> > One remark: The "Let's get it started" example in
>> > docs/tutorial.rst look
2013/10/29 Johannes Stezenbach :
> Hi,
>
Hi Johannes,
> On Wed, Oct 16, 2013 at 08:51:24AM -0300, Wander Lairson Costa wrote:
>> I am proud to announce that PyUSB 1.0.0 beta is out.
> ...
>> TODO
>>
>>
>> * More tests with legacy module.
&
much more time than I was expecting to, so I would like
to thank you all for your patience, and specially for those whose contributed
for this release.
--
Best Regards,
Wander Lairson Costa
--
October Webinars: Cod
2013/6/12 Nathan Hjelm :
> Done.
>
Thanks :)
--
Best Regards,
Wander Lairson Costa
--
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-d
2013/6/11 Pete Batard :
> On 2013.06.11 15:01, Wander Lairson Costa wrote:
>> Are all libusbx maintainers back to libusb-devel mailing list?
>
> Besides myself, I don't think any of the other maintainers ever
> officially left libusb-devel. And I have been monitoring what ha
n that when I have a
problem (generally when developing PyUSB), it manifests in both
libraries.
BTW, when everything starts to happen in libusb-devel again, would you
guys mind coming back to the [libusb] prefix in messages subject
again?
--
Best Regards,
Wa
; benefit from. Therefore we hope that everybody will welcome this change.
>
Would be possible to rejoin the mailing lists earlier? Sometimes I
don't know which mailing list I am supposed to send messages to
(libusb, libusbx or both?).
--
Best Regards,
Wander Lairson Costa
---
2013/3/30 Alan Stern :
> On Sat, 30 Mar 2013, Wander Lairson Costa wrote:
>
[snip]
> It is mentioned explicitly in section 9.6.3 of the USB-2 spec:
>
> An endpoint is not shared among interfaces within a single
> configuration unless the endpoint is used by
2013/3/29 Alan Stern :
> On Fri, 29 Mar 2013, Wander Lairson Costa wrote:
>
>> Dear all,
>>
>> I have a (kind of dumb) question regarding libusb_bulk_transfer and
>> libusb_interrupt_transfer functions. These functions don't receive any
>> interface re
2013/3/30 Xiaofan Chen :
> On Sat, Mar 30, 2013 at 5:23 AM, Wander Lairson Costa
>
> Okay, so you have the same result as I. Either the firmware
> or the host program is not working. It seems to me the
> firmware is probably the culprit.
>
I guess so.
--
Best Regards,
Wa
Dear all,
I have a (kind of dumb) question regarding libusb_bulk_transfer and
libusb_interrupt_transfer functions. These functions don't receive any
interface related information in their parameters, so, which interface
they will send/receive data to/from?
--
Best Regards,
Wander Lairson
se]
[ 0.042878] [2b42] libusbx: debug [usbi_remove_pollfd] remove fd 6
[ 0.042890] [2b42] libusbx: debug [libusb_unref_device] destroy device 2.3
[ 0.042896] [2b42] libusbx: debug [libusb_exit]
[ 0.042899] [2b42] libusbx: debug [libusb_exit] destroying default context
[snip]
--
Bes
2013/3/15 Wander Lairson Costa :
> 2013/3/14 Xiaofan Chen :
>> On Thu, Mar 14, 2013 at 11:07 PM, Xiaofan Chen wrote:
>>> On Sun, Mar 3, 2013 at 6:05 PM, Xiaofan Chen wrote:
>>>> On Sun, Mar 3, 2013 at 6:55 AM, Wander Lairson Costa
>>>> wrote:
>&
2013/3/14 Xiaofan Chen :
> On Thu, Mar 14, 2013 at 11:07 PM, Xiaofan Chen wrote:
>> On Sun, Mar 3, 2013 at 6:05 PM, Xiaofan Chen wrote:
>>> On Sun, Mar 3, 2013 at 6:55 AM, Wander Lairson Costa
>>> wrote:
>>>> 2013/3/2 Xiaofan Chen :
>>
2013/3/2 Xiaofan Chen :
> On Fri, Jan 11, 2013 at 8:46 AM, Wander Lairson Costa
> wrote:
>> I am trying to do a isochronous loop transfer, I can write the data
>> but I am getting an error when trying to read it.
>>
>> The successfully transfer is the write o
2013/1/24 Xiaofan Chen :
> On Thu, Jan 24, 2013 at 10:30 PM, Xiaofan Chen wrote:
>> On Thu, Jan 24, 2013 at 6:27 PM, Wander Lairson Costa
>> wrote:
>>> If you look the code for the Benchmark firmware, you will see that for
>>> OUT bulk and interrupt transfers, th
ny bytes it received, but for isochronous transfers, it
always assume it received "packet size" bytes.
--
Best Regards,
Wander Lairson Costa
--
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, W
I observed that benchmark firmware always expects isochronous transfer
of a size multiple of packet size. Is this just a convention on the
firmware or is there something about isochronous that I am missing
out?
2013/1/21 Xiaofan Chen :
> On Sun, Jan 20, 2013 at 10:20 PM, Wander Lairson Co
Finally I found the issue. Indeed the problem was the firmware, I was
setting up the isochronous endpoint with handshake. I have done some
raw tests and it feels like it is working. Thank you all.
2013/1/20 Wander Lairson Costa :
> 2013/1/20 Xiaofan Chen :
>> On Fri, Jan 11, 2013 a
2013/1/20 Xiaofan Chen :
> On Fri, Jan 11, 2013 at 6:37 PM, Wander Lairson Costa
> wrote:
>>>> [1] https://github.com/walac/isochronous
>>>>
>>>> [2] https://github.com/walac/bmfw
>>>
>>> Can your test your firmware against the B
2013/1/11 Tim Roberts :
> Wander Lairson Costa wrote:
>> I am trying to do a isochronous loop transfer, I can write the data
>> but I am getting an error when trying to read it. Following are the
>> logs:
>
Hi Tim,
First of all, thanks for the explanation.
> Isochron
2013/1/11 Xiaofan Chen :
> On Fri, Jan 11, 2013 at 8:46 AM, Wander Lairson Costa
> wrote:
>> The successfully transfer is the write one, the failed one is the read
>> request. Source code for my test app can be found at [1]. The firmware
>> code [2] is a customize
26 matches
Mail list logo
