Re: [Libusbx-devel] Releasing 1.0.16 ...

2013-07-12 Thread Hans de Goede
Hi, On 07/12/2013 12:15 AM, Pete Batard wrote: > freecode has now been updated (but each new entry gets reviewed by the > freecode people before it is published, so it may be a few hours before it > gets publicized) along with the index page on http://libusbx.org (there is a > link to the lates

Re: [Libusbx-devel] Releasing 1.0.16 ...

2013-07-12 Thread Xiaofan Chen
On Fri, Jul 12, 2013 at 3:14 PM, Hans de Goede wrote: > On 07/12/2013 12:15 AM, Pete Batard wrote: >> Finally, the default download from SF was set to the windows binaries, >> which is not what we want, especially as we always use the default SF >> download for the latest source on the index page.

[Libusbx-devel] [PATCH] Windows: Fix race between windows_clock_gettime_threaded() and windows_clock_gettime()

2013-07-12 Thread Simon Haggett
When the timer thread is created in windows_init(), it performs an initialisation phase in which it uses QueryPerformanceFrequency() to determine if there is a high resolution timer available, and sets hires_frequency and hires_ticks_to_ps appropriately. However, since windows_init() does not wait

[Libusbx-devel] [PATCH] WinCE: Fix race between wince_clock_gettime_threaded() and wince_clock_gettime()

2013-07-12 Thread Simon Haggett
When the timer thread is created in wince_init(), it performs an initialisation phase in which it uses QueryPerformanceFrequency() to determine if there is a high resolution timer available, and sets hires_frequency and hires_ticks_to_ps appropriately. However, since wince_init() does not wait for

Re: [Libusbx-devel] Releasing 1.0.16 ...

2013-07-12 Thread Toby Gray
On 11/07/13 23:15, Pete Batard wrote: > (but I'm still not too sure why -win became the default download and > not wince, which was uploaded later). The reason for this is probably because I've been uploading the wince binaries via SFTP. I've being doing it via SFTP because I don't get the sou

[Libusbx-devel] [PATCH] hotplug: Pass explicit context to callbacks

2013-07-12 Thread Florian Albrechtskirchinger
Instead of passing NULL for the context to hotplug callbacks, if the context happens to be the default context, always pass the explicit context pointer. --- libusb/hotplug.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/libusb/hotplug.c b/libusb/hotplug.c index 6b04342..36

[Libusbx-devel] [PATCH] hotplug: Pass explicit context to callbacks

2013-07-12 Thread Florian Albrechtskirchinger
The accompanying patch changes the hotplug callback invocation to always pass the explicit context pointer. The current behavior doesn't permit comparing contexts in the callback, when dealing with multiple contexts, as the comparison will fail, if the context is also the default and therefore N