On 1 October 2012 07:05, Freddie Chopin <[email protected]> wrote: >>> Is there any code that fits such characteristics? I just cannot see >>> anyway >>> it would be possible to gain any performance by having the working area >>> available past resets and resumes - when you do anything that requires >>> working area and should be fast (flashing) you do it in one go without >>> any >>> resumes or resets in between... >> >> >> Apparently the nand code depends heavily on re-use of the working >> area, and it doesn't fit the assumption of making all the work in one >> go. Every read will need one algorithm execution and if that now needs >> to carry the algorithm upload too, it's bound to be slower. How much I >> have no idea. Same for the MIPS fastdata access and arm7/9 >> read_memory. >>
rather than introduce speed regressions i would sooner revert the original commit that caused this issue. This would give us more time to find a solution that does not impact the speed for mips/cfi code. Spen ------------------------------------------------------------------------------ Got visibility? Most devs has no idea what their production app looks like. Find out how fast your code is with AppDynamics Lite. http://ad.doubleclick.net/clk;262219671;13503038;y? http://info.appdynamics.com/FreeJavaPerformanceDownload.html _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
