[Openocd-development] mc1322x patch

2009-03-26 Thread Duane Ellis
Jeff Williams: >> Last we heard Duane was "waiting for the dust to settle". I think it has, so, what can we do about your patch. I'd like to take it in pieces. Lets avoid "changing the state numbers" for a moment. and lets focus on the "arm7-thumb" parts. Do you have, or can you create a strip

Re: [Openocd-development] PATCH: openocd jlink.c cleanup

2009-03-26 Thread Jeff Williams
Hi Zack, Let's still coordinate efforts if possible. For instance I'd be happy to test your changes against the ARM7 gear I have if you're willing to test my changes against ARM9 if that's what you have. Jeff El Mar 26, 2009, a las 19:43 , Zach Welch escribió: > Feel free to drop my patch.

Re: [Openocd-development] PATCH: openocd jlink.c cleanup

2009-03-26 Thread Zach Welch
Feel free to drop my patch. This effort was quick and painless, and functional improvements from others can be added first. This was mostly an initial audit of the code and an quick test to see if the code module was free for further patching. I somewhat expected a conflict, since I did not scou

Re: [Openocd-development] PATCH: openocd jlink.c cleanup

2009-03-26 Thread Jeff Williams
Hi Zach, My only concern is that we're still waiting on some kind of resolution on JLink changes to support MC1322x. Last we heard Duane was "waiting for the dust to settle". Is there any way to coordinate these two efforts, so that we don't end up with a mess of wasted work? For instan

[Openocd-development] PATCH: openocd jlink.c cleanup

2009-03-26 Thread Zach Welch
Howdy, I have attached a patch to simplify the jlink.c file, which I wanted to submit before trying to do some more work on that module. With these changes, the code will fit neatly into an 80 column terminal and should be much easier to read. There should not be _any_ functional changes; even t