Hi Tim,
On 2012-07-02, at 4:14 PM, Tim Roberts wrote:
> Kevyn-Alexandre Paré wrote:
>>
>>>
>>> If timerfd is available on your system, to manage timer expirations
>>> through a file descriptor, that's added to the POLLIN list.
>> thx, The linux kernel that I'm using have timerfd enable!
>>
>>
[pbatard][1] closed [issue 34][2] on [libusbx/libusbx][3] July 06, 2012
> Setup mailing list notification for issues
[1]: https://github.com/pbatard
[2]: https://github.com/libusbx/libusbx/issues/34 (Setup mailing list
notification for issues)
[3]: https://github.com/libusbx/libusbx
[pbatard][1] commented on [issue 34][2] on [libusbx/libusbx][3] July 06, 2012
> I'm gonna declare this enhancement resolved, with the following caveats: On
> issue creation, only the title of the new issue is made availablem but …
[1]: https://github.com/pbatard
[2]: https://github.com/li
On Fri, 6 Jul 2012, Hans de Goede wrote:
> > In theory we could prevent this problem by adding pre- and post-reset
> > handlers to usbfs. The difficulty is: What should such handlers do?
> > There's no way to inform client programs about the reset.
>
> Right, so I see one option here:
>
> 1) Ha
Hi,
On 07/06/2012 04:10 PM, Alan Stern wrote:
> On Fri, 6 Jul 2012, Hans de Goede wrote:
>
>> I've been seeing these intermittent failures to reclaim an interface after
>> a device reset. After much debugging and inserting sleeps in strategic
>> places to make the race window larger I've found the
On Fri, 6 Jul 2012, Hans de Goede wrote:
> I've been seeing these intermittent failures to reclaim an interface after
> a device reset. After much debugging and inserting sleeps in strategic
> places to make the race window larger I've found the following race:
> 1) A user is running some software
I've been seeing these intermittent failures to reclaim an interface after
a device reset. After much debugging and inserting sleeps in strategic
places to make the race window larger I've found the following race:
1) A user is running some software using libusb which will automatically
detect,
[pbatard][1] opened [issue 34][2] on [libusbx/libusbx][3] July 06, 2012
> Setup mailing list notification for issues
[1]: https://github.com/pbatard
[2]: https://github.com/libusbx/libusbx/issues/34 (Setup mailing list
notification for issues)
[3]: https://github.com/libusbx/libusbx
