On Tue, Oct 2, 2012 at 1:09 PM, Freddie Chopin <[email protected]> wrote:
> W dniu 2012-10-02 12:56, Spencer Oliver pisze:
>> but then you could also include the following, as they relate to this f3 
>> support
>> http://openocd.zylin.com/809
>> http://openocd.zylin.com/810
>
> You're right - done. Anything else? Maybe we could also cherry-pick your
> "validations" of ftdi configs?
>
>> this is also a bug fix for the new ftdi driver, that fixes issues with
>> using jtag_rclk
>> http://openocd.zylin.com/839
>
> On the other hand this one is not approved - it's waiting for Andreas'
> response... I'm compiling it right now to test and we'll see. I'll push
> it too and we can decide on gerrit.
>

This one should be safe, I just wanted to check if there wasn't some
easily fixed logic error in the caller that would be a better
solution. It felt odd that by returning ERROR_FAIL when it previously
returned success, something would work better. Haven't had time to
check it out, though.

Just don't pull too many patches into the bugfix release, it's
supposed to fix bugs, not introduce others. I do think that even
though 0.6.0 is the first release with the ftdi driver, so there's no
regressions there, it's good to include ftdi bugfixes that would
otherwise hamper widespread testing in 0.6.x and delay deprecation of
the old driver. That would include correcting config files and marking
them as verified.

I personally wouldn't mind having the updated stm32f3 support in
0.6.x, although I think that almost falls outside what's suitable for
a bugfix release.

/Andreas

------------------------------------------------------------------------------
Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy New Relic app performance management and know exactly
what is happening inside your Ruby, Python, PHP, Java, and .NET app
Try New Relic at no cost today and get our sweet Data Nerd shirt too!
http://p.sf.net/sfu/newrelic-dev2dev
_______________________________________________
OpenOCD-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openocd-devel

Reply via email to