Yes, It's time to create a new repository with a release candidate so that all the developers can try out the code and discuss issues. Here's what I would suggest.
Step 1: Locate the most up-to-date versions of the or1200, its documents and the wishbone spec and copy them into a new repository. Freeze the originals so that nothing we do will impact the users. The only changes that we will make to the "official" release are critical bugs that are also made to the release candidate as well. Step 2: Create a tool flow for simulation and linting and copy over as many or1200 sims as we can find. We need to create a robust suite capable of verifying the entire design. Step 3: Let developers try it and discuss what works and what doesn't. Anyone can modify a cloned database to show their proposals in action. The stuff that works gets pulled back into the golden copy. John Eaton On Thu, Apr 12, 2012 at 5:13 AM, Olof Kindgren <[email protected]>wrote: > Hi everyone, > > There are a lot of things going with or1200, and recently there have been > more patches than we have had time to deal with. I know myself that it is > frustrating to submit patches without anyone acknowledging them. Some of > the proposed changes are also potentially breaking the sw/hw ABI, which > means we have to be really careful when we apply them. > > My proposal is that we try to focus our efforts on releasing a new or1200 > rel3 (or is it rel4). We have been talking about this for quite some time > now, but not really gotten any closer to finalizing this. Therefore I > started a basic roadmap page on the wiki > http://opencores.org/or1k/OR1200_Roadmap and for now assigned three tasks > for the next release. I know that it's more fun to add new features, but I > think it's more important to have proper release now. If no one else > objects, I would be willing to step up as release manager for this release. > Feel free to add items to the wiki, but keep them under unassigned tasks > until we have discussed them publicly. The three items listed under the > next release should of course also be discussed, but this is my initial > proposal, and I think it is plenty of work just to fix those items. > > -- > 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 > >
_______________________________________________ OpenRISC mailing list [email protected] http://lists.openrisc.net/listinfo/openrisc
