[K42-discussion] K42 development trees

[Amos Waterland]

K42 is presently undergoing a rewrite of its boot logic and Linux
integration, which will allow us to run on the hypervisors found on
Power5 systems and on rHype, allow us to be kexeced from Linux, etc.
We have upgraded from 2.6.5-ameslab Linux sources to vanilla 2.6.13.

We would like to have a more open development model, so we have
published the source trees for this rewrite.  The trees are updated
daily with our development work, so anybody from a university or
elsewhere who feels like jumping in can do so.  The source is kept in
the git source code management system, which is used by the Linux kernel.

Here are the instructions to get going, assuming a devkit is installed
(http://ozlabs.org/pipermail/k42-discussion/2005-March/000840.html).
Steps with a semicolon at the end are expected to exit non-zero, as the
K42 and Linux builds depend on each other, so you have to bootstrap them
piecewise:

 git-clone http://www.cs.unm.edu/~k42/git/kitchsrc.git &&
 cd kitchsrc &&
 git-checkout k42-port &&
 make full_snapshot SEQ=1;
 cd .. &&
 git-clone http://www.cs.unm.edu/~k42/git/linux-030.git &&
 cd linux-030 &&
 git-checkout k42-port &&
 make ARCH=ppc64 CROSS_COMPILE=powerpc64-linux- \
  CROSS32_COMPILE=powerpc-linux- k42_defconfig scripts/kallsyms &&
 make -f Makefile.k42 MKANCHOR=~/devel/percs \
  CROSS_COMPILE=powerpc64-linux- CROSS32_COMPILE=powerpc-linux- k42libs &&
 cd ../kitchsrc &&
 make SEQ=1;
 make -f Makefile.new 

The resultant kernel is named k42-vmlinux, and will make it through boot
on many PPC64 systems.  It falls over after paging is set up, so that is
the focus of our current development.

If you do some work that you would like included, just make your git
tree public and post an email saying "please pull from X", or just run
`git diff HEAD' and post the patch.  The advantage of this development
model is that your trees are independent entities with your own version
history and branches.

Note that these trees are hoped to become the official K42 sources
someday, but right now are still pretty rough.  People interested in
these trees are probably only those doing K42 ports or device driver
work; otherwise you should probably stay with the mainline CVS tree.