Here is a random list of some of the interface problems: - define a common mechanism by which OpenOCD handles interfaces. C++ handles this trivially(pure abstract classes), OpenOCD should settle for nothing less than ;-). Solve the upcast problem... Be able to distinguish runtime between "not implemented yet" and "should not be implemented", etc.
- cache handling happens inside the targets. It should be possible for gdb_server.c to implement software breakpoints in read only memory(protected by MMU) using target_xx() fn's. - arm needs to define interfaces that allow mrc/mcr type things to be placed into a sane location. - look at register.c for a particularly vile example... register_get_arch_type.. shudder... :-) -- Ø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
