> -----Original Message----- > From: Tomi Valkeinen [mailto:tomi.valkeinen@xxxxxxxxx] > Sent: Monday, June 21, 2010 2:08 PM > To: Aguirre, Sergio > Cc: Koen Kooi; Guruswamy, Senthilvadivu; > linux-omap@xxxxxxxxxxxxxxx; > linux-fbdev-devel@xxxxxxxxxxxxxxxxxxxxx; tony@xxxxxxxxxxx; > 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: > > Senthil, > > > > > -----Original Message----- > > > From: linux-omap-owner@xxxxxxxxxxxxxxx [mailto:linux-omap- > > > owner@xxxxxxxxxxxxxxx] On Behalf Of Koen Kooi > > > Sent: Monday, May 10, 2010 3:03 AM > > > To: Guruswamy, Senthilvadivu > > > Cc: linux-omap@xxxxxxxxxxxxxxx; > linux-fbdev-devel@xxxxxxxxxxxxxxxxxxxxx; > > > tony@xxxxxxxxxxx; tomi.valkeinen@xxxxxxxxx; 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: > > > > > > > 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. > > > > 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. [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.��.n��������+%������w��{.n�����{�������ܨ}���Ơz�j:+v�����w����ޙ��&�)ߡ�a����z�ޗ���ݢj��w�f
