On Sun, Mar 30, 2014 at 6:41 PM, Bjørn Forsman <[email protected]>wrote:

> Hi all,
>

> I'm the maintainer of openocd in NixOS.


Hi!

I've never heard of it but it seems like a nice idea, I'll try it out.


> Here is the list of flags I wonder whether I should enable:
>
>   --enable-jtag_vpi       Enable building support for JTAG VPI
>
>   --enable-usb_blaster_libftdi
>                           Enable building support for the Altera
> USB-Blaster
>                           using the libftdi driver, opensource alternate of
>                           FTD2XX
>

Probably should be enabled.


>
>   --enable-usb_blaster_ftd2xx
>                           Enable building support for the Altera
> USB-Blaster
>                           using the FTD2XX driver from ftdichip.com


No.


>
> (What happens if I don't specify any of the "usb_blaster" option? No
> support at all?)
>

Exactly.


>   --enable-amtjtagaccel   Enable building the Amontec JTAG-Accelerator
> driver
>

Enable.


>   --enable-zy1000-master  Use ZY1000 JTAG master registers
>   --enable-zy1000         Enable ZY1000 interface
>   --enable-ioutil         Enable ioutil functions - useful for standalone
>                           OpenOCD implementations
>   --enable-ep93xx         Enable building support for EP93xx based SBCs
>   --enable-at91rm9200     Enable building support for AT91RM9200 based SBCs
>   --enable-bcm2835gpio    Enable building support for bitbanging on BCM2835
>                           (as found in Raspberry Pi)
>

The above might compile but won't work unless openocd runs on the
respective platform. So generally no. For NixOS running on, say, RPi the
last one should be enabled.


>   --enable-gw16012        Enable building support for the Gateworks GW16012
>                           JTAG Programmer
>   --enable-presto_libftdi Enable building support for ASIX Presto
> Programmer
>                           using the libftdi driver
>

Enable.


>   --enable-presto_ftd2xx  Enable building support for ASIX Presto
> Programmer
>                           using the FTD2XX driver
>   --enable-openjtag_ftd2xx
>                           Enable building support for the OpenJTAG
> Programmer
>                           with ftd2xx driver
>

No.


>   --enable-openjtag_ftdi  Enable building support for the OpenJTAG
> Programmer
>                           with ftdi driver
>
  --enable-oocd_trace     Enable building support for some prototype
>                           OpenOCD+trace ETM capture hardware
>   --enable-buspirate      Enable building support for the Buspirate
>   --enable-sysfsgpio      Enable building support for programming driven
> via
>                           sysfs gpios.
>

Enable.


>   --enable-minidriver-dummy
>                           Enable the dummy minidriver.
>

Do not enable as it disables all other drivers.


>   --enable-remote-bitbang Enable building support for the Remote Bitbang
> jtag
>                           driver
>

Enable.


>
> Is there any reason not to enable all? (Except from maybe saving a few
> bytes of install size?)
>

Some may have dependencies that are unwanted, such as the proprietary FTDI
D2XX library, or may wreak havoc on a platform other than the intended as
they access memory mapped peripherals directly.


> And if enabling all the right thing to do for distros, how about
> making a "enable-all" switch so that on the next release we don't
> accidentally configure out some cool new feature just because we
> forgot to look very closely at ./configure --help?
>

Since the last release, libusb and hidapi based adapters are enabled
automatically based on what pkg-config says about library availability.
This will probably be extended for other dependencies as well, at least
libftdi.

/Andreas
------------------------------------------------------------------------------
_______________________________________________
OpenOCD-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openocd-devel

Reply via email to