On Thu, Nov 29, 2012 at 2:05 AM, Jonas Bonn <[email protected]> wrote:
> Aside from that, Linus' repo is what you should be basing new features > on... hence, that's the repo that should be the 'openrisc' one (as > opposed to personal repos) on the main github page, in my opinion. (And > Linus' repo is already mirrored on github, so there's really no need to > do it again...) > Ok, so it's just confusion on my part. There's some conflicting documentation around, and it just wasn't clear to me what we should be using as the "official" one :) The reason I did this is that I want to add support for no-delay-slot mode. So I'll just delete the repo I just created and fork Linus' repo in its place so eventually I can push the changes there. There's a bunch of these scripts floating around. Mine's a Makefile and > parallelizes better than the rest... I updated it last weekend to build > Stefan's latest stuff... I should probably publish that somewhere. > Mine will parallelize the build fairly well, as well. It's a script for SCons, which is a dependency-base build tool like make, but it's python-based so it's ridiculously flexible... but unfortunately harder to learn. I know someone who already had most of this in place... :( > Are you referring to Ruben's orbuild? I took a look at it, but I haven't used perl in years, and digging into it to figure out where to put my changes seemed harder than just whipping something up for scons :) -Pete
_______________________________________________ Linux mailing list [email protected] http://lists.openrisc.net/listinfo/linux
