On Monday 15 June 2009, Zach Welch wrote: > Others have pointed out that this licensing violation occurs only when > distributing the binaries, so I do want to provide assurance that I have > no problem supporting these types of features -- for developers to use > in local builds _only_. I think such support is great, in fact.
So ... no particular issue with the patch I used to start out this thread? We could maybe achieve closure on this issue, at least for the upcoming release? :) A key change was the advice-to-packagers: | That said, the OpenOCD developers would also like you to follow a few suggestions: | 1. Send patches, including config files, upstream. | 2. Always build with printer ports enabled. | 3. Use libftdi + libusb for FT2232 support. Previously #3 implied the D2XX option was viable, and went on there for some length... I think I'll re-spin that patch to point out that the performance difference is marginal, which seems to reflect *current* reports (vs a-few-years-old, or perhaps bitbang mode not mpssse). - Dave _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
