[PATCH 00/12][RFC] Intial Kconfig Fragment Demo

Amit Kucheria amit.kucheria at linaro.org
Wed Mar 9 08:51:00 UTC 2011

On Wed, Mar 9, 2011 at 10:30 AM, Andy Green <andy at warmcat.com> wrote:
> On 03/09/2011 08:17 AM, Somebody in the thread at some point said:
> Hi -
>>> 5) The igep, overo, and panda configs all use the same omap3
>>> config according to the hwpacks. I'm not sure I believe that,
>>> but went along with it to get this out the door.
>> They do use the same config - or 'flavour' as they are referred to in
>> the Ubuntu kernel config system.
> Panda is OMAP4 and the other two are OMAP3 AIUI, I am aware they are all
> under "OMAP2+" in the kernel, but there are really significant differences
> from configuration point of view like SMP or not.
> How is that handled with the same config?

One can build a single kernel binary that runs on OMAP2/3/4 platforms
from the mainline kernel. That has been the main requirement from the
maintainer to add new board support. Everything under mach-omap2 and
plat-omap is written for runtime detection of features.

However, last I looked, there were problems with the ARM locking
primitives being patched at runtime. So it prevented SMP-on-UP
kernels, that is, SMP had to be turned off. But that will eventually
get fixed so you could have a SMP kernel running on a UP system. This
is how x86 does it today.


More information about the linaro-dev mailing list