On Fri, Jul 3, 2009 at 10:45 AM, Zach Welch<z...@superlucidity.net> wrote: > On Thu, 2009-07-02 at 22:18 -0400, Duane Ellis wrote: >> David Brownell wrote: >> >>> I think this universal inf file >> >>> >> > >> > I would have thought it should be one with a LOT more IDs... >> > >> > That one omits the Olimex dongles, Sheevaplug, Signalyzer, >> > Flyswatter, the Luminary stuff ... and about a dozen more. >> > >> > >> That is *exactly* why I suggested that if some could create a *TEMPLATE* >> *INF* file - any of us 'script-guys' can easily create a script that can >> easily generate, and easily update the 'universal inf file' > > Very wise advice. This is definitely the way to go, if possible; I did > not look carefully enough at the patch to know one way or the other. >
If you could run inf-wizard of libusb-win32, you will understand better the process of generating the INF file for libusb-win32. But I understand that you may not run Windows at all. The INF Wizard from libusb-win32 is already using kind of a template file. http://libusb-win32.svn.sourceforge.net/viewvc/libusb-win32/trunk/libusb/src/inf_wizard.c?view=markup If you run INF wizard, it takes four parameters to generate the INF file. 1. Vendor ID 2. Product ID 3. Manufacturer name 4. Device name In fact, it automatically detect the 4 parameters and give you the freedom to change them. The default INF file generated for FTDI device may not be so good (USB composite device). Therefore Freddie has already put the correct way to do it (use the individual interface). I kind of agree with Freddie that "I don't see any point in writing a script which parses some kind of table to do such simple task. Adding a new interface is just a matter of entering a few (2-4) lines to the inf file". -- Xiaofan http://mcuee.blogspot.com _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
