libusb-win32-devel

Re: [Libusb-win32-devel] (no subject)

[Tanis 'S. N. - ****&c. <ta...@de...>]

I tried, but Safe mode BSODs too. I've ran chkdsk, DISM and sfc /scannow, but it's still just bootlooping.
I guess I'll reinstall. Thanks for the quick response.


/beep
Den 18. november 2024, kl. 08.54 Centraleuropæisk normaltid, skrev Xiaofan Chen <xia...@gm...>:

> Hmm, class filters were not supported long ago.
> 
> Please try to boot into safe mode and then remove libusb-win32 in this case.
> 
> Best regards,
> Xiaofan
> 
> On Mon, Nov 18, 2024 at 8:50 AM Tanis 'Silke' Nielsen - ****&c.
> <<ta...@de...>> wrote:
> 
> > 
> > 
> > So, I did something stupid.
> > I've been using libusb to filter a device, and instead of running Filter Wizard,
> > I accidentally clicked Install all class filters.
> > Libusb did its thing, and then came an immediate BSOD.
> > Now I get a STOP 0x0000007B (INACCESSIBLE_BOOT_DEVICE) everytime
> > I try to boot. What did I do? Any ideas? I was using 1.2.7.3. (it's outdated, I know.
> > I was a bit confused during the install process)
> > 
> > cheers
> > /beep
> > 
> 
> _______________________________________________
> Libusb-win32-devel mailing list
> Lib...@li...
> <https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel>
> 

Re: [Libusb-win32-devel] (no subject)

[Xiaofan C. <xia...@gm...>]

Hmm, class filters were not supported long ago.

Please try to boot into safe mode and then remove libusb-win32 in this case.

Best regards,
Xiaofan

On Mon, Nov 18, 2024 at 8:50 AM Tanis 'Silke' Nielsen - ****&c.
<ta...@de...> wrote:
>
>
> So, I did something stupid.
> I've been using libusb to filter a device, and instead of running Filter Wizard,
> I accidentally clicked Install all class filters.
> Libusb did its thing, and then came an immediate BSOD.
> Now I get a STOP 0x0000007B (INACCESSIBLE_BOOT_DEVICE) everytime
> I try to boot. What did I do? Any ideas? I was using 1.2.7.3. (it's outdated, I know.
> I was a bit confused during the install process)
>
> cheers
> /beep
>

[Libusb-win32-devel] (no subject)

[Tanis 'S. N. - ****&c. <ta...@de...>]

So, I did something stupid.
I've been using libusb to filter a device, and instead of running Filter Wizard, I accidentally clicked Install all class filters.
Libusb did its thing, and then came an immediate BSOD.
Now I get a STOP 0x0000007B (INACCESSIBLE_BOOT_DEVICE) everytime I try to boot. What did I do? Any ideas? I was using 1.2.7.3. (it's outdated, I know. I was a bit confused during the install process)

cheers
/beep

Re: [Libusb-win32-devel] Licensing for USB Inf Creator / Installer and libraries

[Kilbane, S. <Ste...@an...>]

Thanks Xianfan.

> Do you mean that the developer uses libusbK GUI inf-wizard to create the driver installer?

That’s my understanding, yes.  I’m trying to establish what licenses apply to the wizard, and what licenses apply to the resulting installed libraries.

Typically, an installer is distinct from the payload it installs, so a GPL installer wouldn’t be problematic for a commercial payload, and a GPL payload wouldn’t be problematic for a commercial installer. Since, in this case, the libraries are getting created as well, I can’t tell where the boundary lies, and so what code is part of the installer, versus what code is part of the payload libraries.

> Take note I am not a lawyer so you may want to talk to your legal department

Oh, sure. We’ll definitely engage with our own legal folks for confirmation on actions that relate to the licenses. But which licenses is a technical question since it’s “what gets linked where”.

I’ll pass your response onto the development team in the hope that it guides them.

steve

From: Xiaofan Chen <xia...@gm...>
Date: Thursday, 10 October 2024 at 12:33
To: lib...@li... <lib...@li...>
Subject: Re: [Libusb-win32-devel] Licensing for USB Inf Creator / Installer and libraries
Do you mean that the developer uses libusbK GUI inf-wizard to create the
driver installer?

libusbK license: you can choose the BSD option (except portions using libwdi
which uses LGPL v3 license).
https://github.com/mcuee/libusbk/blob/master/libusbK/license/AUTHORS-libusbK.txt

The installer uses libwdi, which uses LGPL v3 license.
https://github.com/pbatard/libwdi

The installer does not modify libusb0.sys and libusb0.dll, so you do not need to
worry about the distribution of libusb0.sys (GPL v3 license) and libusb0.dll
(LGPL license v3)
https://github.com/mcuee/libusb-win32/blob/master/libusb/installer_license.txt

I can see the only issue seems to be the libwdi linkage of the libusbK
GUI installer tool
(which may force it to be GPLv3 licensed because of static linking).
However, I believe
the driver installer created by the tool does not fall into GPLv3
license. You do need to
mention the license of the components, like the license of
libusb0.sys/libusb0.dll and
libusbK.sys/libusbK.dll. You may also want to mention the driver
installer is created
using the libusbK GUI Inf wizard tool and its license.

Take note I am not a lawyer so you may want to talk to your legal department
with the above information which can not be considered as legal advice
but rather
my personal opinion.

Best regards,
Xiaofan

On Thu, Oct 10, 2024 at 6:38 PM Kilbane, Stephen
<Ste...@an...> wrote:
>
> Hi all,
>
> Is there information that outlines which licenses apply to which libraries?
>
> One of our developers is using USB Inf Creator/Installer, targeting WinUsb, libusbK
> and libusb0. Our OSS compliance processes identified a variety of weak/strong copyleft licenses.
>
> As I understand things – and I’m not the developer working with libusbK, so I may have
>  this wrong – the developer is using the Creator / Installer to create the libraries as well as
>  to install them. Given that there are multiple stages involved, I’m struggling to understand
> which licenses apply to the creator/installer, and which apply to the resulting libraries –
>  and since I’m not the developer working with this package, I’m not able to see where the
> boundaries lie between components, in the source tree.
>
> We’re keen to make sure we fulfil any and all licensing obligations, so ny guidance
> gratefully appreciated.
>
> Thanks,
>
> steve
>
> --
>
> Stephen Kilbane
>
> Director,
> Open Source Program Office
>
> Tel +44 131 346-3450
> Email ste...@an...
>
> _______________________________________________
> Libusb-win32-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel


_______________________________________________
Libusb-win32-devel mailing list
Lib...@li...
https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel

Re: [Libusb-win32-devel] Licensing for USB Inf Creator / Installer and libraries

[Xiaofan C. <xia...@gm...>]

Do you mean that the developer uses libusbK GUI inf-wizard to create the
driver installer?

libusbK license: you can choose the BSD option (except portions using libwdi
which uses LGPL v3 license).
https://github.com/mcuee/libusbk/blob/master/libusbK/license/AUTHORS-libusbK.txt

The installer uses libwdi, which uses LGPL v3 license.
https://github.com/pbatard/libwdi

The installer does not modify libusb0.sys and libusb0.dll, so you do not need to
worry about the distribution of libusb0.sys (GPL v3 license) and libusb0.dll
(LGPL license v3)
https://github.com/mcuee/libusb-win32/blob/master/libusb/installer_license.txt

I can see the only issue seems to be the libwdi linkage of the libusbK
GUI installer tool
(which may force it to be GPLv3 licensed because of static linking).
However, I believe
the driver installer created by the tool does not fall into GPLv3
license. You do need to
mention the license of the components, like the license of
libusb0.sys/libusb0.dll and
libusbK.sys/libusbK.dll. You may also want to mention the driver
installer is created
using the libusbK GUI Inf wizard tool and its license.

Take note I am not a lawyer so you may want to talk to your legal department
with the above information which can not be considered as legal advice
but rather
my personal opinion.

Best regards,
Xiaofan

On Thu, Oct 10, 2024 at 6:38 PM Kilbane, Stephen
<Ste...@an...> wrote:
>
> Hi all,
>
> Is there information that outlines which licenses apply to which libraries?
>
> One of our developers is using USB Inf Creator/Installer, targeting WinUsb, libusbK
> and libusb0. Our OSS compliance processes identified a variety of weak/strong copyleft licenses.
>
> As I understand things – and I’m not the developer working with libusbK, so I may have
>  this wrong – the developer is using the Creator / Installer to create the libraries as well as
>  to install them. Given that there are multiple stages involved, I’m struggling to understand
> which licenses apply to the creator/installer, and which apply to the resulting libraries –
>  and since I’m not the developer working with this package, I’m not able to see where the
> boundaries lie between components, in the source tree.
>
> We’re keen to make sure we fulfil any and all licensing obligations, so ny guidance
> gratefully appreciated.
>
> Thanks,
>
> steve
>
> --
>
> Stephen Kilbane
>
> Director,
> Open Source Program Office
>
> Tel +44 131 346-3450
> Email ste...@an...
>
> _______________________________________________
> Libusb-win32-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel

[Libusb-win32-devel] Licensing for USB Inf Creator / Installer and libraries

[Kilbane, S. <Ste...@an...>]

Hi all,

Is there information that outlines which licenses apply to which libraries?

One of our developers is using USB Inf Creator/Installer, targeting WinUsb, libusbK and libusb0. Our OSS compliance processes identified a variety of weak/strong copyleft licenses.

As I understand things – and I’m not the developer working with libusbK, so I may have this wrong – the developer is using the Creator / Installer to create the libraries as well as to install them. Given that there are multiple stages involved, I’m struggling to understand which licenses apply to the creator/installer, and which apply to the resulting libraries – and since I’m not the developer working with this package, I’m not able to see where the boundaries lie between components, in the source tree.

We’re keen to make sure we fulfil any and all licensing obligations, so ny guidance gratefully appreciated.

Thanks,

steve
--
Stephen Kilbane
Director,
Open Source Program Office

Tel +44 131 346-3450
Email ste...@an...<mailto:ste...@an...>

[Libusb-win32-devel] libusb-win32 kernel interface passthrough for composite device

[Raymond B. <ray...@gm...>]

 Hello, I'm looking to write a Windows driver/achieve similar functionality
using libusb-win32 for the Apple iPad. I wish to achieve the following with
the driver:

1. The driver should be able to send vendor-specific control messages to
the device (to expose a CDC NCM interface in a new configuration).
2. The driver should be able to set the device's USB configuration (to this
new configuration).
3. The driver should pass through the PTP and Apple USBMUX interfaces to
their appropriate (and default) drivers.
4. The driver should configure and present the NCM Data and NCM Control
interfaces as a Windows Network Adapter.

>From these requirements, I'm thinking that this driver will have a similar
role as the Windows Generic Parent Driver. My questions are:

1. Is the "passthrough" of interfaces possible with the libusb-win32 kernel
driver? Or will I have to write my own?
2. Windows recently added support for UMDF NetAdapterCx drivers. Would a
driver like that be able to communicate with libusb's kernel driver? Or
would it have to be bundled within the kernel driver itself?

Thanks in advance

Re: [Libusb-win32-devel] Getting Error URB_FUNCTION_ABORT_PIPE

[Tormod V. <lis...@gm...>]

Use the official Zadig 2.6, it has 1.2.6.0 embedded.

Tormod

On Tue, May 28, 2024 at 10:07 PM Mayur Purandare
<may...@gm...> wrote:
>
> Hello,
> A kind reminder.
> Is there any way to rollback to 1.2.6.0
> Thank you.
>
> BR,
> Mayur
>
> On Thu, 23 May, 2024, 8:24 am Mayur Purandare, <may...@gm...> wrote:
>>
>> Hello,
>>
>> I tried to install the driver 1.4.0.0 over the previous version i.e. 1.2.6.0using Zadig tool. However,  now I am not able to connect to my hardware. I tried to reinstall the previous version. It gets installed but I still cannot communicate with the hardware.
>> Please guide.
>> Thank you.
>>
>> Regards,
>> Mayur.
>>
>> On Fri, 17 May, 2024, 11:40 am Mayur Purandare, <may...@gm...> wrote:
>>>
>>> Hello xiaofanc,
>>>
>>> Thank you for your reply.
>>> We will try this.
>>> Thank you.
>>>
>>> Regards,
>>> Mayur
>>>
>>> On Fri, 17 May, 2024, 11:11 am Xiaofan Chen, <xia...@gm...> wrote:
>>>>
>>>> No. That libusbk inf wizard is not part of libusb-win32 project, but rather part of libusbK project.
>>>>
>>>> You can use the bundled Zadig utility to install libusb-win32 1.4.0 device driver. You can also use libwdi wdi-simple example as a template to write your own driver installer.
>>>> https://github.com/pbatard/libwdi/tree/master/examples
>>>>
>>>> Regards,
>>>> Xiaofan
>>>>
>>>> On Fri, May 17, 2024, 12:53 Mayur Purandare <may...@gm...> wrote:
>>>>>
>>>>> Hello,
>>>>> A kind reminder. Is there any inf wizard utility available to create the 1.4.0.0 driver?
>>>>> Kindly let me know.
>>>>>
>>>>> Thank you
>>>>>
>>>>> Regards,
>>>>> Mayur
>>>>>
>>>>>
>>>>> On Tue, 14 May, 2024, 10:19 am Mayur Purandare, <may...@gm...> wrote:
>>>>>>
>>>>>> Hello Tormod,
>>>>>>
>>>>>> Firstly, apologies for posting the wrong link.
>>>>>> We had created this driver using the INF Wizard.  (The Screenshot is in the attachment.) as mentioned in the first comment of the link below.
>>>>>>
>>>>>> ==>> https://sourceforge.net/p/libusb-win32/support-requests/65/
>>>>>> (A screenshot of the comment is included)
>>>>>>
>>>>>> Is there any similar Driver Package creator available for version 1.4.0.0?
>>>>>>
>>>>>> Also, will it resolve the error we are facing i.e.  URB_FUNCTION_ABORT_PIPE or are there any more settings we need to do while invoking this?
>>>>>> (We are calling the communication functions in Asynchronous Methods.)
>>>>>>
>>>>>> Kindly let us know.
>>>>>>
>>>>>> Thank you.
>>>>>>
>>>>>> Regards,
>>>>>> Mayur
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Mon, 13 May 2024 at 13:08, Tormod Volden <lis...@gm...> wrote:
>>>>>>>
>>>>>>> On Mon, May 13, 2024 at 3:38 AM Mayur Purandare wrote:
>>>>>>>
>>>>>>> > Thank you very much for your reply regarding the updated version.
>>>>>>> > However, is there any installable available for this version as it is there for 1.2.6.0 (link below)
>>>>>>>
>>>>>>> I believe you can use the zadig_2.8_mod_1400.exe executable to install
>>>>>>> the driver. This is zadig 2.8 modified to include libusb0.sys 1.4.0.0.
>>>>>>>
>>>>>>> > https://sourceforge.net/projects/libusb-win32/files/libusb-win32-releases/1.2.6.0/libusb-win32-devel-filter-1.2.6.0.exe/download
>>>>>>> >
>>>>>>> > The install exe available at the above link is also signed so that it can run on Windows 10 and 11.
>>>>>>>
>>>>>>> Do you use libusb0.sys as a filter driver?
>>>>>>>
>>>>>>> Tormod
>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> Libusb-win32-devel mailing list
>>>>>>> Lib...@li...
>>>>>>> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
>>>>>
>>>>> _______________________________________________
>>>>> Libusb-win32-devel mailing list
>>>>> Lib...@li...
>>>>> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
>>>>
>>>> _______________________________________________
>>>> Libusb-win32-devel mailing list
>>>> Lib...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
>
> _______________________________________________
> Libusb-win32-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel

Re: [Libusb-win32-devel] Getting Error URB_FUNCTION_ABORT_PIPE

[Mayur P. <may...@gm...>]

Hello,
A kind reminder.
Is there any way to rollback to 1.2.6.0
Thank you.

BR,
Mayur

On Thu, 23 May, 2024, 8:24 am Mayur Purandare, <may...@gm...>
wrote:

> Hello,
>
> I tried to install the driver 1.4.0.0 over the previous version i.e.
> 1.2.6.0using Zadig tool. However,  now I am not able to connect to my
> hardware. I tried to reinstall the previous version. It gets installed but
> I still cannot communicate with the hardware.
> Please guide.
> Thank you.
>
> Regards,
> Mayur.
>
> On Fri, 17 May, 2024, 11:40 am Mayur Purandare, <
> may...@gm...> wrote:
>
>> Hello xiaofanc,
>>
>> Thank you for your reply.
>> We will try this.
>> Thank you.
>>
>> Regards,
>> Mayur
>>
>> On Fri, 17 May, 2024, 11:11 am Xiaofan Chen, <xia...@gm...> wrote:
>>
>>> No. That libusbk inf wizard is not part of libusb-win32 project, but
>>> rather part of libusbK project.
>>>
>>> You can use the bundled Zadig utility to install libusb-win32 1.4.0
>>> device driver. You can also use libwdi wdi-simple example as a template to
>>> write your own driver installer.
>>> https://github.com/pbatard/libwdi/tree/master/examples
>>>
>>> Regards,
>>> Xiaofan
>>>
>>> On Fri, May 17, 2024, 12:53 Mayur Purandare <may...@gm...>
>>> wrote:
>>>
>>>> Hello,
>>>> A kind reminder. Is there any inf wizard utility available to create
>>>> the 1.4.0.0 driver?
>>>> Kindly let me know.
>>>>
>>>> Thank you
>>>>
>>>> Regards,
>>>> Mayur
>>>>
>>>>
>>>> On Tue, 14 May, 2024, 10:19 am Mayur Purandare, <
>>>> may...@gm...> wrote:
>>>>
>>>>> Hello Tormod,
>>>>>
>>>>> Firstly, apologies for posting the wrong link.
>>>>> We had created this driver using the INF Wizard.  (The Screenshot is
>>>>> in the attachment.) as mentioned in the first comment of the link below.
>>>>>
>>>>> ==>> https://sourceforge.net/p/libusb-win32/support-requests/65/
>>>>> (A screenshot of the comment is included)
>>>>>
>>>>> Is there any similar Driver Package creator available for version
>>>>> 1.4.0.0?
>>>>>
>>>>> Also, will it resolve the error we are facing
>>>>> i.e.  URB_FUNCTION_ABORT_PIPE or are there any more settings we need to do
>>>>> while invoking this?
>>>>> (We are calling the communication functions in Asynchronous Methods.)
>>>>>
>>>>> Kindly let us know.
>>>>>
>>>>> Thank you.
>>>>>
>>>>> Regards,
>>>>> Mayur
>>>>>
>>>>>
>>>>>
>>>>> On Mon, 13 May 2024 at 13:08, Tormod Volden <lis...@gm...>
>>>>> wrote:
>>>>>
>>>>>> On Mon, May 13, 2024 at 3:38 AM Mayur Purandare wrote:
>>>>>>
>>>>>> > Thank you very much for your reply regarding the updated version.
>>>>>> > However, is there any installable available for this version as it
>>>>>> is there for 1.2.6.0 (link below)
>>>>>>
>>>>>> I believe you can use the zadig_2.8_mod_1400.exe executable to install
>>>>>> the driver. This is zadig 2.8 modified to include libusb0.sys 1.4.0.0.
>>>>>>
>>>>>> >
>>>>>> https://sourceforge.net/projects/libusb-win32/files/libusb-win32-releases/1.2.6.0/libusb-win32-devel-filter-1.2.6.0.exe/download
>>>>>> >
>>>>>> > The install exe available at the above link is also signed so that
>>>>>> it can run on Windows 10 and 11.
>>>>>>
>>>>>> Do you use libusb0.sys as a filter driver?
>>>>>>
>>>>>> Tormod
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> Libusb-win32-devel mailing list
>>>>>> Lib...@li...
>>>>>> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
>>>>>>
>>>>> _______________________________________________
>>>> Libusb-win32-devel mailing list
>>>> Lib...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
>>>>
>>> _______________________________________________
>>> Libusb-win32-devel mailing list
>>> Lib...@li...
>>> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
>>>
>>

Re: [Libusb-win32-devel] Getting Error URB_FUNCTION_ABORT_PIPE

[Mayur P. <may...@gm...>]

Hello,

I tried to install the driver 1.4.0.0 over the previous version i.e.
1.2.6.0using Zadig tool. However,  now I am not able to connect to my
hardware. I tried to reinstall the previous version. It gets installed but
I still cannot communicate with the hardware.
Please guide.
Thank you.

Regards,
Mayur.

On Fri, 17 May, 2024, 11:40 am Mayur Purandare, <may...@gm...>
wrote:

> Hello xiaofanc,
>
> Thank you for your reply.
> We will try this.
> Thank you.
>
> Regards,
> Mayur
>
> On Fri, 17 May, 2024, 11:11 am Xiaofan Chen, <xia...@gm...> wrote:
>
>> No. That libusbk inf wizard is not part of libusb-win32 project, but
>> rather part of libusbK project.
>>
>> You can use the bundled Zadig utility to install libusb-win32 1.4.0
>> device driver. You can also use libwdi wdi-simple example as a template to
>> write your own driver installer.
>> https://github.com/pbatard/libwdi/tree/master/examples
>>
>> Regards,
>> Xiaofan
>>
>> On Fri, May 17, 2024, 12:53 Mayur Purandare <may...@gm...>
>> wrote:
>>
>>> Hello,
>>> A kind reminder. Is there any inf wizard utility available to create the
>>> 1.4.0.0 driver?
>>> Kindly let me know.
>>>
>>> Thank you
>>>
>>> Regards,
>>> Mayur
>>>
>>>
>>> On Tue, 14 May, 2024, 10:19 am Mayur Purandare, <
>>> may...@gm...> wrote:
>>>
>>>> Hello Tormod,
>>>>
>>>> Firstly, apologies for posting the wrong link.
>>>> We had created this driver using the INF Wizard.  (The Screenshot is in
>>>> the attachment.) as mentioned in the first comment of the link below.
>>>>
>>>> ==>> https://sourceforge.net/p/libusb-win32/support-requests/65/
>>>> (A screenshot of the comment is included)
>>>>
>>>> Is there any similar Driver Package creator available for version
>>>> 1.4.0.0?
>>>>
>>>> Also, will it resolve the error we are facing
>>>> i.e.  URB_FUNCTION_ABORT_PIPE or are there any more settings we need to do
>>>> while invoking this?
>>>> (We are calling the communication functions in Asynchronous Methods.)
>>>>
>>>> Kindly let us know.
>>>>
>>>> Thank you.
>>>>
>>>> Regards,
>>>> Mayur
>>>>
>>>>
>>>>
>>>> On Mon, 13 May 2024 at 13:08, Tormod Volden <lis...@gm...>
>>>> wrote:
>>>>
>>>>> On Mon, May 13, 2024 at 3:38 AM Mayur Purandare wrote:
>>>>>
>>>>> > Thank you very much for your reply regarding the updated version.
>>>>> > However, is there any installable available for this version as it
>>>>> is there for 1.2.6.0 (link below)
>>>>>
>>>>> I believe you can use the zadig_2.8_mod_1400.exe executable to install
>>>>> the driver. This is zadig 2.8 modified to include libusb0.sys 1.4.0.0.
>>>>>
>>>>> >
>>>>> https://sourceforge.net/projects/libusb-win32/files/libusb-win32-releases/1.2.6.0/libusb-win32-devel-filter-1.2.6.0.exe/download
>>>>> >
>>>>> > The install exe available at the above link is also signed so that
>>>>> it can run on Windows 10 and 11.
>>>>>
>>>>> Do you use libusb0.sys as a filter driver?
>>>>>
>>>>> Tormod
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Libusb-win32-devel mailing list
>>>>> Lib...@li...
>>>>> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
>>>>>
>>>> _______________________________________________
>>> Libusb-win32-devel mailing list
>>> Lib...@li...
>>> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
>>>
>> _______________________________________________
>> Libusb-win32-devel mailing list
>> Lib...@li...
>> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
>>
>

Re: [Libusb-win32-devel] Getting Error URB_FUNCTION_ABORT_PIPE

[Mayur P. <may...@gm...>]

Hello xiaofanc,

Thank you for your reply.
We will try this.
Thank you.

Regards,
Mayur

On Fri, 17 May, 2024, 11:11 am Xiaofan Chen, <xia...@gm...> wrote:

> No. That libusbk inf wizard is not part of libusb-win32 project, but
> rather part of libusbK project.
>
> You can use the bundled Zadig utility to install libusb-win32 1.4.0 device
> driver. You can also use libwdi wdi-simple example as a template to write
> your own driver installer.
> https://github.com/pbatard/libwdi/tree/master/examples
>
> Regards,
> Xiaofan
>
> On Fri, May 17, 2024, 12:53 Mayur Purandare <may...@gm...>
> wrote:
>
>> Hello,
>> A kind reminder. Is there any inf wizard utility available to create the
>> 1.4.0.0 driver?
>> Kindly let me know.
>>
>> Thank you
>>
>> Regards,
>> Mayur
>>
>>
>> On Tue, 14 May, 2024, 10:19 am Mayur Purandare, <
>> may...@gm...> wrote:
>>
>>> Hello Tormod,
>>>
>>> Firstly, apologies for posting the wrong link.
>>> We had created this driver using the INF Wizard.  (The Screenshot is in
>>> the attachment.) as mentioned in the first comment of the link below.
>>>
>>> ==>> https://sourceforge.net/p/libusb-win32/support-requests/65/
>>> (A screenshot of the comment is included)
>>>
>>> Is there any similar Driver Package creator available for version
>>> 1.4.0.0?
>>>
>>> Also, will it resolve the error we are facing
>>> i.e.  URB_FUNCTION_ABORT_PIPE or are there any more settings we need to do
>>> while invoking this?
>>> (We are calling the communication functions in Asynchronous Methods.)
>>>
>>> Kindly let us know.
>>>
>>> Thank you.
>>>
>>> Regards,
>>> Mayur
>>>
>>>
>>>
>>> On Mon, 13 May 2024 at 13:08, Tormod Volden <lis...@gm...>
>>> wrote:
>>>
>>>> On Mon, May 13, 2024 at 3:38 AM Mayur Purandare wrote:
>>>>
>>>> > Thank you very much for your reply regarding the updated version.
>>>> > However, is there any installable available for this version as it is
>>>> there for 1.2.6.0 (link below)
>>>>
>>>> I believe you can use the zadig_2.8_mod_1400.exe executable to install
>>>> the driver. This is zadig 2.8 modified to include libusb0.sys 1.4.0.0.
>>>>
>>>> >
>>>> https://sourceforge.net/projects/libusb-win32/files/libusb-win32-releases/1.2.6.0/libusb-win32-devel-filter-1.2.6.0.exe/download
>>>> >
>>>> > The install exe available at the above link is also signed so that it
>>>> can run on Windows 10 and 11.
>>>>
>>>> Do you use libusb0.sys as a filter driver?
>>>>
>>>> Tormod
>>>>
>>>>
>>>> _______________________________________________
>>>> Libusb-win32-devel mailing list
>>>> Lib...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
>>>>
>>> _______________________________________________
>> Libusb-win32-devel mailing list
>> Lib...@li...
>> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
>>
> _______________________________________________
> Libusb-win32-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
>

Re: [Libusb-win32-devel] Getting Error URB_FUNCTION_ABORT_PIPE

[Xiaofan C. <xia...@gm...>]

No. That libusbk inf wizard is not part of libusb-win32 project, but rather
part of libusbK project.

You can use the bundled Zadig utility to install libusb-win32 1.4.0 device
driver. You can also use libwdi wdi-simple example as a template to write
your own driver installer.
https://github.com/pbatard/libwdi/tree/master/examples

Regards,
Xiaofan

On Fri, May 17, 2024, 12:53 Mayur Purandare <may...@gm...>
wrote:

> Hello,
> A kind reminder. Is there any inf wizard utility available to create the
> 1.4.0.0 driver?
> Kindly let me know.
>
> Thank you
>
> Regards,
> Mayur
>
>
> On Tue, 14 May, 2024, 10:19 am Mayur Purandare, <
> may...@gm...> wrote:
>
>> Hello Tormod,
>>
>> Firstly, apologies for posting the wrong link.
>> We had created this driver using the INF Wizard.  (The Screenshot is in
>> the attachment.) as mentioned in the first comment of the link below.
>>
>> ==>> https://sourceforge.net/p/libusb-win32/support-requests/65/
>> (A screenshot of the comment is included)
>>
>> Is there any similar Driver Package creator available for version 1.4.0.0?
>>
>> Also, will it resolve the error we are facing
>> i.e.  URB_FUNCTION_ABORT_PIPE or are there any more settings we need to do
>> while invoking this?
>> (We are calling the communication functions in Asynchronous Methods.)
>>
>> Kindly let us know.
>>
>> Thank you.
>>
>> Regards,
>> Mayur
>>
>>
>>
>> On Mon, 13 May 2024 at 13:08, Tormod Volden <lis...@gm...>
>> wrote:
>>
>>> On Mon, May 13, 2024 at 3:38 AM Mayur Purandare wrote:
>>>
>>> > Thank you very much for your reply regarding the updated version.
>>> > However, is there any installable available for this version as it is
>>> there for 1.2.6.0 (link below)
>>>
>>> I believe you can use the zadig_2.8_mod_1400.exe executable to install
>>> the driver. This is zadig 2.8 modified to include libusb0.sys 1.4.0.0.
>>>
>>> >
>>> https://sourceforge.net/projects/libusb-win32/files/libusb-win32-releases/1.2.6.0/libusb-win32-devel-filter-1.2.6.0.exe/download
>>> >
>>> > The install exe available at the above link is also signed so that it
>>> can run on Windows 10 and 11.
>>>
>>> Do you use libusb0.sys as a filter driver?
>>>
>>> Tormod
>>>
>>>
>>> _______________________________________________
>>> Libusb-win32-devel mailing list
>>> Lib...@li...
>>> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
>>>
>> _______________________________________________
> Libusb-win32-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
>

Re: [Libusb-win32-devel] Getting Error URB_FUNCTION_ABORT_PIPE

[Mayur P. <may...@gm...>]

Hello,
A kind reminder. Is there any inf wizard utility available to create the
1.4.0.0 driver?
Kindly let me know.

Thank you

Regards,
Mayur


On Tue, 14 May, 2024, 10:19 am Mayur Purandare, <may...@gm...>
wrote:

> Hello Tormod,
>
> Firstly, apologies for posting the wrong link.
> We had created this driver using the INF Wizard.  (The Screenshot is in
> the attachment.) as mentioned in the first comment of the link below.
>
> ==>> https://sourceforge.net/p/libusb-win32/support-requests/65/
> (A screenshot of the comment is included)
>
> Is there any similar Driver Package creator available for version 1.4.0.0?
>
> Also, will it resolve the error we are facing
> i.e.  URB_FUNCTION_ABORT_PIPE or are there any more settings we need to do
> while invoking this?
> (We are calling the communication functions in Asynchronous Methods.)
>
> Kindly let us know.
>
> Thank you.
>
> Regards,
> Mayur
>
>
>
> On Mon, 13 May 2024 at 13:08, Tormod Volden <lis...@gm...>
> wrote:
>
>> On Mon, May 13, 2024 at 3:38 AM Mayur Purandare wrote:
>>
>> > Thank you very much for your reply regarding the updated version.
>> > However, is there any installable available for this version as it is
>> there for 1.2.6.0 (link below)
>>
>> I believe you can use the zadig_2.8_mod_1400.exe executable to install
>> the driver. This is zadig 2.8 modified to include libusb0.sys 1.4.0.0.
>>
>> >
>> https://sourceforge.net/projects/libusb-win32/files/libusb-win32-releases/1.2.6.0/libusb-win32-devel-filter-1.2.6.0.exe/download
>> >
>> > The install exe available at the above link is also signed so that it
>> can run on Windows 10 and 11.
>>
>> Do you use libusb0.sys as a filter driver?
>>
>> Tormod
>>
>>
>> _______________________________________________
>> Libusb-win32-devel mailing list
>> Lib...@li...
>> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
>>
>

Re: [Libusb-win32-devel] Getting Error URB_FUNCTION_ABORT_PIPE

[Mayur P. <may...@gm...>]

Hello Tormod,

Firstly, apologies for posting the wrong link.
We had created this driver using the INF Wizard.  (The Screenshot is in the
attachment.) as mentioned in the first comment of the link below.

==>> https://sourceforge.net/p/libusb-win32/support-requests/65/
(A screenshot of the comment is included)

Is there any similar Driver Package creator available for version 1.4.0.0?

Also, will it resolve the error we are facing i.e.  URB_FUNCTION_ABORT_PIPE
or are there any more settings we need to do while invoking this?
(We are calling the communication functions in Asynchronous Methods.)

Kindly let us know.

Thank you.

Regards,
Mayur



On Mon, 13 May 2024 at 13:08, Tormod Volden <lis...@gm...> wrote:

> On Mon, May 13, 2024 at 3:38 AM Mayur Purandare wrote:
>
> > Thank you very much for your reply regarding the updated version.
> > However, is there any installable available for this version as it is
> there for 1.2.6.0 (link below)
>
> I believe you can use the zadig_2.8_mod_1400.exe executable to install
> the driver. This is zadig 2.8 modified to include libusb0.sys 1.4.0.0.
>
> >
> https://sourceforge.net/projects/libusb-win32/files/libusb-win32-releases/1.2.6.0/libusb-win32-devel-filter-1.2.6.0.exe/download
> >
> > The install exe available at the above link is also signed so that it
> can run on Windows 10 and 11.
>
> Do you use libusb0.sys as a filter driver?
>
> Tormod
>
>
> _______________________________________________
> Libusb-win32-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
>

Re: [Libusb-win32-devel] Getting Error URB_FUNCTION_ABORT_PIPE

[Tormod V. <lis...@gm...>]

On Mon, May 13, 2024 at 3:38 AM Mayur Purandare wrote:

> Thank you very much for your reply regarding the updated version.
> However, is there any installable available for this version as it is there for 1.2.6.0 (link below)

I believe you can use the zadig_2.8_mod_1400.exe executable to install
the driver. This is zadig 2.8 modified to include libusb0.sys 1.4.0.0.

> https://sourceforge.net/projects/libusb-win32/files/libusb-win32-releases/1.2.6.0/libusb-win32-devel-filter-1.2.6.0.exe/download
>
> The install exe available at the above link is also signed so that it can run on Windows 10 and 11.

Do you use libusb0.sys as a filter driver?

Tormod

Re: [Libusb-win32-devel] Getting Error URB_FUNCTION_ABORT_PIPE

[Mayur P. <may...@gm...>]

Hello Tormod,

Thank you very much for your reply regarding the updated version.
However, is there any installable available for this version as it is there
for 1.2.6.0 (link below)
https://sourceforge.net/projects/libusb-win32/files/libusb-win32-releases/1.2.6.0/libusb-win32-devel-filter-1.2.6.0.exe/download

The install exe available at the above link is also signed so that it can
run on Windows 10 and 11.

Thank you.

Regards,
Mayur

On Mon, 13 May 2024 at 02:09, Tormod Volden <lis...@gm...> wrote:

> On Fri, May 10, 2024 at 7:47 PM Mayur Purandare wrote:
> > We are using LibUSBDotNet 2.2.29 in our application. Along with this, we
> are using LibUsb Driver 1.2.6.0.
>
> > Is there any upgraded driver version available? Where can we get it?
>
> The latest libusb-win32 release is 1.4.0.0:
> https://github.com/mcuee/libusb-win32/releases
>
> Best regards,
> Tormod
>
>
> _______________________________________________
> Libusb-win32-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
>

Re: [Libusb-win32-devel] Getting Error URB_FUNCTION_ABORT_PIPE

[Tormod V. <lis...@gm...>]

On Fri, May 10, 2024 at 7:47 PM Mayur Purandare wrote:
> We are using LibUSBDotNet 2.2.29 in our application. Along with this, we are using LibUsb Driver 1.2.6.0.

> Is there any upgraded driver version available? Where can we get it?

The latest libusb-win32 release is 1.4.0.0:
https://github.com/mcuee/libusb-win32/releases

Best regards,
Tormod

[Libusb-win32-devel] Getting Error URB_FUNCTION_ABORT_PIPE

[Mayur P. <may...@gm...>]

Hello,
We are using LibUSBDotNet 2.2.29 in our application. Along with this, we
are using LibUsb Driver 1.2.6.0.
In our application, we communicate with our hardware periodically every 500
ms.
We observed that the application gets disconnected from the hardware and
with the error URB_FUNCTION_ABORT_PIPE.

Is there any setting we are missing while using this driver?
Is there any upgraded driver version available? Where can we get it?
Please advise.

Thank you.

BR,
Mayur

[Libusb-win32-devel] Restarting device power causes USB communication failure

[许叶洪 <yeh...@te...>]

Hi,

The GUI I wrote called libusb-win32 to communicate with Keysight DMM 34464A
via USB. During the communication process, I restarted the power supply of
the DMM. From the bus sound software, it appears that USB is no longer able
to send messages. Opening the GUI again allows for USB communication. After
opening the GUI several times, USB cannot send messages again. Why is this

Re: [Libusb-win32-devel] Provide a commercial (non-GPL) license

[Андрій О. <ost...@gm...>]

Dear libusb team,
Let me clarify – I am using unmodified libusb0.sys driver, however I do
sign the driver package with my own cert, using my own installer with a
custom .inf.
I would appreciate if you could confirm that this does not force me to
disclose my app source code, provided of course that I clearly state the
usage of libusb-win32 with the link to its repository

сб, 17 лют. 2024 р. о 16:35 Xiaofan Chen <xia...@gm...> пише:

> On Thu, Feb 8, 2024 at 1:30 AM Андрій Остапчук
> <ost...@gm...> wrote:
> >
> > Hello Libusb Team,
> > Do you provide a commercial (non-GPL) license for the libusb0.sys
> windows driver?
> > I would like to use my own installer for the driver and distribute it
> with my application without
> > being forced to disclose my app code. Unfortunately, I can't use the
> newest version of the
> >  libusbk due to a specific USB device I am connected to.
>
> Sorry but we do not.
>
> By integrating libusb-win32 device driver into your driver installer,
> you should not be
> required to change your driver installer license to be GPL, as long as
> you do not
> change the driver source code. You can just mention that your device
> driver is using
> libusb-win32 device driver and provide the web link to libusb-win32 github.
>
> Reference: similar question.
> https://github.com/pbatard/libwdi/issues/279
>
> BTW, I am not suggesting you use libwdi though as it is licensed
> under LGPL. Rather you can use other installers like Inno Setup.
>
> --
> Xiaofan
>
>
> _______________________________________________
> Libusb-win32-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
>

Re: [Libusb-win32-devel] Provide a commercial (non-GPL) license

[Xiaofan C. <xia...@gm...>]

On Thu, Feb 8, 2024 at 1:30 AM Андрій Остапчук
<ost...@gm...> wrote:
>
> Hello Libusb Team,
> Do you provide a commercial (non-GPL) license for the libusb0.sys windows driver?
> I would like to use my own installer for the driver and distribute it with my application without
> being forced to disclose my app code. Unfortunately, I can't use the newest version of the
>  libusbk due to a specific USB device I am connected to.

Sorry but we do not.

By integrating libusb-win32 device driver into your driver installer,
you should not be
required to change your driver installer license to be GPL, as long as
you do not
change the driver source code. You can just mention that your device
driver is using
libusb-win32 device driver and provide the web link to libusb-win32 github.

Reference: similar question.
https://github.com/pbatard/libwdi/issues/279

BTW, I am not suggesting you use libwdi though as it is licensed
under LGPL. Rather you can use other installers like Inno Setup.

-- 
Xiaofan

[Libusb-win32-devel] Provide a commercial (non-GPL) license

[Андрій О. <ost...@gm...>]

Hello Libusb Team,
Do you provide a commercial (non-GPL) license for the libusb0.sys windows
driver? I would like to use my own installer for the driver and distribute
it with my application without being forced to disclose my app code.
Unfortunately, I can't use the newest version of the libusbk due to a
specific USB device I am connected to.

Best regards,
Andrii Ostapchuk

[Libusb-win32-devel] Fwd: [libusb] Announcing libusb v1.0.27

[Xiaofan C. <xia...@gm...>]

FYI

---------- Forwarded message ---------
From: Tormod Volden <lis...@gm...>
Date: Thu, Feb 1, 2024 at 7:30 AM
Subject: [libusb] Announcing libusb v1.0.27
To: <lib...@li...>


We are happy to announce the final release of libusb 1.0.27.

ChangeLog with most important changes since 1.0.26:

* New libusb_init_context API to replace libusb_init
* New libusb_get_max_alt_packet_size API
* New libusb_get_platform_descriptor API (BOS)
* Allow setting log callback with libusb_set_option/libusb_init_context
* New WebAssembly + WebUSB backend using Emscripten
* Fix regression in libusb_set_interface_alt_setting
* Fix sync transfer completion race and use-after-free
* Fix hotplug exit ordering
* Linux: NO_DEVICE_DISCOVERY option set per context
* macOS: Fix missing device list cleanup locking
* macOS: Do not clear device data toggle for newer OS versions
* macOS: Fix running binaries on older OS than build host
* Windows: Allow claiming multiple associated interfaces
* Windows: Ignore non-configured devices instead of waiting
* Windows: Improved root hub detection

The source code tarball can be downloaded here:
https://github.com/libusb/libusb/releases/download/v1.0.27/libusb-1.0.27.tar.bz2

An archive of Windows binaries can be downloaded here:
https://github.com/libusb/libusb/releases/download/v1.0.27/libusb-1.0.27.7z

Note that the release tarball includes a configure script so unlike a
git checkout it is not necessary to bootstrap with autoconf.

The 1.0.27 release was made possible by the contributions from all
patch submitters (see below git shortlog with 158 commits from 31
contributors, of which 22 new!) plus everyone who contributed with
issue reporting, discussions and testing.

On behalf of the libusb development community,
Tormod


--


Addison Crump (1):
      descriptor: Guard against corrupted descriptor length field

Alex Feinman (1):
      windows: Refactor parsing of MI_XX string taking into account
it's 16-based

Alexander Mot (1):
      windows: Define __func__ for vs2015

Aurelien Jarno (1):
      tests/set_option: Avoid use-after-free in case of test failure

Brad Smith (1):
      threads_posix: Use proper getthrid() for thread ID on OpenBSD

Craig Hutchinson (1):
      Fix `exit` order to match reverse of `init`

Dominik Boehi (1):
      descriptor: Add support for BOS platform descriptor parsing

Edgar Fuß (2):
      netbsd: Add comment about udi_speed values matching libusb enum
      netbsd: Map NetBSD's udi_bus/udi_addr to libusb's 1-based API

Francis Hart (1):
      Fix setting log level before libusb_init()

Ihor Dutchak (2):
      Fix possible memory leak of configuration descriptor (Darwin/Windows)
      darwin/windows: Find interface descriptor by bInterfaceNumber

Ingvar Stepanyan (15):
      Add Emscripten backend for WebAssembly + WebUSB support
      examples/hotplugtest: Match any device by default
      tests: Mark callbacks as LIBUSB_CALL
      testlib: Don't count skipped tests as failures
      CI: Run cross-platform tests on all platforms
      CI: Enable Address Sanitizer (ASAN) where supported
      CI: Tell tests that we don't have any devices
      CI: Pass the extra warnings flags to CXXFLAGS too
      Add WebUSB testing via node-usb
      CI: Enable Emscripten build
      tests/stress_mt: Test open/transfer/close on available devices
      webusb: Wasm+WebUSB backend fixes and improvements
      tests/stress_mt: Stop early if any device fails
      tests/set_option: Allow no devices in test_no_discovery
      msvc: Add tests/init_context project to MSVC

Joshua M. Clulow (2):
      sunos: Fix error detection in sunos_submit_transfer()
      sunos: Return error if OS paths hit their limits

Lars Kanis (2):
      core: Don't overwrite the log callback on every global libusb_set_option()
      core: Allow setting global log callback after first libusb_init()

Lonnie Abelbeck (1):
      configure.ac: Link with -latomic only if no atomic builtins

Ludovic Rousseau (6):
      Doxygen: Add references to LIBUSB_ERROR codes
      Doxygen: Improve libusb_wrap_sys_device() documentation
      Add github action build for --enable-debug-log
      Fix build error with --enable-debug-log
      Fix build errors of tests with --enable-debug-log
      Fix github action warnings

Mario Kleiner (1):
      windows: Fix off-by-one error in HID backend for devices without
report IDs

Martin Ling (4):
      docs: Clear endpoint halt issued after cancellation only for macOS < 10.5
      windows: Add GetPipePolicy to struct winusb_interface
      windows: Add option for WinUSB RAW_IO endpoint policy
      Revert "windows: Add option for WinUSB RAW_IO endpoint policy"

Nathan Hjelm (17):
      darwin: add missing locking around cached device list cleanup
      config: allow configure to continue without pkg-config installed
      darwin: Do not clear device data toggle on macOS 10.5 or newer
      Add tags and cscope.out to .gitignore
      core: Add libusb_init_context() setting options at context creation
      Update tests and example to use the new libusb_init_context() function
      libusb_set_options: Adjust semantics of libusb_set_option for log level
      tests: Add unit test for libusb_set_option
      Add support for setting the log callback with
libusb_set_option/libusb_init_context
      darwin: fix potential crash at darwin_exit
      ci: do not hard code test names for CI
      ci: dump test suite output on test failure
      ci: ensure testsuite log is dumped on failure
      darwin: add get_running_version helper
      darwin: add abstraction for IOUSBInterfaceInterface
      darwin: add abstraction for IOUSBDeviceInterface
      darwin: add testing for IOKit version fallbacks

Niklas Gürtler (1):
      Fix #1263 by acquiring the waiters lock while calling transfer
callbacks and swapping the order of operations in sync_transfer_cb

Orhan aib Kavrakoglu (3):
      core: Factor out helper get_endpoint_max_packet_size()
      core: Add helper find_alt_endpoint()
      core: Add libusb_get_max_alt_packet_size()

Pablo Prietz (1):
      core: Remove leftover usbi_mutex_unlock in
libusb_set_interface_alt_setting

Petr Pazourek (1):
      windows: Allow device GUIDs missing terminating characters or separators

Rosen Penev (4):
      windows: Add clock_gettime check
      windows: Mark libusb_set_option as WINAPIV
      windows: Fix build with --disable-log
      windows: Remove __stdcall libusb_set_option from .def file

Ryan Metcalfe (3):
      descriptor: Introduce interface association descriptors (IAD)
      windows: Allow claiming all interfaces for a WINUSBX composite function
      xusb: Print info from IAD descriptors

Sean McBride (18):
      Simplify clock_gettime() conditionalization and fallback on macOS
      examples: Replace most uses of sprintf with safer snprintf
      core: Fix -Wswitch warnings by including all enum values in switch
      darwin: Revert seemingly harmless introduction of temporary variable
      darwin: Avoid error checking regression
      descriptor: Prevent string descriptor buffer overread
      io: Fix incorrect alignment in allocation in libusb_alloc_transfer
      core: Add missing mutex acquisition when manipulating active_contexts_list
      libusb.h: Rename ZERO_SIZED_ARRAY to LIBUSB_FLEXIBLE_ARRAY
      io: Change remove_from_flying_list() to not lock
flying_transfers_lock itself
      Fix docs about backend functions that lock itransfer->lock
      Document backend functions that already lock dev_handle->lock
      Replace all http://libusb.info/ with https
      darwin: locationID is 32-bit, not 64-bit
      Correct some spelling and add codespell config file
      xcode: Move some options from Xcode project to xcconfig file
      xcode: Add files from other backends into the Xcode project
      docs: Prefer use of libusb_init_context() over old libusb_init()

Shawn Hoffman (5):
      msvc: Rework msbuild files
      windows: Whitespace fix
      msvc: Implement LIBUSB_DEPRECATED_FOR
      msvc: Correct usage comments about linking
      windows: Use sdk-defined GUIDs where possible

Simon Chan (1):
      windows: Recognize Samsung composite device driver

SomeAlphabetGuy (1):
      core: Avoid possible data race in log_v()

Sonatique (1):
      msvc: Add configurations with /MT compilation flag

Sylvain (1):
      git ignore "build" folder

Sylvain Fasel (2):
      windows: Define bus numbers without using HCD
      windows: No longer wait for device to get an active configuration

Tormod Volden (52):
      windows: Pass on returned isochronous packet status on libusbK
      core: Remove select case not possibly reached
      windows: Correct function name in comment
      core: Avoid mutex lock while printing error and warning
      windows: Avoid invalid dereference in debug print
      windows: Silence warnings when building without logging
      tests: Add multithreaded stress test for Posix platforms
      CI: Run multithreaded stress test on Linux
      core: Do not warn about new context as implicit default
      Fix most -Wpedantic warnings
      xusb: Add newlines in mass-storage test output
      Bump LIBUSB_API_VERSION to 0x0100010A
      windows: Omit -mwin32 GCC option for MSYS/MinGW
      windows: Only link with --add-stdcall-alias if supported by linker
      xusb: Improve kernel driver probe messages
      xusb: Improve Max LUN retrieval stall handling
      tests/stress_mt: Add Windows threads support
      tests/stress_mt: Also run with device enumeration
      Revert "windows: Fix off-by-one error in HID backend for devices
without report IDs"
      core: Avoid crash due to premature va_end
      core: Fix always-true condition in log callback function setting
      netbsd/openbsd: Drop parentheses around return values
      netbsd/openbsd: Remove extraneous parentheses around ioctl call
      netbsd: Print control transfer request debug values in hex
      netbsd: Add error number to debug output
      Add HACKING file with hints on proper commits
      tests: Remove unused function in init_context.c
      tests: Fix builds with logging disabled
      Revert "core: Remove select case not possibly reached"
      windows: Cover all enumeration passes explicitly in switch statements
      stress_mt: Return error if device count varies
      core: Avoid warning with logging disabled
      windows: Avoid warning with logging disabled
      windows: Include enumeration details in debug output
      CI: Simplify Linux job description
      CI: Add Linux and MSYS build with logging disabled
      tests/umockdev: Avoid unknown warning option on older gcc
      .gitignore: Ignore test binaries and logs
      tests: Use AM_LDFLAGS for -static flag to allow LDFLAGS override
      libusb 1.0.27-rc1
      libusb.h: Avoid UNREFERENCED_PARAMETER macro on GCC/clang
      tests/stress_mt: Ignore some unavailable devices on Windows
      tests/stress_mt: Ignore device descriptor mismatch for Windows HID
      ChangeLog updates
      Change libusb_init_option to fix libusb_set_option() on big-endian
      windows: Downgrade get_guid DeviceInterfaceGUID warning to info
      docs: Add more references in libusb_option section
      libusb 1.0.27-rc2
      configure.ac: Do not build umockdev if --enable-debug-log is used
      examples/hotplugtest: Tone down message about failed open
      configure.ac: Bump libtool library version
      libusb 1.0.27

Xiaofan Chen (2):
      CI: Add build jobs for MSYS clang32/64
      Do not deprecate libusb_set_debug and libusb_init

Zeng Guang (1):
      windows: Add USBD_STATUS_STALL_PID to usbd_status translation

xloem (1):
      linux: Keep the no_device_discovery option per context


_______________________________________________
libusb-devel mailing list
lib...@li...
https://lists.sourceforge.net/lists/listinfo/libusb-devel

Re: [Libusb-win32-devel] libusbdotnet reviewers and contributors welcome

[Xiaofan C. <xia...@gm...>]

Just FYI that PR 193 has been merged.

Best regards,
Xiaofan

On Sun, Apr 9, 2023 at 10:02 PM Xiaofan Chen <xia...@gm...> wrote:

> I am not so sure if there are many libusbdotnet users here. In case you
> are interested, you may want to take a look at the PR here.which
> is one of the main missing features of the master branch (async
> transfer support).
> https://github.com/LibUsbDotNet/LibUsbDotNet/pull/193
>
> There are other missing features like the Device Notification.
> https://github.com/LibUsbDotNet/LibUsbDotNet/issues/32
>
> There are also some issues not yet sorted out, for both the master
> branch (v3) and v2 branch.
> https://github.com/LibUsbDotNet/LibUsbDotNet/issues
>
> --
> Xiaofan
>

Re: [Libusb-win32-devel] Query regarding Libusb dll usage

[Xiaofan C. <xia...@gm...>]

Hi Manish,

You need to follow the license.

libusbdotnet: LGPL v3 license
https://github.com/LibUsbDotNet/LibUsbDotNet/blob/master/LICENSE

libusb-win32 driver: GPL v3 license
https://github.com/mcuee/libusb-win32/blob/master/libusb/COPYING_GPL.txt

libusb-win32 library: LGPL v3 license
https://github.com/mcuee/libusb-win32/blob/master/libusb/COPYING_LGPL.txt

As long as you did not modify any of the source codes, you should be fine. You
can point out the location of the two projects for the source codes or you can
bundle the source codes.

Best regards,
Xiaofan


On Fri, Apr 14, 2023 at 4:09 PM Manish Ram <ram...@gm...> wrote:
>
> Hello Libusb Team,
>
>  Needed information regarding the usage of Libusb in my application.
>
> We are using the below versions:
>
>         LibUsbDotNet dll version: 2.2.29
>
>         USB Driver version: 1.2.6.0
>
> Could you please let us know if there is any restriction on the distribution of these
> libraries along with my application?
>
> Best Regards,
> Manish Ram