From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: David Eger <eger-dated-1080865620.ef4dea@theboonies.us>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Jakub Jelinek <jj@ultra.linux.cz>,
Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: scrollmode, accel_flags, fbcon.c ...
Date: Fri, 26 Mar 2004 13:21:37 +1100 [thread overview]
Message-ID: <1080267697.3068.24.camel@gaston> (raw)
In-Reply-To: <Pine.LNX.4.58.0403260040100.7037@rosencrantz.theboonies.us>
On Fri, 2004-03-26 at 11:14, David Eger wrote:
> are scrollmode or accel_flags meaningful to anyone here?
>
> Paging through fbcon.c, I've realized why the radeonfb driver is still
> slow -- the accelerated functions are never being called!
>
> Hardwiring scrollmode to __SCROLL_YMOVE in updatescrollmode() makes my
> console go a lot faster :)
Heh, good catch ;)
> So within fbcon.c why is there a "scrollmode" variable which can be set
> to: __SCROLL_YWRAP, __SCROLL_YPAN, __SCROLL_YREDRAW, or __SCROLL_YMOVE?
Never been too sure about those. James ?
> Also accel_flags actually useful to anyone? I see in the fb code some
> half-hearted attempts to test for FB_ACCELF_TEXT, but it's not clear at
> all to me where these accel flags are supposed to be set... are they even
> relevant with the new accel interface? It seems all this is properly
> replaced by filling in the fbops to either the driver's custom fillrect()
> or cfb_fillrect(), no?
I think they are irrelevant, I removed most of the stuff using that
in radeonfb, it would not work properly. I'm not sure what to do with
the scrollmode though. I'll have to experiment.
Ben.
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
next prev parent reply other threads:[~2004-03-26 2:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.58.0403081323040.32244@rosencrantz.theboonies.us>
[not found] ` <Pine.GSO.4.58.0403091111540.26626@waterleaf.sonytel.be>
2004-03-26 0:14 ` scrollmode, accel_flags, fbcon.c David Eger
2004-03-26 2:21 ` Benjamin Herrenschmidt [this message]
2004-03-26 7:14 ` Geert Uytterhoeven
2004-03-26 14:42 ` Benjamin Herrenschmidt
2004-03-26 15:03 ` Geert Uytterhoeven
2004-03-27 1:24 ` Benjamin Herrenschmidt
2004-03-28 8:16 ` Geert Uytterhoeven
2004-03-29 17:50 ` James Simmons
2004-03-29 22:35 ` Benjamin Herrenschmidt
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=1080267697.3068.24.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=eger-dated-1080865620.ef4dea@theboonies.us \
--cc=geert@linux-m68k.org \
--cc=jj@ultra.linux.cz \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.