On 12/07/2011, at 10:18 PM, Spencer Oliver <s...@spen-soft.co.uk> wrote:
> On 12 July 2011 13:08, Xiaofan Chen <xiaof...@gmail.com> wrote: >> On Tue, Jul 12, 2011 at 7:14 PM, Steve Bennett <ste...@workware.net.au> >> wrote: >>> On 12/07/2011, at 9:10 PM, Øyvind Harboe wrote: >>> >>>> If this problem eventually goes away, then I think it would make sense not >>>> to leave cruft in OpenOCD that we have to remove later? >>>> >>>> The workaround is available on the mailing list... >>>> >>>> I don't maintain or know much about ft2232, just a general comment. >>>> >>> >>> I have the fix, so I don't mind either way. >>> But I will let you help the next person who complains on the mailing >>> list that it doesn't work :-) >>> >> >> Like this. :-) >> >> mcuee@ubuntu64:~$ openocd-d2xx -f board/ek-lm3s1968.cfg >> Open On-Chip Debugger 0.5.0-dev-00950-g898dd3a-dirty (2011-07-11-21:42) >> Licensed under GNU GPL v2 >> For bug reports, read >> http://openocd.berlios.de/doc/doxygen/bugs.html >> Info : only one transport option; autoselect 'jtag' >> 500 kHz >> Error: unable to get latency timer: 4 >> in procedure 'init' >> >> >> > > I think we do need this patch - or something similar. > > can we have a comment in the code, perhaps a todo then it will show up > in our nice eclipse editor. Sure. Just say exactly how the comment needs to be formatted. > Or even better check the driver version. No idea how to do this. > > Cheers > Spen > _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
