-----Original Message-----
From: Dave Martin [mailto:dave.martin at linaro.org]
Sent: Wednesday, February 09, 2011 3:18 PM
To: Santosh Shilimkar
Cc: Tony Lindgren; Nicolas Pitre; linux-omap at vger.kernel.org;
Russell King - ARM Linux; linux-arm-kernel at lists.infradead.org
Subject: Re: [PATCH 00/14] Fix issues with ARMv6+v6k+v7 kernels

On Wed, Feb 9, 2011 at 6:04 AM, Santosh Shilimkar
[off-list ref] wrote:

quoted

quoted

-----Original Message-----
From: linux-omap-owner at vger.kernel.org [mailto:linux-omap-
owner at vger.kernel.org] On Behalf Of Tony Lindgren
Sent: Wednesday, February 09, 2011 6:06 AM
To: Nicolas Pitre
Cc: Santosh Shilimkar; Russell King - ARM Linux; linux-
omap at vger.kernel.org; linux-arm-kernel at lists.infradead.org
Subject: Re: [PATCH 00/14] Fix issues with ARMv6+v6k+v7 kernels

* Nicolas Pitre [off-list ref] [110208 12:41]:

quoted

On Tue, 8 Feb 2011, Santosh Shilimkar wrote:

quoted

quoted

I think it's probably going to be better to _purposely_

break

quoted

quoted

the

quoted

quoted

quoted

OMAP build when it covers v6 and v7 CPUs in these kernels

as I

quoted

quoted

don't

quoted

quoted

quoted

think it's sanely fixable given where we are.

Agreed. ?At least making SMP unavailable when both v6 and v7

are

quoted

quoted

quoted

configured should be small and good enough for 2.6.38-rc5.

That's probably the best solution as then we can still do boot
testing on all omap2plus_defconfig boards.

Just to be clear, are we saying disable SMP from omap2plus build.
If the v6, v7 is not fixable then, we also need a SMP
config for OMAP. Just boot test with SMP disable config for
OMAP4 is not enough.

You could also have a "v7+" unified kernel -- i.e., supporting
OMAP3+4+SMP.
This is what we currently do in Linaro, since we're focusing on v7
and above.

This sounds good way forward considering future OMAP architectures
as well.

But I let Tony comment on this idea.

Regards,
Santosh