From: Manjunath Hadli <manjunath.hadli@ti.com>
To: linux-fbdev@vger.kernel.org
Subject: [RFC PATCH 3/3] davinci: vpbe: add build infrastructure for fbdev driver
Date: Mon, 26 Sep 2011 13:47:09 +0000 [thread overview]
Message-ID: <1317044109-7429-4-git-send-email-manjunath.hadli@ti.com> (raw)
add Kconfig and Makefile changes to build the fbdev driver
Signed-off-by: Manjunath Hadli <manjunath.hadli@ti.com>
---
drivers/media/video/davinci/Kconfig | 13 +++++++++++++
drivers/media/video/davinci/Makefile | 1 +
2 files changed, 14 insertions(+), 0 deletions(-)
diff --git a/drivers/media/video/davinci/Kconfig b/drivers/media/video/davinci/Kconfig
index a7f11e7..0ea27b8 100644
--- a/drivers/media/video/davinci/Kconfig
+++ b/drivers/media/video/davinci/Kconfig
@@ -113,3 +113,16 @@ config VIDEO_VPBE_DISPLAY
To compile this driver as a module, choose M here: the
module will be called vpbe_display.
+
+config VIDEO_VPBE_FB
+ tristate "VPBE Framebuffer driver"
+ depends on FB && ARCH_DAVINCI
+ select VIDEO_DMXXX_VPBE
+ select FB_CFB_FILLRECT
+ select FB_CFB_COPYAREA
+ select FB_CFB_IMAGEBLIT
+ default y
+ help
+ Enables VPBE Framebuffer driver on a DMXXX device
+ To compile this driver as a module, choose M here: the
+ module will be called vpbe_fb.
diff --git a/drivers/media/video/davinci/Makefile b/drivers/media/video/davinci/Makefile
index ae7dafb..da4a5b4 100644
--- a/drivers/media/video/davinci/Makefile
+++ b/drivers/media/video/davinci/Makefile
@@ -18,3 +18,4 @@ obj-$(CONFIG_VIDEO_DM355_CCDC) += dm355_ccdc.o
obj-$(CONFIG_VIDEO_ISIF) += isif.o
obj-$(CONFIG_VIDEO_DM644X_VPBE) += vpbe.o vpbe_osd.o vpbe_venc.o
obj-$(CONFIG_VIDEO_VPBE_DISPLAY) += vpbe_display.o
+obj-$(CONFIG_VIDEO_VPBE_FB) += vpbe_fb.o
--
1.6.2.4
reply other threads:[~2011-09-26 13:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1317044109-7429-4-git-send-email-manjunath.hadli@ti.com \
--to=manjunath.hadli@ti.com \
--cc=linux-fbdev@vger.kernel.org \
/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).