I made a little progress this week.  First, I managed to build a 2.6.32 kernel based on Angstrom's recipes that appears to be the build to use for PSP support.  Something tells me this is sufficient to get the Xorg driver working, but I haven't tried it yet.  In any case, I have a better understanding of the recipes now and should be able to build any kernel they build by porting the kernel recipes to my build (which is easy using my own make-based recipe structure).  It should be much easier to experiment until I find a kernel that works with the Xorg driver.

I also grabbed another Narcissus build, a minimal build with X running Matchbox, as a comparison baseline.  I can see the kernel config from this though it doesn't say where the kernel source is pulled from.  The PSP kernel (above) comes from the arago trees so I'm hoping that's the right one.  I have not, as yet, compared the kernel config from the PSP build to the one on the Narcisuss build. 

Second, I think I figured out how to add neon support to Crosstool-NG.  This wasn't hard, but until you know what you're looking for it is.  I finally found a configuration option (Crosstool-NG uses a kernel-styled menuconfig, which is nice) – CT_ARCH_FPU, which is in the Target submenu – to set.  I also changed from software FPU to hardware FPU.  Again, these are just guesses at this point.  I'm building the toolchain again and will use it later to rebuild the kernel and see if that boots tonight.

SourceForge CVS is still down.  At some point I may have to do a clean rebuild to make sure my sandbox is working properly from a build perspective and then just create a Git tree on GitHub or Gitorious -anyone have a preference? I'm leaning toward gitorious since there are many other BeagleBoard repos there.  I'm just anal about checking in a tree that doesn't build – I don't think that should ever happen so I need to reverify the come build once before I switch to git..