On Sun, 2009-05-31 at 10:50 +0200, Øyvind Harboe wrote: > > It sounds like the problem relates to the fact that reset_config will > > not work for all combinations of interfaces and targets. All of this > > discussion makes me think that OpenOCD needs two reset_config commands: > > one for the interface and one for the target. With knowledge of both, > > OpenOCD could do the right thing in all cases, as I understand things; > > however, this may be incorrect for reasons that others can explain. > > What I would like to see is that we push funky rules into board/target config > files and keep the reset_config implementation as simple as possible. > > There are pieces missing today, such as the board/target config files > ability to detect capabilities in the interface.
It seems simpler for the authors of the interfaces and boards files to simply declare what the hardware can do, and OpenOCD should work out the best capabilities to use. That seems simpler for script authors than trying make them detect things in the configuration files. Or am I missing something here? --Z _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
