linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Vrabel <dvrabel@arcom.com>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: [patch] Framebuffer kbuild -- add options for building software ops (0/4)
Date: Tue, 15 Feb 2005 10:45:51 +0000	[thread overview]
Message-ID: <4211D2DF.2070302@arcom.com> (raw)
In-Reply-To: <Pine.LNX.4.56.0502141724240.6781@pentafluge.infradead.org>

James Simmons wrote:
>>>1/2 -- add the FB_SOFTWARE_CFB_OPS option to Kconfig and Makefile
>>>2/2 -- make all drivers (where appropriate) select FB_SOFTWARE_CFB_OPS
>>
>>But I'd prefer to have 3 separate options, since some drivers don't need all 3
>>of them, e.g.:
>>  - CONFIG_CFB_FILLRECT
>>  - CONFIG_CFB_COPYAREA
>>  - CONFIG_CFB_IMAGEBLT
> 
> We should have CONFIG_SOFT_CURSOR for the sotftware cursor, softcursor.c, as 
> well. David could you add that as well? 

Done. Even though it seems of little use.  It seems only two drivers
don't use soft_cursor (rivafb and intelfb).

A new set of four patches to follow.

1/4 -- add FB_CFB_xxx options to framebuffer Kconfig and Makefile
2/4 -- make all framebuffer drivers (where appropriate) select FB_CFB_xxx
3/4 -- add FB_SOFT_CURSOR options to framebuffer Kconfig and Makefile
4/4 -- make all framebuffer drivers (where appropriate) select
FB_SOFT_CURSOR.

David Vrabel
-- 
David Vrabel, Design Engineer

Arcom, Clifton Road           Tel: +44 (0)1223 411200 ext. 3233
Cambridge CB1 7EA, UK         Web: http://www.arcom.com/


-------------------------------------------------------
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

  reply	other threads:[~2005-02-15 10:45 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     ` David Vrabel [this message]
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 ` [patch] Framebuffer kbuild -- add FB_SOFTWARE_CFB_OPS for building cfb*.o (1/2) David Vrabel
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=4211D2DF.2070302@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).