On Mon, Jun 15, 2009 at 6:41 PM, Xiaofan Chen <xiaof...@gmail.com> wrote:
> On Tue, Jun 16, 2009 at 9:27 AM, Xiaofan Chen<xiaof...@gmail.com> wrote: > > On Tue, Jun 16, 2009 at 8:39 AM, David Brownell<davi...@pacbell.net> > wrote: > >> On Monday 15 June 2009, Xiaofan Chen wrote: > >>> As I read, if libusb-win32's WinUSB backend is working, then you can > >>> use WinUSB as the driver and install it under Vista 64. There will be > >>> a warning but you can install it even if the VID/PID combination has > >>> not go through the WHQL process. > >> > >> Should we include any special advice for Window users? > >> > >> Like, "get the latest from SVN"? > >> > >> I'd think "test thoroughly on the platforms you support" > >> goes without saying, and should shake loose Win64 issues. > > > > The problem is that libusb-win32 SVN's WinUSB backend is not > > working right now (nor is the HID backend). And I do not know when > > it will be working. Take note that libusb-win32 does work on XP 64, > > but not Vista 64. So Win64 issue is actually Vista 64 issue. > > > > So the only solution for Vista 64 user is to use D2XX DLL and > > use private build. > > Or some of the JTAG hardware vendors can sponsor the fees to > get the libusb-win32 device driver digitally signed by a approved > Certification Authority like Verisign. ;-) > > The fee is said to be only US$400. > http://www.cygnal.org/ubb/Forum9/HTML/001764.html > > Last time we had a discussion on this issue here. That > was back in 2007. Now Vista 64 is getting really popular. > http://www.nabble.com/WinUSB-td13706403.html > > US$400 is not a big amount for the hardware vendors, right? ;-) > > Once the core driver is signed, users can use libusb-win32 > already. Hardware vendors can choose to go for WHQL > as well which costs about US$1000. Has anyone actually run the libusb-win32 driver through the WHQL tests? IME, it takes a machine half a day per OS variant to run them on a driver that essentially does nothing as far as the tests are concerned. The money you pay MS is insignificant compared to the development costs of actually running the tests... Orin.
_______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
