Don't mind me when it comes to the NAND. I won't be active probably until Christmas break when I no longer have persistent projects :). At that time I welcome the challenge of forcing my stuff into the proper mold. I'll have to make a list. Have fun!
// Dean Glazeski On Fri, Dec 4, 2009 at 7:21 PM, Zach Welch <[email protected]> wrote: > On Fri, 2009-12-04 at 03:43 -0800, Zach Welch wrote: > [snip] > > > The last two patches begin to split the NOR flash layer into > > > public and private APIS (<flash/nor/{core,imp}.h>, respectively) > > > and into core and TCL modules (flash/nor/{core,tcl}.c, likewise). > > > > > > More patches will be required to finish this job, and these changes > > > will be both disruptive and boring. The result will be much better > > > separation of mechanism and policy in this area of the tree, then > > > I will move on to the next module deserving such treatment. > > > > Pushed, after a lively discussion.... ;) Stay tuned for more patches of > > this nature. > > I have pushed more patches that remove flash.[ch] by splitting them into > various files in flash/nor/. Doing so separated the NAND tree from the > NOR tree, so many files will give faster rebuilds. Even better, > target.h is no longer exposed through the public NOR flash API (i.e. > flash/nor/core.h). It can stand further improvement, but this marks a > major milestone for this tiny part of the tree. > > I can proceed to the NAND layer or the target layer, but both of these > have other active development and may be too disruptive at present. > > Cheers, > > Zach > > _______________________________________________ > Openocd-development mailing list > [email protected] > https://lists.berlios.de/mailman/listinfo/openocd-development >
_______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
