From: Daniel Drake <dan@re...> - 2009-11-15 12:50:00
The major change here is moving to use timerfd (when available) for
timer handling, meaning that libusb_get_next_timeout() always returns 0
and timeout events are triggered through the file descriptor set.
This is stepping towards a major async API simplification.
As this is a fairly intrusive change, please give this a little more
time than usual before rolling out into a production environment...
Old behaviour can be restored with ./configure --disable-timerfd
Daniel Drake (4):
Use AM_SILENT_RULES for building
Use timerfd for timeout handling
Update documentation about early completion caveats
Ludovic Rousseau (1):
Add libusb_get_max_iso_packet_size() to libusb.h
Get latest updates about Open Source Projects, Conferences and News.