On Sun, Jun 14, 2009 at 11:05 PM, Xiaofan Chen <xiaof...@gmail.com> wrote:
> On Sun, Jun 14, 2009 at 12:59 PM, Orin Eman<orin.e...@gmail.com> wrote: > > FWIW, to load on 64bit Windows versions, a driver _does not_ need to go > > through the WHQL process. It does however, need to be signed by someone > the > > OS trusts* and you _will_ get the message asking whether you trust the > > manufacturer when you install it. > > You are right. Somebody needs to contribute the Verisign (or similar > Certification > Authority) key to sign a 64 bit device driver in order to get libusb-win32 > device driver to work under Vista 64 without user side hacking. > http://osdir.com/ml/lib.libusb.devel.windows/2007-08/msg00053.html > > On the other hand, libusb-win32 1.0 may be able to solve the issue > by using WinUSB as the backend. The other backend is HID. The > problem is that libusb-win32 1.0 SVN is not working and has not > been updated for quite a while. The last check-in was 22 months ago. > http://libusb-win32.svn.sourceforge.net/viewvc/libusb-win32/trunk/ > Unfortunately, you need an inf file to associate the winusb driver with your device's vid/pid and that too needs signing. In theory, there is a special WHQL submission for this, "Driver Update Acceptable" where you don't have to run through the full tests... but that's not relevant here since no-one is going to pay for it. The company I work for had to do a WHQL of submission for a USB device that is supported in the box on Vista just because our device had a different vid/pid. For a non-WHQL driver, I'll have to check if a self-signed certificate installed in both the trusted root and trusted publisher physical stores works without setting "Test Sign" mode... I don't recall if it did since I switched to using a real SPC in the driver work I've been doing. Orin.
_______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
