A battery driver has been added for the GTA01. The immediate beneficiaries of this feature would be the FSO and SHR distros. (Note that this code doesn't do anything new for the kernel -- instead, it just exposes information that was previously only available from apm in the same way as the GTA02 exposes that information.)
This is something I've been meaning to work on for a long time -- and then when I finally got started, I discovered that it was harder than I thought. It's still very much a work-in-progress, but the OE repository now has a recipe to build a trimmed-down variant of the FSO image suitable for use by Qt Extended, as well as a recipe to create a toolchain suitable to build Qt Extended. This should serve to bring the continuing improvements in infrastructure (kernel, boot time, and other various fixes) to Qt Extended users with far less effort than in the past. This is outlined on the new Qt Extended page.
For one thing, I've been "fudging" on the requirement to distribute sources with the binary kernels -- the source for the bit of code that isn't in the Openmoko git repo is on my site, but that's not the whole story all the time -- what's also important are the bits that I leave out of the kernel. Those bits have been infrequent in the past, but no so going forward (there's some stuff in the so-called "stable" branch that isn't particularly stable at all -- it's got to go).
So, the net of it all is that we have a git repo:
http://repo.or.cz/w/linux-2.6/openmoko-kernel/knife-kernel.git
My branches will all be prefixed with "mwester"; the one the kernels here have been based on is the "mwester-stable" branch. The version string reported by the kernel can be matched up to the git hashes to find out exactly what was used to build that kernel at any time.
If anyone wishes a place to keep their own kernel branch, just ask -- you'll need an ID on repo.or.cz, and I'll be happy to give you rights to push to that tree.
Now, as for the name: why "knife-kernel"?
You decide. Which sounds better?