On Tue, 2009-04-21 at 09:13 -0700, Jeff Williams wrote: > Hey guys, > > The recent jtag.[h,c] and jlink.c churn has totally hosed all of my > pending patches. BTW: these changes included a lot more than just > fixes to the TAP handling for significant improvement in efficiency > and increased device support. I'd also included a whole bunch of > changes to significantly improve state debugging to make both pod > debugging and JLink development better. > > I'm a little frustrated that this increase in functionality is now in > pieces on the floor to quash compiler warnings and churn to suit taste > and style. I'd asked that we not churn the code until this big patch > got resolved. It's now going to take A LOT of time for me to sort > this out, and I don't have a lot of time now. Too bad, because there > were a group of us excited to get MC1322x up on OpenOCD - now that's > probably toast.
Jeff, The original patches you posted were not in a state that was suitable for directly applying to the tree, so they were taken by Duane. Thereafter, the community has given time for Duane to post the changes (finished or not). As I write this, those have still not been posted. I thought this was all in the public record, though I guess one might have to read between the lines to see this full story. This explains the lack of apparent progress on your patches; however, I would be frustrated in your shoes too. I will get to those changes in time, pull them apart, and the pieces will get into the tree. As it stands, I seem to be in the best position to work on the J-link driver (i.e. free time and skill), to push it through to a working state. Certainly, we will need you to stick around long enough to help re-test the integration of your work, _when_ that day comes. Don't give up yet. I will post another message to cover the fine points of these topics, which will give my pointed perspective on these matter for the community to consider. I wanted to reply to you personally first as this medium is very impersonal. I do not want you to read that message and think it was solely directed back at you; it most decidedly is not. :) Cheers, Zach _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
