commit | c730a8410c8fc683e845fefcc06d6ced349b583b | [log] [tgz] |
---|---|---|
author | Frank Li <Frank.Li@nxp.com> | Thu Aug 15 10:21:17 2019 -0500 |
committer | Nathan Hjelm <hjelmn@google.com> | Wed Oct 30 19:05:42 2019 -0700 |
tree | aa9c527644fb07910a4ae847e5d149d153019a37 | |
parent | 211d79185120519ca9c436855d3b7406359e793b [diff] |
windows: workaround WaitForMultipleObjects max 64 events limitation. WaitForMultiObjects have limiation. Only can wait max 64 events. but usbi_poll may pass more than 64 fds. In previous implement, only wait for first 64 events. if previous 64 events were not trigger usbi_poll will wait for about 10s timemout eventhough other event triggered. This patch workaround this limitation. If max events less than 64, call WaitforMultiObjects directly. If max events more than 64, group every 63 events into one work thread. This thread call waitformulitobjects wait for this groug events and one addtional thread exit events. If any events trigger, this thread will trigger main notify events. The main usbi_poll thread call waitforsingleobject wait for notify events. If this events trigger, that means any of work threads get events. Then call exit notify events let all working thread exit safely. Return value changed, 0 means timeout. 1 - N means which event triggered. Closes #612 Signed-off-by: Frank Li <Frank.Li@nxp.com> Signed-off-by: Nathan Hjelm <hjelmn@google.com>
libusb is a library for USB device access from Linux, macOS, Windows, OpenBSD/NetBSD and Haiku userspace. It is written in C (Haiku backend in C++) and licensed under the GNU Lesser General Public License version 2.1 or, at your option, any later version (see COPYING).
libusb is abstracted internally in such a way that it can hopefully be ported to other operating systems. Please see the PORTING file for more information.
libusb homepage: http://libusb.info/
Developers will wish to consult the API documentation: http://api.libusb.info
Use the mailing list for questions, comments, etc: http://mailing-list.libusb.info
(Please use the mailing list rather than mailing developers directly)