On Tue, 2009-06-09 at 22:17 -0700, David Brownell wrote: > On Tuesday 09 June 2009, Rick Altherr wrote: > > I'm proposing that we use encapsulation and possibly ADTs to define > > clear boundaries for functionality in the code base. Rather than have > > one massive code base, I'd like to see subsystems that can be worked > > on internally with minimal effect to the users of that subsystem. > > OpenOCD has some of that and Zach has been doing a lot of work to > > refine that. > > I think we agree there. And yes, Zach's code overhauls are > good to see. > > Something else that's worth observing is that clean boundaries > might make it practical to build an OpenOCD core which doesn't > pre-link every interface, NOR, NAND, and CPU driver ... they > could be dynamically loaded modules. (CPU drivers being the > most complex.) > > Having clean boundaries there would make it easier to provide > new modules, by reducing the amount of information folk need > to master before they can plug in new code.
I have developed loadable module support in the past, and it's already on The List here. If I can afford to take the time, OpenOCD will be fully decoupled from its various driver modules. --Z _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
