2012/1/17 Ouabache Designworks <[email protected]>: > The "Pragmatic Programmer" was written by two guys who have done enough > firmware projects to > understand what works and what doesn't. > > Their main rule is that you NEVER copy data in a database. Everything is > stored in one designated > location and anyone who needs it has to get it from there. Openrisc violates > this rule and your post > is a good example of the troubles that this can create. > > minsoc did it right in that they grab their processor from it's original > location. Orpsocv2 messed up by > making a copy. I think that there may even be some others around as well. > > We must fix this but doing so will be a challenge. We must get all known > fixes put back into the original > or1200 along with a test suite that proves that it works. Then oprsocv2 and > others must remove their > copies and start using the original. > > I am willing to work on this, Anyone else? > > > John Eaton > I fully agree, and this is one of the main aspects of ORPSoC v3 that I am working on. I have put a lot of effort into sorting out white space changes from functional changes in the ORPSoC v2 cores, to be able to keep the good stuff as patches.
There is some information on the wiki about ORPSoCv3 and I'm hoping to release a todo list soon with things that need to be done. -- Olof Kindgren ______________________________________________ ORSoC Website: www.orsoc.se Email: [email protected] ______________________________________________ FPGA, ASIC, DSP - embedded SoC design _______________________________________________ OpenRISC mailing list [email protected] http://lists.openrisc.net/listinfo/openrisc
