Re: [Libusbx-devel] [PATCH] Add topology calls, v2

2012-05-15 Thread Pete Batard
On 2012.05.15 01:03, Pete Batard wrote: > Could be that we're > trying to access unref'd and restroyed parent devices on OS-X, hence the > seemingly random outcome. Yup. Confirmed that some of the parents we're trying to access get unref'd and destroyed before we attempt to access their data. If

Re: [Libusbx-devel] [RFC PATCH] windows_usb: get_device_list: if the backend api changed, use the new api

2012-05-15 Thread Pete Batard
On 2012.05.14 19:47, Uri Lublin wrote: > When I started the implementation, I was not aware of libusb plans > on supporting hotplug in the near future. Yeah that's the issue we had with libusb and part of why we forked. Libusb has been so bottlenecked with issues that should have been dealt with

Re: [Libusbx-devel] [RFC PATCH] windows_usb: get_device_list: if the backend api changed, use the new api

2012-05-15 Thread Pete Batard
On 2012.05.14 20:21, Uri Lublin wrote: > (I also changed -k option's according to vid:pid of a usb disk I'm > testing with) The fact that you tested with an usb disk may explain a few things. In that case, you're _replacing_ an existing driver (mass storage -> WinUSB) rather than installing a ne

Re: [Libusbx-devel] [RFC PATCH] windows_usb: get_device_list: if the backend api changed, use the new api

2012-05-15 Thread Pete Batard
On 2012.05.15 04:42, Peter Stuge wrote: >> if you want to dismiss the Windows backend as full of bugs > > I never wrote that and I never hinted at that. > > This email thread is about just one bug. Quote: "the Windows backend doesn't really deliver because of this bug and with a few others". >>