>> Actually, the minidrivers don't clone today, so that's already taken care of. > > Doesn't that apply only to zy1000.c ?
The USB case needs to delay execution to build a long scan, so there copy is required. >> The USB drivers have a 1ms roundtrip problem to contend with, the >> rest is in the noise, essentially. There is plenty of evidence to this >> effect. > > *You* brought up performance as concern... My goal was primarily > streamlining code. I did. We need both streamlined and fast code. Until we have both sorted, we leave things the way they are. > Your example seemed to be too much of a workaround rather than > addressing the problem directly, which IMO is that the uint32_t case > is so common that there should be a short unambiguous way to deal with > it. > > Of course even a set of standard wrappers to package the set-up of the > most common field configurations would help a lot, without also > serving as a shortcut into the minidriver-layer to avoid the copying. I've got some thoughts on how to do this, but nothing written up yet. >> Also we have to *carefully* consider how we can make *small* steps that >> can be tested on all the hardware combinations. Otherwise any change >> is unlikely to pay off. We're getting there but it will and should take time. > > It was a suggestion on long-term goals. Small steps are usually most > effective when they go towards a specific target. I'm doing small steps in a branch for now. We'll see how it pans out. That branch might end up being a big leap before it is pushed to the master branch. -- Øyvind Harboe http://www.zylin.com/zy1000.html ARM7 ARM9 ARM11 XScale Cortex JTAG debugger and flash programmer _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
