> 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.
I looked at the jtag part of that. This does not interfere with my patch so it is safe to apply mine immediately. I would object to hunk #1 in Dick's patch because it masks a potential error. Either the added code is essentially a NOP or it is hiding an earlier error in calculating the number of fields. I don't have the time now to dig into the FT2232 changes so I can't comment on the other hunks. But there is next to zero overlap with my patch. Michael _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
