From: David Vrabel <dvrabel@arcom.com>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: [patch] Framebuffer kbuild -- add FB_SOFTWARE_CFB_OPS for building cfb*.o (1/2)
Date: Mon, 14 Feb 2005 12:43:22 +0000 [thread overview]
Message-ID: <42109CEA.4050302@arcom.com> (raw)
In-Reply-To: <421096C6.3030105@arcom.com>
Add a FB_SOFTWARE_CFB_OPS option to the framebuffer Kconfig and
Makefile. This enables the building of the cfbfillrect, cfbcopyarea and
cfbimageblt objects.
Signed-off-by: David Vrabel <dvrabel@arcom.com>
Index: linux-2.6-i386/drivers/video/Kconfig
===================================================================
--- linux-2.6-i386.orig/drivers/video/Kconfig 2005-02-14
11:02:39.000000000 +0000
+++ linux-2.6-i386/drivers/video/Kconfig 2005-02-14 11:27:34.506113502 +0000
@@ -38,6 +38,14 @@
(e.g. an accelerated X server) and that are not frame buffer
device-aware may cause unexpected results. If unsure, say N.
+config FB_SOFTWARE_CFB_OPS
+ tristate
+ depends on FB
+ default n
+ ---help---
+ This enables functions for some generic software drawing operations
for drivers
+ which don't provide their own (accelerated) ones.
+
config FB_MODE_HELPERS
bool "Enable Video Mode Handling Helpers"
depends on FB
Index: linux-2.6-i386/drivers/video/Makefile
===================================================================
--- linux-2.6-i386.orig/drivers/video/Makefile 2005-02-14
11:02:39.000000000 +0000
+++ linux-2.6-i386/drivers/video/Makefile 2005-02-14 11:28:49.062987325
+0000
@@ -13,6 +13,8 @@
obj-$(CONFIG_PPC) += macmodes.o
endif
+obj-$(CONFIG_FB_SOFTWARE_CFB_OPS) += cfbfillrect.o cfbcopyarea.o
cfbimgblt.o
+
# Hardware specific drivers go first
obj-$(CONFIG_FB_RETINAZ3) += retz3fb.o
obj-$(CONFIG_FB_AMIGA) += amifb.o c2p.o
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next prev parent reply other threads:[~2005-02-14 12:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-14 12:17 [patch] framebuffer Kconfig -- add option for building cfb*.o (0/2) David Vrabel
2005-02-14 12:23 ` Geert Uytterhoeven
2005-02-14 13:50 ` David Vrabel
2005-02-14 14:04 ` [patch] Framebuffer kbuild -- add FB_CFB_xxx options (1/2) David Vrabel
2005-02-14 14:06 ` Framebuffer kbuild -- make all drivers select FB_CFB_xxx (2/2) David Vrabel
2005-02-14 14:12 ` David Vrabel
2005-02-14 17:25 ` [patch] framebuffer Kconfig -- add option for building cfb*.o (0/2) James Simmons
2005-02-15 10:45 ` [patch] Framebuffer kbuild -- add options for building software ops (0/4) David Vrabel
2005-02-15 10:51 ` Framebuffer kbuild -- add FB_CFB_xxx options (1/4) David Vrabel
2005-02-15 10:53 ` [patch] Framebuffer kbuild -- make all drivers select FB_CFB_xxx (2/4) David Vrabel
2005-02-15 10:54 ` [patch] Framebuffer kbuild -- add FB_SOFT_CURSOR option (3/4) David Vrabel
2005-02-15 10:55 ` [patch] Framebuffer kbuild -- make all drivers select FB_SOFT_CURSOR (4/4) David Vrabel
2005-02-14 12:43 ` David Vrabel [this message]
2005-02-14 12:46 ` [patch] Framebuffer kbuild -- make drivers select FB_SOFTWARE_CFB_OPS (2/2) David Vrabel
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=42109CEA.4050302@arcom.com \
--to=dvrabel@arcom.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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).