From: Senthilvadivu Guruswamy <svadivu@ti.com>
To: linux-omap@vger.kernel.org, linux-fbdev@vger.kernel.org,
tony@atomide.com, tomi.valkeinen@nokia.com, hvaibhav@ti.com
Cc: Senthilvadivu Guruswamy <svadivu@ti.com>
Subject: [PATCH v2 0/2] DSS2:Allow FB to build without VRFB
Date: Thu, 13 May 2010 15:32:26 +0000 [thread overview]
Message-ID: <1273764028-25822-1-git-send-email-svadivu@ti.com> (raw)
From: Senthilvadivu Guruswamy <svadivu@ti.com>
Hi all,
This patch series replaces the patch
"DSS2 Include VRFB into omap2-3build only"
Thanks for the review comments.
The intent of this series is to split the patch into 2 logical
patches and also to incorporate the comments on multi-omap build.
In this series, Kconfig is changed to have
OMAP2_VRFB depend on ARCH_OMAP2 and ARCH_OMAP3.
This change takes care of the multi-omap builds.
This patch would allow successful build of omap_4430sdp_defconfig
when OMAP2_DSS and FB_OMAP2 is enabled from menuconfig.
For verification: Generated the .config on omap3_defconfig with DSS
and FB enabled. Generated .config is same with and without the patch.
List of Changed Files:
arch/arm/plat-omap/include/plat/vrfb.h
drivers/video/omap2/Kconfig
drivers/video/omap2/omapfb/Kconfig
Thanks,
Senthil
next reply other threads:[~2010-05-13 15:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-13 15:32 Senthilvadivu Guruswamy [this message]
2010-05-13 15:32 ` [PATCH v2 1/2] DSS2: Allow FB_OMAP2 to build without VRFB Senthilvadivu Guruswamy
2010-05-13 15:30 ` Nishanth Menon
2010-05-14 5:36 ` Guruswamy, Senthilvadivu
2010-05-13 15:32 ` [PATCH v2 2/2] DSS2: make VRFB depends on OMAP2,3 Senthilvadivu Guruswamy
2010-05-13 16:00 ` [PATCH v2 1/2] DSS2: Allow FB_OMAP2 to build without VRFB Koen Kooi
2010-05-13 16:15 ` Nishanth Menon
2010-05-14 9:40 ` Guruswamy, Senthilvadivu
2010-05-14 5:40 ` Guruswamy, Senthilvadivu
2010-05-14 7:23 ` [PATCH v2 0/2] DSS2:Allow FB " Tomi Valkeinen
2010-05-14 10:15 ` Guruswamy, Senthilvadivu
2010-05-14 10:39 ` Koen Kooi
[not found] ` <1273842100.2814.85.camel@tubuntu.research.nokia.com>
2010-05-17 5:50 ` Guruswamy, Senthilvadivu
2010-06-03 8:43 ` 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=1273764028-25822-1-git-send-email-svadivu@ti.com \
--to=svadivu@ti.com \
--cc=hvaibhav@ti.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=tomi.valkeinen@nokia.com \
--cc=tony@atomide.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).