Hi Grazvydas,
Kernel:
That OE patching is not a good thing, it confuses the hell out people. People just assume they can clone pandora-kernel.git and build their custom kernel similar way they can do with kernel.org (and quite
rightfully
so). Only minority have full OE setups and there were plenty of "I'm building my kernel, where is squashfs?" type of questions on the boards.
So from next release everything needed will be in pandora-kernel.git and defconfig will be in perfect sync with OE, so that a toolchain of choice +
a
clone of pandora-kernel.git is all that's needed to build full-featured
custom
kernel.
It looks like AUFS2 is the only thing that we need and is not in mainline, right? (squashfs is in mainline for a while now). I can start looking at merging this soon.
That works for me wonderfully, I went to some length to get rid of most of the patches and AUFS2 was about all that was left, if you can deal with that I would appreciate it (it will also make mainline OE easier as we can just have a very simple kernel recipe without any hacking).
Grazvydas, I would appreciate your take on this being a good idea or not? We could stay with .27 (or .35) but it seems sensible to move to a very recent kernel and I would love to be able to make use of it in
userspace.
.35 was more of a test (it's not even based on stable kernel, it's based
on -
rc3) and should not be used. I think we should start from .37 directly with no migration from .27, as the only thing really missing
there
is BT. There are a few regressions/breakages that I know of already (OSS emulation problems, NAND errors and performace regressions, omapfb X driver not liking default 24bpp mode; should be fixable with fbset in .xinitrc) but that's no reason to start with .27 and we'd better give .37
testing
ASAP so it becomes better at the end.
BTW I'll probably be rebasing pandora-37 branch on 2.6.37.1 this week.
Okies, AUFS2 aside I'll move to 2.6.37 from the pandora-37 branch TIP and only go for that version if you think we are in good shape.
Less work for me then maintaining some munge :).
Thanks,
John