>>> WinUsb_GetAssociatedInterface should be the magic you need.
>> Thanks, I'll try that.
That was what I was missing! The call didn't appear any where in the
Microsoft example. Thanks!
> I'm also curious with the results you'll get from bypassing libusbx
> altogether.
I implemented my test wi
On 2013.05.29 01:17, qse drf wrote:
>> WinUsb_GetAssociatedInterface should be the magic you need.
> Thanks, I'll try that.
I'm also curious with the results you'll get from bypassing libusbx
altogether.
As you may expect, the fact that you seem to be seeing the same
behaviour with very differe
On 2013.05.28 23:08, Tim Roberts wrote:
> Hans de Goede wrote:
>> I would like to give libusb using applications to os cached string
>> descriptors, so that those can be accessed without the need to open a
>> device and do io on it.
>
> The device is already open, because your API requires a libusb
On 2013.05.28 11:25, Hans de Goede wrote:
> +int LIBUSB_CALL libusb_set_strerror_locale(const char *locale);
> +const char * LIBUSB_CALL libusb_strerror(enum libusb_error errcode);
Why not go:
const char * LIBUSB_CALL libusb_strerror(enum libusb_error errcode,
const char *locale);
?
Since it's b
Finally got a chance to check out the updated branch.
First, the usual stream of compilation errors:
1. cygwin is being an ass (as usual), with:
sam3u_benchmark.c: In function ‘benchmark_in’:
sam3u_benchmark.c:100:5: warning: passing argument 7 of
‘libusb_fill_iso_transfer’ from incompatible po
>> I checked the inf created by Zadig, and it claims the entire device. I
>> assumed this had to be the case, since libusbx is able to acces both
>> interfaces.
>
> You can modify that INF...
But it works as-is with libusbx.
>
>> I'm going to keep trying to figure out how to use WinUSB directly.
>
Hans de Goede wrote:
> I would like to give libusb using applications to os cached string
> descriptors, so that those can be accessed without the need to open a
> device and do io on it.
The device is already open, because your API requires a libusb_device,
right? So, you're saving the cost of o
Hi,
On 05/28/2013 10:38 PM, Ludovic Rousseau wrote:
> 2013/5/28 Tim Roberts :
>> Hans de Goede wrote:
>>> Sorry no code (yet), as I would first like to get some buy in for
>>> the concept before spending time on coding this.
>>>
>>> For apps which show a list of usb devices to the user, it is usef
Hi,
On 05/28/2013 09:58 PM, Tim Roberts wrote:
> Hans de Goede wrote:
>> Sorry no code (yet), as I would first like to get some buy in for
>> the concept before spending time on coding this.
>>
>> For apps which show a list of usb devices to the user, it is useful
>> to have some userfriendly desc
qse drf wrote:
> I checked the inf created by Zadig, and it claims the entire device. I
> assumed this had to be the case, since libusbx is able to acces both
> interfaces.
You can modify that INF...
> I'm going to keep trying to figure out how to use WinUSB directly.
WinUsb_GetAssociatedInter
2013/5/28 Tim Roberts :
> Hans de Goede wrote:
>> Sorry no code (yet), as I would first like to get some buy in for
>> the concept before spending time on coding this.
>>
>> For apps which show a list of usb devices to the user, it is useful
>> to have some userfriendly description of the device to
Hans de Goede wrote:
> Sorry no code (yet), as I would first like to get some buy in for
> the concept before spending time on coding this.
>
> For apps which show a list of usb devices to the user, it is useful
> to have some userfriendly description of the device to show.
>
> I've code for this i
>>> So this seems like a bug in libusbx that it doesn't seem to honor the
>>> synchronous API expectations in this case, as evidenced by the
>>> concatenating of the
>>> buffers from multiple calls. Or am I missing something?
>>
>> Can you try using the libusb-win32 or libusbK driver instead of Wi
Hi,
Sorry no code (yet), as I would first like to get some buy in for
the concept before spending time on coding this.
For apps which show a list of usb devices to the user, it is useful
to have some userfriendly description of the device to show.
I've code for this in spice-gtk, which I think r
Hi,
Thanks for the comments and the review.
On 05/28/2013 01:10 PM, Ludovic Rousseau wrote:
> Hello,
>
> 2013/5/28 Hans de Goede :
>> This patch adds the much requested libusb_strerror() function, taking into
>> account all issues people raised wrt previous attempts.
>>
>> Criteria / Decisions un
Hello,
2013/5/28 Hans de Goede :
> This patch adds the much requested libusb_strerror() function, taking into
> account all issues people raised wrt previous attempts.
>
> Criteria / Decisions underlying this implementation:
> -Must support translated messages
> -Must not use gettext as that does
Hi,
I had hardcoded the values of sysfs_can_relate_devices and
sysfs_has_descriptors to 0, to also test the code paths for older
kernels, and this accidentally ended up in the
"POSIX: Move setting of pipes to non-blocking into usbi_pipe"
commit.
I've now pushed a fixed tree to the darwin-integrat
This patch adds the much requested libusb_strerror() function, taking into
account all issues people raised wrt previous attempts.
Criteria / Decisions underlying this implementation:
-Must support translated messages
-Must not use gettext as that does not work well in combination with Windows
(w
18 matches
Mail list logo
