Infowizard don't work on Window 10
<[email protected]> Tue, 20 Oct 2015 11:07:43 +0000
| Newsgroups | gmane.comp.lib.libusb.devel.windows |
|---|---|
| Message-ID | <[email protected]> |
I installed the infowizard on windows 10, and installed wdk7.1, but the infowizard can't detect it, all driver versions are 0. Does it mean it cannot work on win 10. 通过 Android 版 Outlook 发送 On Mon, Oct 5, 2015 at 5:16 PM -0700, "Dave" <[email protected]> wrote: 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: [email protected] Sent: Monday, October 05, 2015 19:01 To: [email protected] Subject: Libusb-win32-devel Digest, Vol 110, Issue 1 Send Libusb-win32-devel mailing list submissions to [email protected] 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 [email protected] You can reach the person managing the list at [email protected] 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" <[email protected]> Subject: Re: [Libusb-win32-devel] Libusbk for Window 10 signing To: <[email protected]> Message-ID: <4178359F7E8144F7BDCE761EC9CD4D73@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@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 <[email protected]> Subject: Re: [Libusb-win32-devel] Libusbk for Window 10 signing To: [email protected] Message-ID: <CAGjSPUB2GYJywyfGA5bO8B20EYdm0n8aSVvH6Zzf3NEGfMB5nA@mail.gmail.com> Content-Type: text/plain; charset=UTF-8 On Mon, Oct 5, 2015 at 8:52 AM, Dave <[email protected]> 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 <[email protected]> Subject: Re: [Libusb-win32-devel] Libusbk for Window 10 signing To: "[email protected]" <[email protected]> Message-ID: <CAE9Na6G8HLfZGJXV2rXMEcg+Ygr9wJmKMuceNkXkgePppjLWVg@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 <[email protected]> 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@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 > [email protected] > https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel ------------------------------ Message: 4 Date: Mon, 5 Oct 2015 17:58:59 +0800 From: Xiaofan Chen <[email protected]> Subject: Re: [Libusb-win32-devel] Libusbk for Window 10 signing To: [email protected] Message-ID: <CAGjSPUAcMiY3QHU3AqqTTHsepFDgybJBo9RonGL=RNZCcjGDbw@mail.gmail.com> Content-Type: text/plain; charset=UTF-8 On Mon, Oct 5, 2015 at 12:37 PM, B?rge Strand-Bergesen <[email protected]> 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 <[email protected]> Subject: Re: [Libusb-win32-devel] Libusbk for Window 10 signing To: "[email protected]" <[email protected]> Message-ID: <CAE9Na6FZqOF_s_8JOXY779S+QnYP+-zEy4M3mscnHdGyFd5qUA@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 <[email protected]> wrote: > On Mon, Oct 5, 2015 at 12:37 PM, B?rge Strand-Bergesen > <[email protected]> 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 > [email protected] > https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel ------------------------------ ------------------------------------------------------------------------------ ------------------------------ _______________________________________________ Libusb-win32-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel End of Libusb-win32-devel Digest, Vol 110, Issue 1 ************************************************** ------------------------------------------------------------------------------ _______________________________________________ Libusb-win32-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel ------------------------------------------------------------------------------ _______________________________________________ Libusb-win32-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel