On Thu, 2012-03-29 at 11:00 -0700, John Stultz wrote:
On 03/29/2012 02:22 AM, Jon Medhurst (Tixy) wrote:
John, I've attached a config fragment for Versatile Express.
Great! I've merged that in! There's a few warnings though:
Value requested for CONFIG_ARCH_VEXPRESS_DT not in final .config Requested value: CONFIG_ARCH_VEXPRESS_DT=y Actual value:
Value requested for CONFIG_FB_ARMHDLCD not in final .config Requested value: CONFIG_FB_ARMHDLCD=y Actual value:
I'm guessing these are features not in the base 3.3 tree? If so you might want to break those out and re-add them with those patches.
To do that the vexpress config fragment will need to be a topic branch on the ARM Landing Teams git, and every topic which changes a config needs to be stacked on top of that. Is that what is expected?
Currently I have two separate topics with monolithic Android and Ubuntu configs, so if we are moving over to config fragments I can delete these?
This includes loadable module support because one of our topic branches adds the gator module with a default config of 'm'. I did this because Linaro kernels are expected to have this module available but I didn't see any reason for it to be built-in, and as there may be versioning issues between it and the separate user side daemon, I thought it wise to keep the door open for loading an alternate module obtained from elsewhere. That decision does mean that all Linaro kernels would need loadable module support built in, but I don't think that is a bad idea.
Tushar had similar request, but I don't think the android configs (at least the ones I've managed) use modules, so I've added the MODULES=y to the common ubuntu.conf file.
That sounds fair enough, and meets the current requirements. We can deal with other requirements as the become apparent.