On 04/25/2012 10:22 AM, Somebody in the thread at some point said:
Hi -
Maybe it's something on my side but I noticed I have android logging coming on my vanilla defconfig now. I can force it off in my defconfig, but I am wondering if that's intentional?
It doesn't seem to be android logger itself, just something else I always saw after Androidization, kernel logging that's anyway enabled to console by printk / loglevel is repeated without having it severity tag parsed off. That's objectionable now the basis is androidized and it still happens even with CONFIG_ANDROID off.
We're still undergoing uplevel on tilt-tracking and didn't get back to tilt-3.3 functionality yet (OMAP4 boot is busted, although hopefully we have a fix for that today), so I put off this common config thing.
OMAP4 is booting again FWIW just a few dings to sort out.
However now I see it included, aren't most of the patches about board support redundant? If LTs base on this, they will add in their own golden initial defconfig for their board(s) at that point; when they're combined they'll all be in the combined tree. It seems like I shouldn't be seeing a defconfig about Panda coming in with this base tree, but create it (perhaps after mixing in config fragments that did come in with the base tree) in my tree.
Looking closer at this, we prefer not to have CONFIG_MTD or CONFIG_JFFS in the base config. We don't really have a case for them on Panda.
You might want to push those out into a mtd.conf we will pass over, or something similar.
-Andy