Karsten Schulz | 23 Nov 21:35 2015
Picon

WinUSB LibUSB

Hello togheter,
 
we have an Microcontroller on the USB Port, and write/read em succseed with LibUSB .
Now we try to read/write with WinUSB.
 
An Problem is the content of   :  WINUSB_SETUP_PACKET
 
LibUsb use : usb_control_msg(usb_dev_handle *dev, int requesttype, int request,int value, int index, char *bytes, int size,int timeout)
to send/recieve data , in this case WinUSB need to form out an SetupPacket:

WINUSB_SETUP_PACKET setup;
SetupPacket.RequestType = (1<<5) | 0x80; //try use type from LibUSB
SetupPacket.Request = 0;
SetupPacket.Value = 0;
SetupPacket.Index = 0;
SetupPacket.Length = sizeof(UCHAR);
WinUsb_ControlTransfer(WinusbHandle, SetupPacket, &bars, sizeof(UCHAR), &cbSent, 0);
 
Command ends Succsesfull! But the part got no data.
 
Hav any one Information to form out the setup packed correctly so we can use alternat WinUSB ?
 
We use it for Digispark Atiny85 Microcontrollerboard with arduino : http://digistump.com/wiki/digispark/tutorials/connecting
 
Thanks much for any Help
Karsten from Berlin
 
 
 
 
 
------------------------------------------------------------------------------
Go from Idea to Many App Stores Faster with Intel(R) XDK
Give your users amazing mobile app experiences with Intel(R) XDK.
Use one codebase in this all-in-one HTML5 development environment.
Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs.
http://pubads.g.doubleclick.net/gampad/clk?id=254741551&iu=/4140
_______________________________________________
Libusb-win32-devel mailing list
Libusb-win32-devel <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
Xiaofan Chen | 23 Nov 14:28 2015
Picon

libusb-win32, libusbK and libusbdotnet under Windows 10

I just got time to carry out some simple tests under Windows 10 Professional
(upgraded from Windows 7 Ultimate) on a 5 year old PC (only 2GB RAM
with Pentium Dual Core E5500 Intel G41 chipset).

It seems to me that libusb-win32, libusbK and libusbdotnet all work fine
under Windows 10.

I use the libusbK inf-wizard GUI and Zadig for the installation of the drivers
(libusb0.sys, libusbK.sys and WinUSB).

I'd like to get your feedback on Windows 10. It seems to be more stringent
on the digital signature but Zadig and libusbK inf-wizard's self-signing method
seem to work fine.

--

-- 
Xiaofan

------------------------------------------------------------------------------
Go from Idea to Many App Stores Faster with Intel(R) XDK
Give your users amazing mobile app experiences with Intel(R) XDK.
Use one codebase in this all-in-one HTML5 development environment.
Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs.
http://pubads.g.doubleclick.net/gampad/clk?id=254741551&iu=/4140
mabdallah | 22 Oct 14:18 2015

Win7 speed issue

I'm trying to use libUSb-Win32 with USB-to-TTl serial converter to send raw
data just to test making usb driver on windows, the problem is that data
rate monitored on the bus using USBLyzer is 6.6msec per bit ! how can i
increase the speed to maximum available speed ? 

N.B. Data is send correctly with no problem in data itself, the problem is
with speed. 

Here is my code: 
=========== 

    usb_init(); 
    usb_set_debug(255) ; 
    usb_find_busses(); 
    num = usb_find_devices() ; 

    printf("Devices: %d\n", num) ; 

    busses = usb_get_busses(); 

        for (bus = busses; bus; bus = bus->next) { 
                struct usb_device *dev; 

                for (dev = bus->devices; dev; dev = dev->next) { 
                        if ((dev->descriptor.idVendor == 0x067B) &&
(dev->descriptor.idProduct == 0x2303)) { 
                                mydev = usb_open(dev) ; 

                                if (mydev == NULL) 
                                { 
                                        printf("Error: usb_open\n") ; 
                                } 
                                else 
                                { 
                                        printf("Device opened\n") ; 

                                        mreturn =
usb_set_configuration(mydev, 1) ; 

                                        if (mreturn != 0) 
                                        { 
                                                printf("Error:
usb_set_configuration\n") ; 
                                        } 
                                        else 
                                        { 
                                                printf("Config. set\n") ; 

                                                mreturn =
usb_claim_interface(mydev, 0) ; 

                                                if (mreturn != 0) 
                                                { 
                                                        printf("Error:
usb_claim_interface\n") ; 
                                                } 
                                                else 
                                                { 
                                                        printf("Interface
claimed\n") ; 

                                                        mreturn =
usb_bulk_write(mydev, 2, data, 1000, 0) ; 

                                                        if (mreturn < 0) 
                                                        { 

printf("Error: usb_bulk_write\n") ; 
                                                        } 
                                                        else 
                                                        { 
                                                                printf("Data
sent\n") ; 
                                                        } 

                                                       
usb_release_interface(mydev, 0) ; 
                                                } 
                                        } 
                                } 
                        } 
                } 
        } 

and here is USB info by testlibusb-win: 
========================= 

bus/device  idVendor/idProduct 
bus-0/\\.\libusb0-0001--0x067b-0x2303     067B/2303 
- Manufacturer : Prolific Technology Inc. 
- Product      : USB-Serial Controller 
bLength:             18 
bDescriptorType:     01h 
bcdUSB:              0110h 
bDeviceClass:        00h 
bDeviceSubClass:     00h 
bDeviceProtocol:     00h 
bMaxPacketSize0:     40h 
idVendor:            067Bh 
idProduct:           2303h 
bcdDevice:           0300h 
iManufacturer:       1 
iProduct:            2 
iSerialNumber:       0 
bNumConfigurations:  1 
  wTotalLength:         39 
  bNumInterfaces:       1 
  bConfigurationValue:  1 
  iConfiguration:       0 
  bmAttributes:         a0h 
  MaxPower:             50 
    bInterfaceNumber:   0 
    bAlternateSetting:  0 
    bNumEndpoints:      3 
    bInterfaceClass:    255 
    bInterfaceSubClass: 0 
    bInterfaceProtocol: 0 
    iInterface:         0 
      bEndpointAddress: 81h 
      bmAttributes:     03h 
      wMaxPacketSize:   10 
      bInterval:        1 
      bRefresh:         0 
      bSynchAddress:    0 
      bEndpointAddress: 02h 
      bmAttributes:     02h 
      wMaxPacketSize:   64 
      bInterval:        0 
      bRefresh:         0 
      bSynchAddress:    0 
      bEndpointAddress: 83h 
      bmAttributes:     02h 
      wMaxPacketSize:   64 
      bInterval:        0 
      bRefresh:         0 
      bSynchAddress:    0 

Thanks

--
View this message in context: http://libusb.6.n5.nabble.com/Win7-speed-issue-tp5715261.html
Sent from the LibUSB Dev - Win32 mailing list archive at Nabble.com.

------------------------------------------------------------------------------
diverger | 21 Oct 17:32 2015
Picon

回复: Re: Infowizard don't work on Window 10

Sorry for the long email, I'm not very familiar with my Android email client yet.

The info wizard indeed comes from the lib usbk's installer, which I download from sourceforge. In win7, it works well, but won't on win10.

I don't know if we mean the same "info wizard", but I mean the one comes with the libusbk installer, can you give me some suggestions, thanks.



发送自我的三星设备
------------------------------------------------------------------------------
_______________________________________________
Libusb-win32-devel mailing list
Libusb-win32-devel <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
Zaslavsky Evelina | 20 Oct 10:12 2015
Picon

ReadBufferSize cause error windows8

Hi All,  I'm really sorry for disturbing you. I have a problem with my LibUsbDotNet project and asking for your help.

In windows 7 the project works correctly, but when I migrate the project to windows 8 i get the follow error:
No data to read IOTimeOut.
(I checked the devise side, cmdWrite reseaved correctly and device send the answer)

This is the function:
   private void cmdRead_Click(object sender, EventArgs e)
        {
            cmdRead.Enabled = false;
            byte[] readBuffer = new byte[1024];
            int uiTransmitted;
            ErrorCode eReturn;
            
                if ((eReturn = mEpReader.Read(readBuffer, 1000, out uiTransmitted)) == ErrorCode.None)
                {
                    tsStatus.Text = uiTransmitted + " bytes read.";
                    showBytes(readBuffer, uiTransmitted);
                }
                else
                    tsStatus.Text = "No data to read! " + eReturn;
}
            cmdRead.Enabled = true;
        }

After this readBuffer contains the readed correct answer from device, but  eReturn = IOTimeOut

When I debugged it i sow that
the follow function returns false:

 Kernel32.DeviceIoControl(endPointBase.Device.Handle,
                                            cltCode,
                                            req,
                                            LibUsbRequest.Size,
                                            buffer,
                                            bufferLength,
                                            out lengthTransferred,
                                            pOverlapped);  

This error happens if the  readBuffe.size more then 64.

 mEpReader.ReadBufferSize = 1024; - doesn't help

This code will run perfect:

  private void cmdRead_Click(object sender, EventArgs e)
        {
            cmdRead.Enabled = false;
            byte[] readBuffer = new byte[64];;
            int uiTransmitted;
            ErrorCode eReturn;
            
                if ((eReturn = mEpReader.Read(readBuffer, 1000, out uiTransmitted)) == ErrorCode.None)
                {
                    tsStatus.Text = uiTransmitted + " bytes read.";
                    showBytes(readBuffer, uiTransmitted);
                }
                else
                    tsStatus.Text = "No data to read! " + eReturn;
}
            cmdRead.Enabled = true;
        }

I already reinstalled the LibUSB0 drivers.

Thank you for your attention.

Have a nice day.
------------------------------------------------------------------------------
_______________________________________________
Libusb-win32-devel mailing list
Libusb-win32-devel <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
ZhangHua | 16 Oct 04:25 2015
Picon

Maximum transfer size when call bulk transfer API in libusb

Hi,

I'm using https://github.com/libusb and based on libusbK.sys. Per MS's link: https://msdn.microsoft.com/en-us/library/windows/hardware/ff538112%28v=vs.85%29.aspx?f=255&MSPPError=-2147217396. It has hard-coded limit in there USB driver stack. Then what libusbK.sys and libusb done for this? If I need split my large chunks of data to smaller ones then call "libusb_bulk_transfer"? Or MS or libusb or libusbK have done the data *scaling* at lower layer for user? 
------------------------------------------------------------------------------
_______________________________________________
Libusb-win32-devel mailing list
Libusb-win32-devel <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
Kněžík Jan | 6 Oct 11:26 2015

Connecting to input endpoint 0x84

Hello,

I am beginner on USB and I want to use LibUsbDotNet to connect GSM modem and send an AT command. LibUsbDotNet offers only endpoints number 1 to 15 (WriteEndpointID) and I need 0x84. Am I missing something? Thank you very much.


Best Regards,

Jan Knezik

------------------------------------------------------------------------------
_______________________________________________
Libusb-win32-devel mailing list
Libusb-win32-devel <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
Dave | 6 Oct 02:15 2015
Picon

Re: Libusbk for Window 10 signing

Many thanks for your comments, Xiaofan and Borge.

I'll look at MS sample drivers to see if I want to tackle the task of 
adapting one of them to this purpose. I'm just a hobbyist, and I put 
together my own XMOS-based USB-I2S device only because of my frustration 
with the miniDSP USBStreamer. It probably would take a lot of time to finish 
a kernel mode driver, so I'm only looking at the possibility. It might be 
fun, though. (I made a good living coding C++ for many years, but my coding 
chops aren't what they were 10 years ago when I retired.)

Borge, I tried out the ASIO driver you use with another XMOS-based device 
some time ago, and it worked fine. We communicated briefly on diyaudio back 
then. The idea of taking the code already written for that driver and 
packaging as a kernel mode driver is intriguing.

Best regards,

Dave

-----Original Message----- 
From: libusb-win32-devel-request <at> lists.sourceforge.net
Sent: Monday, October 05, 2015 19:01
To: libusb-win32-devel <at> lists.sourceforge.net
Subject: Libusb-win32-devel Digest, Vol 110, Issue 1

Send Libusb-win32-devel mailing list submissions to
libusb-win32-devel <at> lists.sourceforge.net

To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
or, via email, send a message with subject or body 'help' to
libusb-win32-devel-request <at> lists.sourceforge.net

You can reach the person managing the list at
libusb-win32-devel-owner <at> lists.sourceforge.net

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Libusb-win32-devel digest..."

Today's Topics:

   1. Re: Libusbk for Window 10 signing (Dave)
   2. Re: Libusbk for Window 10 signing (Xiaofan Chen)
   3. Re: Libusbk for Window 10 signing (B?rge Strand-Bergesen)
   4. Re: Libusbk for Window 10 signing (Xiaofan Chen)
   5. Re: Libusbk for Window 10 signing (B?rge Strand-Bergesen)

----------------------------------------------------------------------

Message: 1
Date: Mon, 5 Oct 2015 07:52:28 +0700
From: "Dave" <dhalbakken.groups <at> gmail.com>
Subject: Re: [Libusb-win32-devel] Libusbk for Window 10 signing
To: <libusb-win32-devel <at> lists.sourceforge.net>
Message-ID: <4178359F7E8144F7BDCE761EC9CD4D73 <at> DaveWin7>
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
reply-type=original

Travis wrote regarding WinUSB:

    You can even add things to you USB descriptor which identifies it as a
"winusb" device and eliminate the need for a driver installer all-together.

I recently experimented with this on an XMOS-based implementation if a
USB-I2S adapter supporting USB Audio 2 and isosynchronous transfers. I hoped
to replace the Thesycon drivers normally used with XMOS adapters with WinUSB
on Windows 10. (Microsoft claims to support isosynchronous transfers under
Windows 8.1 and Windows 10 using WinUSB.) I added a Windows Compatible ID to
the device's firmware and successfully got the adapter to be recognized as a
WinUSB device when it was plugged in, but the OS did not bother to expose
any of the audio interfaces. It looks as if one still must have a layer
above WinUSB to support USB Audio 2.

I wonder if anyone can point me to a source of information on using WinUSB
for audio 2. I have not been able to find anything on Microsoft's developer
sites. It seems Microsoft is still lagging behind Linux and OS-X in its
audio support.

Best regards,

Dave

From: Travis <libusbdotnet <at> gm...> - 2015-08-10 14:58:09

Greetings,

LibusbK is already signed with a DigiCert High Assurance EV Root CA.

At some point, I would like to add the WinUSB ISO support to the libusbK
library and let it become our "primary" driver.  There is little
advantage to using libusbK.sys compares to the newer WinUsb.sys with ISO
support.

That said, nothing is going to stop working.  Even if we support WinUSB
ISO, we will not throw libusbK.sys away.  I would expect most all users
to WANT to transition to the winusb driver.  There are some big
advantage because it is essentially a built-in windows driver for custom
usb devices.  You can even add things to you USB descriptor which
identifies it as a "winusb" device and eliminate the need for a driver
installer all-together.

Regards,
Travis

------------------------------

Message: 2
Date: Mon, 5 Oct 2015 10:16:09 +0800
From: Xiaofan Chen <xiaofanc <at> gmail.com>
Subject: Re: [Libusb-win32-devel] Libusbk for Window 10 signing
To: libusb-win32-devel <at> lists.sourceforge.net
Message-ID:
<CAGjSPUB2GYJywyfGA5bO8B20EYdm0n8aSVvH6Zzf3NEGfMB5nA <at> mail.gmail.com>
Content-Type: text/plain; charset=UTF-8

On Mon, Oct 5, 2015 at 8:52 AM, Dave <dhalbakken.groups <at> gmail.com> wrote:
> Travis wrote regarding WinUSB:
>
>     You can even add things to you USB descriptor which identifies it as a
> "winusb" device and eliminate the need for a driver installer 
> all-together.
>
> I recently experimented with this on an XMOS-based implementation if a
> USB-I2S adapter supporting USB Audio 2 and isosynchronous transfers. I 
> hoped
> to replace the Thesycon drivers normally used with XMOS adapters with 
> WinUSB
> on Windows 10. (Microsoft claims to support isosynchronous transfers under
> Windows 8.1 and Windows 10 using WinUSB.) I added a Windows Compatible ID 
> to
> the device's firmware and successfully got the adapter to be recognized as 
> a
> WinUSB device when it was plugged in, but the OS did not bother to expose
> any of the audio interfaces. It looks as if one still must have a layer
> above WinUSB to support USB Audio 2.
>
> I wonder if anyone can point me to a source of information on using WinUSB
> for audio 2. I have not been able to find anything on Microsoft's 
> developer
> sites. It seems Microsoft is still lagging behind Linux and OS-X in its
> audio support.

No WinUSB is for generic USB device and not USB Audio Device. Even
though Microsoft added isoc transfer support in WinUSB, that does not
mean you can have the USB Audio support using WinUSB.

Basically the answer seems to be that Microsoft does not support
USB Audio Class 2.0 natively since  music production and recording studios
are a niche market. That is still the case under Windows 10.

-- 
Xiaofan

------------------------------

Message: 3
Date: Mon, 5 Oct 2015 06:37:35 +0200
From: B?rge Strand-Bergesen <borge.strand <at> gmail.com>
Subject: Re: [Libusb-win32-devel] Libusbk for Window 10 signing
To: "libusb-win32-devel <at> lists.sourceforge.net"
<libusb-win32-devel <at> lists.sourceforge.net>
Message-ID:
<CAE9Na6G8HLfZGJXV2rXMEcg+Ygr9wJmKMuceNkXkgePppjLWVg <at> mail.gmail.com>
Content-Type: text/plain; charset=UTF-8

Hi Dave,

while I can't point you to a source I can at least tell you how I
share your pain, and share my own insight.

The Audio Widget project has an open source ASIO driver based on
libusbK. It works like a charm. Let me know and I'll point you to this
User Mode code. MS offer of closed source audio drivers example code.
It will tell the OS "hey, I'm a sound card" and accept audio. None of
them send the audio out over UAC2. Because of licensing, the MS
example code can't yet be taken practically into the open and expanded
into a UAC2 driver.

In order to get anywhere I see two options:
1) This is already done by a few entities: Make a virtual sound card,
push the audio back into User Mode, run a service to forward it to
ASIO drivers.
2) This is considered very hard and closed source: Write kernel-mode
code which combines low-level USB access (in your case WinUSB), MS
audio driver example code and UAC2 flowcharts (inspired by the Audio
Widget ASIO driver).

In the ASIO driver there is an .h file from Steinberg which isn't
distributed. Instead, there is a place holder and instructions on how
to obtain the file. The same could maybe be done with the MS examples
needed, assuming they wouldn't need much rewriting, or could (legally)
be patched.

Don't let the cost of signing scare you off. As long as there are test
certificates available for evaluation, I'm sure production
certificates can be crowd sourced. You're far from the only guy to
bring up this problem. Unfortunately, talking to MS about it is about
as productive as talking to a tree.

All the best,
B?rge

On Mon, Oct 5, 2015 at 2:52 AM, Dave <dhalbakken.groups <at> gmail.com> wrote:
> Travis wrote regarding WinUSB:
>
>     You can even add things to you USB descriptor which identifies it as a
> "winusb" device and eliminate the need for a driver installer 
> all-together.
>
> I recently experimented with this on an XMOS-based implementation if a
> USB-I2S adapter supporting USB Audio 2 and isosynchronous transfers. I 
> hoped
> to replace the Thesycon drivers normally used with XMOS adapters with 
> WinUSB
> on Windows 10. (Microsoft claims to support isosynchronous transfers under
> Windows 8.1 and Windows 10 using WinUSB.) I added a Windows Compatible ID 
> to
> the device's firmware and successfully got the adapter to be recognized as 
> a
> WinUSB device when it was plugged in, but the OS did not bother to expose
> any of the audio interfaces. It looks as if one still must have a layer
> above WinUSB to support USB Audio 2.
>
> I wonder if anyone can point me to a source of information on using WinUSB
> for audio 2. I have not been able to find anything on Microsoft's 
> developer
> sites. It seems Microsoft is still lagging behind Linux and OS-X in its
> audio support.
>
> Best regards,
>
> Dave
>
> From: Travis <libusbdotnet <at> gm...> - 2015-08-10 14:58:09
>
> Greetings,
>
> LibusbK is already signed with a DigiCert High Assurance EV Root CA.
>
> At some point, I would like to add the WinUSB ISO support to the libusbK
> library and let it become our "primary" driver.  There is little
> advantage to using libusbK.sys compares to the newer WinUsb.sys with ISO
> support.
>
> That said, nothing is going to stop working.  Even if we support WinUSB
> ISO, we will not throw libusbK.sys away.  I would expect most all users
> to WANT to transition to the winusb driver.  There are some big
> advantage because it is essentially a built-in windows driver for custom
> usb devices.  You can even add things to you USB descriptor which
> identifies it as a "winusb" device and eliminate the need for a driver
> installer all-together.
>
> Regards,
> Travis
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Libusb-win32-devel mailing list
> Libusb-win32-devel <at> lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel

------------------------------

Message: 4
Date: Mon, 5 Oct 2015 17:58:59 +0800
From: Xiaofan Chen <xiaofanc <at> gmail.com>
Subject: Re: [Libusb-win32-devel] Libusbk for Window 10 signing
To: libusb-win32-devel <at> lists.sourceforge.net
Message-ID:
<CAGjSPUAcMiY3QHU3AqqTTHsepFDgybJBo9RonGL=RNZCcjGDbw <at> mail.gmail.com>
Content-Type: text/plain; charset=UTF-8

On Mon, Oct 5, 2015 at 12:37 PM, B?rge Strand-Bergesen
<borge.strand <at> gmail.com> wrote:
>
> Don't let the cost of signing scare you off. As long as there are test
> certificates available for evaluation, I'm sure production
> certificates can be crowd sourced. You're far from the only guy to
> bring up this problem. Unfortunately, talking to MS about it is about
> as productive as talking to a tree.

On the other hand, certificate to sign the driver is just the smallest
part of the efforts (eg: libusb-win32 project got the money using the
donation from the mailing list members). Getting somebody who is familiar
with the kernel mode knowledge to write the driver is the difficult part.

In reality, I have not seen many open source Windows kernel driver
projects since that is really a niche. The only exception seems to be
Redhat which has come out with some open source driver to support
their activities. But again Redhat is a big company.

Maybe things will change now that Microsoft posts the WDF (both KMDF
and UMDF) source codes in github under a very liberal licence (MIT license).
URL: https://github.com/Microsoft/Windows-driver-frameworks

So I think it is now not fair to complain about Microsoft not being
helpful. Rather prepare to climb the steep learning curve
and develop the driver yourself or prepare to pay for the driver
development and maintenance.

-- 
Xiaofan

------------------------------

Message: 5
Date: Mon, 5 Oct 2015 12:09:29 +0200
From: B?rge Strand-Bergesen <borge.strand <at> gmail.com>
Subject: Re: [Libusb-win32-devel] Libusbk for Window 10 signing
To: "libusb-win32-devel <at> lists.sourceforge.net"
<libusb-win32-devel <at> lists.sourceforge.net>
Message-ID:
<CAE9Na6FZqOF_s_8JOXY779S+QnYP+-zEy4M3mscnHdGyFd5qUA <at> mail.gmail.com>
Content-Type: text/plain; charset=UTF-8

Xiofan,

the MIT licence part was new to me! Now there is at last some light in
the tunnel! This means it is at last feasible to put people together
and divide driver jobs into smaller tasks.

Personally, I'm an embedded hardware guy. For audio driver development
work I will volunteer UAC2 hardware with open source firmware and
debug (GPIO, RS232, JTAG) options. That should make it much easier to
see what's going on on the Device side of any such driver development.

B?rge

On Mon, Oct 5, 2015 at 11:58 AM, Xiaofan Chen <xiaofanc <at> gmail.com> wrote:
> On Mon, Oct 5, 2015 at 12:37 PM, B?rge Strand-Bergesen
> <borge.strand <at> gmail.com> wrote:
>>
>> Don't let the cost of signing scare you off. As long as there are test
>> certificates available for evaluation, I'm sure production
>> certificates can be crowd sourced. You're far from the only guy to
>> bring up this problem. Unfortunately, talking to MS about it is about
>> as productive as talking to a tree.
>
> On the other hand, certificate to sign the driver is just the smallest
> part of the efforts (eg: libusb-win32 project got the money using the
> donation from the mailing list members). Getting somebody who is familiar
> with the kernel mode knowledge to write the driver is the difficult part.
>
> In reality, I have not seen many open source Windows kernel driver
> projects since that is really a niche. The only exception seems to be
> Redhat which has come out with some open source driver to support
> their activities. But again Redhat is a big company.
>
> Maybe things will change now that Microsoft posts the WDF (both KMDF
> and UMDF) source codes in github under a very liberal licence (MIT 
> license).
> URL: https://github.com/Microsoft/Windows-driver-frameworks
>
> So I think it is now not fair to complain about Microsoft not being
> helpful. Rather prepare to climb the steep learning curve
> and develop the driver yourself or prepare to pay for the driver
> development and maintenance.
>
>
>
> --
> Xiaofan
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Libusb-win32-devel mailing list
> Libusb-win32-devel <at> lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel

------------------------------

------------------------------------------------------------------------------

------------------------------

_______________________________________________
Libusb-win32-devel mailing list
Libusb-win32-devel <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel

End of Libusb-win32-devel Digest, Vol 110, Issue 1
************************************************** 

------------------------------------------------------------------------------
Dave | 5 Oct 02:52 2015
Picon

Re: Libusbk for Window 10 signing

Travis wrote regarding WinUSB:

    You can even add things to you USB descriptor which identifies it as a 
"winusb" device and eliminate the need for a driver installer all-together.

I recently experimented with this on an XMOS-based implementation if a 
USB-I2S adapter supporting USB Audio 2 and isosynchronous transfers. I hoped 
to replace the Thesycon drivers normally used with XMOS adapters with WinUSB 
on Windows 10. (Microsoft claims to support isosynchronous transfers under 
Windows 8.1 and Windows 10 using WinUSB.) I added a Windows Compatible ID to 
the device's firmware and successfully got the adapter to be recognized as a 
WinUSB device when it was plugged in, but the OS did not bother to expose 
any of the audio interfaces. It looks as if one still must have a layer 
above WinUSB to support USB Audio 2.

I wonder if anyone can point me to a source of information on using WinUSB 
for audio 2. I have not been able to find anything on Microsoft's developer 
sites. It seems Microsoft is still lagging behind Linux and OS-X in its 
audio support.

Best regards,

Dave

From: Travis <libusbdotnet <at> gm...> - 2015-08-10 14:58:09

Greetings,

LibusbK is already signed with a DigiCert High Assurance EV Root CA.

At some point, I would like to add the WinUSB ISO support to the libusbK
library and let it become our "primary" driver.  There is little
advantage to using libusbK.sys compares to the newer WinUsb.sys with ISO
support.

That said, nothing is going to stop working.  Even if we support WinUSB
ISO, we will not throw libusbK.sys away.  I would expect most all users
to WANT to transition to the winusb driver.  There are some big
advantage because it is essentially a built-in windows driver for custom
usb devices.  You can even add things to you USB descriptor which
identifies it as a "winusb" device and eliminate the need for a driver
installer all-together.

Regards,
Travis

------------------------------------------------------------------------------
Swapnil Kulkarni | 4 Sep 13:35 2015
Picon

How to use libusb for CDC devices

Hello,

I am new to libusb and not even very much experienced with USB.
I have a written a firmware for LPC1768 to use it as USB CDC device.
It is getting detected as COM port when I use the driver provided by NXP.
But the problem is when I toggle RTS from any terminal software, host is not generating any request to device. Request is generating only for DTR.

So, I thought to use libusb. I used the inf generator.
When I installed the driver, it is showing as libusb-win32 device.
Can someone tell me how can I configure it as COM port. I want to use it throught terminal software.

Also, will libusb solve my problem with RTS toggling?


Regards,
Swapnil
------------------------------------------------------------------------------
_______________________________________________
Libusb-win32-devel mailing list
Libusb-win32-devel <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
张华 | 19 Aug 05:43 2015
Picon

How to uninstall the libusbk driver using an unistaller

Hi,

I've created my driver installer using libusbK-inf-wizard. So I can invoke the generated "InstallDriver.exe" from my application installer to install my drivers. But how to uninstall the drivers using my application installer? Can "InstallDriver.exe" accept some switch like dpinst.exe, such as '/u' to uninstall the installed drivers?

BTW, it seems Win10 need new signature mechanism. I wonder if libusbk and the generated driver installer can work well on Win10?

Thanks.
------------------------------------------------------------------------------
_______________________________________________
Libusb-win32-devel mailing list
Libusb-win32-devel <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel

Gmane