> Then why not just copy the current trunk to something like > branches/merge-ftd2232-vs-r1809 and then commit the change there so > that it can be tested?
It's even easier than that :-) jtag.c needs a few tweaks and a bit of testing and it can be committed first without further ado. It just needs "someone" to step up to the plate and take charge. https://lists.berlios.de/pipermail/openocd-development/2009-May/006586.html I suspect that ft2232 can be refactored in two rounds. The first without no effect on functionality. I have not really worked on the ft2232 code and I'd rather leave that to someone else. -- Øyvind Harboe Embedded software and hardware consulting services http://consulting.zylin.com _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
