> It isn't just about the interfaces. I would have had to understand > what exactly the armv4_5 etc code does and what it's side-effects are. > But the code is hopelessly bloated. Reading a simple local copy of PC > is a drama of epic proportions: > > buf_get_u32(armv4_5->core_cache->reg_list[15].value, 0, 32)
It's not a pretty sight. On the other hand I'd like to get rid of as many macros as possible, especially those that are specific to one file. While arm11 code is a bit obtuse here, it makes it painfully obvious where the OpenOCD code is tedious. Compare the above to R(PC)... -- Øyvind Harboe http://www.zylin.com/zy1000.html ARM7 ARM9 ARM11 XScale Cortex JTAG debugger and flash programmer _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
