> On Thursday, July 4, 2013, Hans de Goede wrote:
> Given that without this patch the hotplug API is essentially
> unusable for
> applications with a separate event thread, I believe we should add
> this to 1.0.16.
Agreed.
> It is not terribly adventurous, but I think it would
I have now merged this patch with my previous doc one, and pushed it.
Also, thanks to a suggestion from Nathan, you may now see some github
notifications with regards to libusbx issues (at least, they seem to
appear on the mailing list archive [1], though I don't get them in my
libusbx inbox fo
Hi,
This is the exact same problem I am experiencing in my app. I am very much
in favor of this change.
Regards,
Chris
On Thursday, July 4, 2013, Hans de Goede wrote:
> Hi All,
>
> So to make sure the API is sane, and to give the hotplug stuff some extra
> testing, I've ported Spice's usbredir
This is one more test for github automated notifications - please ignore.
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/issues/95#issuecomment-20487980
--
This SF.net email is sp
This is a test for github automated notifications - please ignore.
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/issues/95#issuecomment-20487831
--
This SF.net email is sponsored
This is a test - please ignore.
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/issues/95#issuecomment-20487661
--
This SF.net email is sponsored by Windows:
Build for Windows Sto
Closed #95 via b4c18fac65a594502eec5edd2611d5953e7950f7.
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/issues/95
--
This SF.net email is sponsored by Windows:
Build for Windows
This server 2 purposes:
1) We use lazy free-ing of the callback structure, for it to be actually
free-ed usbi_hotplug_match() needs to be called. This ensures this actually
happens (rather then waiting for a hotplug event to arrive, and not freeing
the callback as long as no such event arrives).
Hi All,
So to make sure the API is sane, and to give the hotplug stuff some extra
testing, I've ported Spice's usbredir code over to it.
And everything worked in one go, until I tried to exit the spice client, at
which point it hangs.
The problem is that the spice usbredir code uses a thread whi
So that the device parameter can be NULL, in combination with a 0
events parameter, to be used to force lazy deregistration.
Signed-off-by: Hans de Goede
---
libusb/hotplug.c | 15 +++
libusb/hotplug.h | 3 ++-
libusb/io.c | 2 +-
libusb/version_nano.h | 2 +-
Hi,
On 07/03/2013 05:10 PM, Chris McClelland wrote:
> Hi libusbx-devel,
>
> I'd like to write an application which uses the "simple" async approach.
> I can't use the polled approach because I'd like my code to be portable
> to Windows.
>
> Here's a scenario:
>
> The main thread creates the worker
Hi,
On 07/03/2013 11:44 PM, Pete Batard wrote:
> If I don't do it today, it'll never happen, so here goes for review.
Looks good, ack.
Regards,
Hans
--
This SF.net email is sponsored by Windows:
Build for Windows Stor
Signed-off-by: Hans de Goede
---
libusb/descriptor.c | 3 +++
libusb/version_nano.h | 2 +-
2 files changed, 4 insertions(+), 1 deletion(-)
diff --git a/libusb/descriptor.c b/libusb/descriptor.c
index ec5c344..ba6d146 100644
--- a/libusb/descriptor.c
+++ b/libusb/descriptor.c
@@ -541,6 +541,9
On Tue, Jul 2, 2013 at 10:11 PM, Xiaofan Chen wrote:
> On Mon, Jul 1, 2013 at 7:14 PM, Hans de Goede wrote:
>> You can find 1.0.16-rc2 docs including all the new API-s here:
>> http://people.fedoraproject.org/~jwrdegoede/libusb-reference/
>
> One issue here:
> http://people.fedoraproject.org/~jwr
On Wed, Jul 3, 2013 at 3:29 AM, Sean McBride wrote:
> On Tue, 2 Jul 2013 23:18:12 +0400, Paul Fertser said:
>>What about documenting this in some special "API bugs" file or
>>documentation section?
>
> We should definitely have a bug for "make libusb -Wcast-align safe"...
Would you please create
15 matches
Mail list logo
