On Fri, 2010-06-18 at 18:57 +0200, ext Aguirre, Sergio wrote:

Senthil,

quoted

-----Original Message-----
From: linux-omap-owner@vger.kernel.org [mailto:linux-omap-
owner@vger.kernel.org] On Behalf Of Koen Kooi
Sent: Monday, May 10, 2010 3:03 AM
To: Guruswamy, Senthilvadivu
Cc: linux-omap@vger.kernel.org; linux-fbdev-devel@lists.sourceforge.net;
tony@atomide.com; tomi.valkeinen@nokia.com; Hiremath, Vaibhav
Subject: Re: [PATCH] DSS2 Include VRFB into omap2-3build only


Op 10 mei 2010, om 10:01 heeft Guruswamy, Senthilvadivu het volgende
geschreven:

quoted

Building a multi-omap kernel is not impacted as long as the display is

not choosen in the build.  Usually display is chosen from the board file.

Solving this problem involves doing these selections in run time, NOT in build time.

One of the solutions for this is to provide all this selections as part
of some platform driver data.

It _should_ be possible to build DSS2, VRFB AND Tiler code at the same time
for a multi-omap build, and be executed selectively, depending on your
silicon detection and board code execution.

If you need to deselect it to succeed, then it's broken for multi-omap
builds. That's the core problem and it hasn't been addressed until date.

I think the v3 patch set does it correctly. It allows VRFB to be built
only if ARCH_OMAP2 || ARCH_OMAP3, but does not turn VRFB off on
ARCH_OMAP4.

 Tomi