From: Tony Lindgren <tony@atomide.com>
To: Nishanth Menon <nm@ti.com>
Cc: Nishanth Menon <menon.nishanth@gmail.com>,
"Guruswamy, Senthilvadivu" <svadivu@ti.com>,
Koen Kooi <koen@dominion.thruhere.net>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"tomi.valkeinen@nokia.com" <tomi.valkeinen@nokia.com>,
"Hiremath, Vaibhav" <hvaibhav@ti.com>,
"linux-fbdev@vger.kernel.org" <linux-fbdev@vger.kernel.org>
Subject: Re: [PATCH] DSS2 Include VRFB into omap2-3build only
Date: Mon, 10 May 2010 17:14:43 +0000 [thread overview]
Message-ID: <20100510171443.GE16460@atomide.com> (raw)
In-Reply-To: <4BE8063B.1080709@ti.com>
* Nishanth Menon <nm@ti.com> [100510 06:07]:
> On 05/10/2010 06:24 AM, Nishanth Menon wrote:
> >On 05/10/2010 03:26 AM, Guruswamy, Senthilvadivu wrote:
> >>Tiler support is not yet in OMAP builds. So multi-omap build will NOT break, but would exclude VRFB feature in the build.
> >in which case, is'nt this patch redundant :) ?
> >
> >joking apart, would'nt a set of function pointers be better - the
> >function pointers could be runtime initialized. the rotational functions
> >for Tiler OR vrfb could be used?
>
> just an addon -> I can see one more potential user of the FEATURES
> framework like dma descriptor feature.. what kind of rotator do we
> have? vrfb Vs tiler..
Guys, let's make one thing clear: We want to make sure things compile
and boot with the omap3_defconfig for all mach-omap2 machines.
This means we must be able to compile in all the drivers (and panels)
without breaking other configurations. This is the standard Linux
behaviour. Any patches that break this will not get merged.
Also, please follow the mailing list etiquette, no more top posting:
http://www.elinux.org/Netiquette
Regards,
Tony
next prev parent reply other threads:[~2010-05-10 17:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-10 6:48 [PATCH] DSS2 Include VRFB into omap2-3build only Senthilvadivu Guruswamy
2010-05-10 7:39 ` Koen Kooi
2010-05-10 8:01 ` Guruswamy, Senthilvadivu
2010-05-10 8:03 ` Koen Kooi
2010-05-10 8:38 ` Guruswamy, Senthilvadivu
2010-05-10 11:24 ` Nishanth Menon
2010-05-10 13:12 ` Nishanth Menon
2010-05-10 17:14 ` Tony Lindgren [this message]
2010-06-18 16:57 ` Aguirre, Sergio
2010-06-21 8:38 ` Tomi Valkeinen
2010-06-21 8:50 ` Guruswamy, Senthilvadivu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100510171443.GE16460@atomide.com \
--to=tony@atomide.com \
--cc=hvaibhav@ti.com \
--cc=koen@dominion.thruhere.net \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=menon.nishanth@gmail.com \
--cc=nm@ti.com \
--cc=svadivu@ti.com \
--cc=tomi.valkeinen@nokia.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).