On Thursday 25 February 2010, Mariano Alvira wrote:
>
> > By the way ... I kind of suspect this will cause build breakage
> > on systems configured to use FTDI's library, since INTERFACE_A
> > and suchlike are not defined.
>
> I don't think it will break much. If you are configured to use FTD2XX
> it uses a different init function:
But there's no
#ifndef INTERFACE_B
#define INTERFACE_B ...
...
#endif
before the layout table, which will reference such symbols outside
of the init function...
> And to me it looks like that driver interprets the device string to
> figure out what to open:
Hmm ... all the more reason to have a clean distinction between
the signal mappping aspect of the layout (in C functions) and the
names in the layout table ...
Seems like you're implying that when using FTDI's library on MS-Windows,
there has always been a mechanism for that: just because the device IDs
passed into the library actually specify USB interfaces (channels) instead
of USB devices (which expose multiple interfaces).
- Dave
_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development
