Honored Contributor
Honored ContributorHi All,
> It would be nice if you can setup a git repository. Done: http://www.psyent.com/git/linux_2_6_16 (http://www.psyent.com/git/linux_2_6_16) Everyone can see below for instructions. > I will check if I can setup a server for git/svn repository at home. That would be great -- using http is fine for pulls, but is useless for a push. I'd really like to see the community take the initiative for maintaining the kernel. I greatly appreciate the effort by Microtronix, but it's really not proper (or fair) to expect them to continue doing all of the work. We should be taking much of that burden. > I am working on initial patches to the latest 2.6.17.1 . Sounds great, I've avoided .17 because I thought it wasn't officially considered "stable" yet -- what is your opinion? Is is ok for nommu architectures? BTW: do you want me to send you the .16 patch? -- it might save you some time (and only includes the bare minimum). > I had asked git/svn from Altera, but with no results. That's unfortunate ... AD if fully behind Blackfin, and I'm seeing lots of momentum behind microblaze. It's really not asking much -- especially when you consider the value of the contributions. BTW: For kernel development git, IMHO, is the _only_ way to go. It was admittedly a bit awkward for me to learn, but I have been _very_ impressed. ================================================================ For everyone's benefit, here's how to get the Nios II code for linux-2.6.16: 1. clone the git repository $ git clone git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.6.16.y.git linux-2.6.16.git 2. create and checkout a "nios2" branch $ cd linux-2.6.16.git $ git branch -f nios2 master $ git checkout nios2 3. pull in the nios2 source tree $ git pull http://www.psyent.com/git/linux_2_6_16 (http://www.psyent.com/git/linux_2_6_16) nios2 4. builld the kernel as you always do Regards, --Scott
