Hi Freddie.
(a copy for the list)
On Sun, 26 Apr 2015 23:08:45 +0200, Freddie Chopin wrote:
> Personally I enable everything that is possible - including anything
that needs libftdi.
--enable-aice --enable-amtjtagaccel --enable-armjtagew --enable-cmsis-dap
--enable-dummy --enable-ftdi --enable-gw16012 --enable-jlink
--enable-jtag_vpi --enable-legacy-ft2232_libftdi
--enable-opendous --enable-openjtag_ftdi --enable-osbdm
--enable-parport --disable-parport-ppdev
--enable-parport-giveio --enable-presto_libftdi
--enable-remote-bitbang --enable-rlink --enable-stlink
--enable-ti-icdi --enable-ulink --enable-usb-blaster-2
--enable-usb_blaster_libftdi --enable-usbprog
--enable-vsllink
Thank you for the reply and recommendation; this is very valuable.
I can see you're a bit richer than me. :)
-But I don't see "--enable-arm-jtag-ew", is that intensional ?
> I even enable legacy ft2232 driver which I know some people don't like
(; I'll think about not enabling that after 0.9.0...
Anyway - libftdi is pretty easy to build, so why not just do it and
solve the problem? (;
I have no problem building libftdi - it's of course quicker not to build it. ;)
I asked because I recalled something about it being deprecated and not
recommended, so I'd like to make sure what's best, before I actually make my
build public.
I believe there's good reason to enable the same interfaces as you do; because
then people would not have problems with differences between the two builds.
Love
Jens
------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
OpenOCD-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openocd-devel
