LKML Archive on
help / color / mirror / Atom feed
From: David Eger <>
Cc: Linux Frame Buffer Dev <>,
Subject: FB accel capabilities patch
Date: Wed, 19 May 2004 11:36:21 +0200 (CEST)	[thread overview]
Message-ID: <> (raw)

Dear Andrew,

A month or two ago I noticed that the framebuffer console driver doesn't
know to do proper framebuffer acceleration in Linux 2.6;  I've implemented
a solution Geert suggested where each framebuffer driver advertizes its 
hardware capabilities via fb_info->flags.  Please apply to -mm so I can 
get wider testing.

The patches are at:

The core of these patches is enabling the use of the following flags:

+/* FBIF = FB_Info.Flags */
+#define FBIF_MODULE		0x0001	/* Low-level driver is a module */
+/* hints */
+#define FBIF_PARTIAL_PAN_OK	0x0040 /* otw use pan only for double-buffering */
+#define FBIF_READS_FAST		0x0080 /* soft-copy faster than rendering */
+/* hardware supported ops */
+#define FBIF_HWACCEL_NONE	0x0000
+#define FBIF_HWACCEL_ROTATE	0x0400
+#define FBIF_HWACCEL_XPAN	0x1000
+#define FBIF_HWACCEL_YPAN	0x2000
+#define FBIF_HWACCEL_YWRAP	0x4000

Patches to each individual driver will trickle in as I get to them;
Since these are only hints to the "application" of fbcon, the fact that 
the hints aren't yet accurate for all drivers (default is zero/one depending
on if the fb driver is a module) is OK, and nothing should break with these
patches.  Each driver also doesn't have to reimplement a noaccel flag 
(to disable acceleration, mainly for testing new accel code), since it
will be already in fb_info now ;-)


getting bounce messages from me? let me know and you'll go on my whitelist

             reply	other threads:[~2004-05-19  9:32 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-19  9:36 David Eger [this message]
2004-05-19 10:03 ` Andrew Morton
2004-05-19 11:14   ` [Linux-fbdev-devel] " Geert Uytterhoeven
2004-05-19 23:31   ` Benjamin Herrenschmidt
2004-05-20  8:19     ` [OT ML related] Emiliano 'AlberT' Gabrielli
2004-05-20  8:54       ` Jurriaan
2004-05-20  9:09         ` Emiliano 'AlberT' Gabrielli
2004-05-20  9:20           ` DervishD
2004-05-20  9:23             ` Emiliano 'AlberT' Gabrielli
2004-05-20  9:32               ` Russell King
2004-05-20 15:54   ` [PATCH 1/4] James' fbcon init and con2fb cleanup David Eger
2004-05-20 15:59     ` [PATCH 2/4] FB accel capabilities (core update) David Eger
2004-05-20 16:00     ` [PATCH 1/4] James' fbcon init and con2fb cleanup James Simmons
2004-05-20 16:01     ` [PATCH 3/4] s/FBINFO_FLAG_/FBINFO_/g David Eger
2004-05-20 16:03     ` [PATCH 4/4] radeonfb accel capabilities David Eger
2004-05-19 19:34 ` [Linux-fbdev-devel] FB accel capabilities patch James Simmons
2004-05-19 21:39   ` David Eger
2004-05-19 21:47     ` James Simmons

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \
    --subject='Re: FB accel capabilities patch' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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