Hi,

On Mon, Mar 03, 2014 at 12:29:31AM +1300, Rob Brown wrote:
> It seems that I've caused 5 changesets to be posted on gerrit due to the loop 
> in 
> step 5 of the patch guide, and I presume this will cause people to waste time 
> looking at them.

It seems the hacking guide clearly states you're supposed to --amend
(-a) your patches, and when you amend, the change-id is kept, so it
would be a single patch on Gerrit. Are you still sure there's a
mistake in the HACKING manual?

Regarding your patches, do I understand it right that you want to use
proprietary library because you do not want to install WinUSB driver
for your device because some proprietary "crossworks" can't use that
adapter with WinUSB drivers? And so you either have to use the
libftdi version of OpenOCD's ft2322 adapter driver or that d2xx
version of the same old deprecated ft2232 driver, and you can't switch
to "ftdi" driver at all?

If this is really the case, wouldn't it be better and cleaner in the
long run to employ libwdi and write a custom app that would
temporarily switch WinUSB to the proprietary driver before starting
crossworks and switch it back to WinUSB after it's finished? I know it
sounds ugly but the task itself (running some silly "ide" on some
silly "os") is horrible; supporting the deprecated and known to be
buggy OpenOCD code for ft2232 is even worse, IMHO.

What do you think?

-- 
Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
mailto:fercer...@gmail.com

------------------------------------------------------------------------------
Flow-based real-time traffic analytics software. Cisco certified tool.
Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer
Customize your own dashboards, set traffic alerts and generate reports.
Network behavioral analysis & security monitoring. All-in-one tool.
http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk
_______________________________________________
OpenOCD-devel mailing list
OpenOCD-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openocd-devel

Reply via email to