Hello list, >I would suggest that ft2232.c 1824 is committed to trunk and >that the newest version of ft2232.c is split into a series of >patches. First commit all the harmless changes, then >try to divide thinigs into "real" changes. But we should use the long sequence as default? In this case we have a working solution. And for testing we can enable the short sequence and can check step by step which patch breaks the functionality.
Best regards, Michael -----Ursprüngliche Nachricht----- Von: [email protected] [mailto:[email protected]]im Auftrag von Øyvind Harboe Gesendet: Freitag, 22. Mai 2009 11:03 An: Michael Fischer Cc: Openocd-Dev; [email protected] Betreff: Re: [Openocd-development] SAM7S256 is broken by 1825 On Fri, May 22, 2009 at 9:07 AM, Michael Fischer <[email protected]> wrote: > Hello Øyvind, > >>Does svn head work if you use 1824 for ft2232.c only? > I have make a new test, copy of the 1872 do not help > only. I must use the long sequence too: > > tms_sequence long > > This mean, I must copy the 1824 over the 1872 and use > the long sequence to get the SAM and LPC working. Great testing! I would suggest that ft2232.c 1824 is committed to trunk and that the newest version of ft2232.c is split into a series of patches. First commit all the harmless changes, then try to divide thinigs into "real" changes. I won't be doing this, I don't want to touch ft2232.c, I'm just trying to help out with testing a bit. -- Øyvind Harboe Embedded software and hardware consulting services http://consulting.zylin.com _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
