Hello world :-)

On Mon, Mar 21, 2011 at 3:00 PM, Øyvind Harboe <[email protected]> wrote:
> In terms of maintenance we can't really support
> two files that are so similar, so unless I hear major
> objections, I'd rather go with this patch and sort
> out any regressions afterwards.

Maybe those two files are similar, but they are targeted for different
cpu families that have different quirks to work, so I think they
should be kept separated to avoid mess that can show up after some
time - usually one more file is not a pain but can make solution more
clear and elegant - thats only my opinion, not an objection :-) If you
prefer one file, why not name it "arm_cortex.c" to avoid putting
cortex_a9 stuff into cortex_a8 file? :-)

I dont have any experience with cortex a8/a9 but i have just ordered
them and should have in couple weeks for testing :-)

Best regards :-)
Tomek

ps/2: I got already into openocd internals, i like the idea of adding
openocd into existing application and sharing the api into tcl rather
than hardcoding :-)

-- 
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development

Reply via email to