It would be advantageous to move in the direction of exposing common target functionality through the target->type polymorphic interface.
Here are some on my list: - cp15 manipulation. The cp15 register exists across a wide range of arm targets. Perhaps mrc/mcr instructions in a more general way? cp15 is an interesting case because target->type is not really arm specific, but since we don't have C++ w/support multiple interfaces per class, etc. we have to make do best we can. Perhaps simply returning "unsupported" by default will be a good way to go here. - further mmu handling. I'm not quite sure what to expose and how here. Recently made more general: - virtual to physical address translation - physical memory read/write -- Ø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
