-----Original Message-----
From: Tomi Valkeinen [mailto:tomi.valkeinen@nokia.com] 
Sent: Monday, June 21, 2010 2:08 PM
To: Aguirre, Sergio
Cc: Koen Kooi; Guruswamy, Senthilvadivu; 
linux-omap@vger.kernel.org; 
linux-fbdev-devel@lists.sourceforge.net; tony@atomide.com; 
Hiremath, Vaibhav
Subject: RE: [PATCH] DSS2 Include VRFB into omap2-3build only

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

quoted

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;

quoted

quoted

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

quoted

quoted

geschreven:

quoted

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

the display is

quoted

quoted

not choosen in the build.  Usually display is chosen from 

the board file.

quoted

It _should_ be possible to build DSS2, VRFB AND Tiler code 

at the same time

quoted

for a multi-omap build, and be executed selectively, 

depending on your

quoted

silicon detection and board code execution.

If you need to deselect it to succeed, then it's broken for 

multi-omap

quoted

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.

[Senthil]  Sergio, the v3 patch allows VRFB in multi-omap build.  Runtime
VRFB usage is not allowed on omap4 device and is allowed for omap2,3.
Refer to v3 patch 3/3.