On Fri, Jun 22, 2012 at 4:38 AM, Pete Batard wrote:
> On 2012.06.21 21:42, Orin Eman wrote:
>
>> The patch is OK, but the compiler then throws the same warning on the
>> next line ("return 1;") so you need to remove the next line as well.
>>
>
> v2 attached.
>
> If you can confirm that everything
Kevyn-Alexandre Paré wrote:
> So by calling the libusb_get_pollfds It return 3 file descriptor.
>
> So my question is why 3?
>
> 2 files descriptor (POLLIN) that could be read.
> 1 file descriptor (POLLOUT) that could be write.
> ...
> So I can see that POLLOUT could be the endpoint8 and 1 of the P
On Fri, 22 Jun 2012 12:44:29 +0100, Pete Batard said:
>On 2012.06.21 21:23, Sean McBride wrote:
>> It would be nice to have nightly builds of libusbx where the resulting
>errors/warnings are gathered together for display.
>
>I agree that it would be nice. However,
>
> *SNIP*
I agree with all the
Hi,
I'm trying to integrate libusb, with Cypress FX2, with libev (event loop) by
using the "polling and timing" function:
http://libusb.sourceforge.net/api-1.0/group__poll.html
So by calling the libusb_get_pollfds It return 3 file descriptor.
So my question is why 3?
2 files descriptor (POLLI
On 2012.06.22 10:47, Hans de Goede wrote:
> While debugging an usbredir issue I noticed the following in libusb/io.c:
>
> int usbi_handle_transfer_completion(struct usbi_transfer *itransfer,
> enum libusb_transfer_status status)
> {
> ...
>
> /* FIXME: could be more in
On Fri, Jun 22, 2012 at 7:54 PM, Pete Batard wrote:
> On 2012.06.22 07:49, Xiaofan Chen wrote:
>> I have not forgot about the testlibusb sample myself but I did not
>> spend much time on it yet. I am kind of more interested in the
>> ISOC sample myself.
>
> Same here. And I wouldn't mind looking i
On 2012.06.22 07:49, Xiaofan Chen wrote:
> I have not forgot about the testlibusb sample myself but I did not
> spend much time on it yet. I am kind of more interested in the
> ISOC sample myself.
Same here. And I wouldn't mind looking into an usbutils's lsusb that can
be compiled against the non
On 2012.06.21 21:23, Sean McBride wrote:
> It would be nice to have nightly builds of libusbx where the resulting
> errors/warnings are gathered together for display.
I agree that it would be nice. However, since this is volunteer based,
I'm doubtful whether we can gather the minimal amount of v
On 2012.06.21 21:42, Orin Eman wrote:
The patch is OK, but the compiler then throws the same warning on the
next line ("return 1;") so you need to remove the next line as well.
v2 attached.
If you can confirm that everything looks good on your end, and if nobody
has further comment, I'll push
Hi,
While debugging an usbredir issue I noticed the following in libusb/io.c:
int usbi_handle_transfer_completion(struct usbi_transfer *itransfer,
enum libusb_transfer_status status)
{
...
/* FIXME: could be more intelligent with the timerfd here. we don't nee
10 matches
Mail list logo
