From: Thomas Winischhofer <thomas@winischhofer.net>
To: David Eger <eger@theboonies.us>
Cc: adaplas@pol.net, David Eger <eger@havoc.gtf.org>,
Andrew Morton <akpm@osdl.org>,
linux-fbdev-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [Linux-fbdev-devel] [PATCH] fb accel capabilities (resend against 2.6.7-rc2)
Date: Thu, 03 Jun 2004 22:46:08 +0200 [thread overview]
Message-ID: <40BF8E10.5020107@winischhofer.net> (raw)
In-Reply-To: <1086285678.40bf676e1da4d@mail.theboonies.us>
David Eger wrote:
> I coded your pseudocode up, and I'm convinced now that you and Thomas are right.
> We should prefer panning when it's available
> cat /usr/src/linux/MAINTAINERS is 0.3 seconds instead of 1.5 seconds.
>
> On the down side, panning makes screen corruption for me... time to investigate
> to see if fbcon or radeonfb is to blame... perhaps panning is just incompatible
> with accel engine at all in radeon...
Sisfb has been using panning for ages and I never saw or heard about
screen corruption. Looks very much like the radeon driver is skrewed...
However, I don't think the engine is "incompatible" with panning.
Panning means just to change the display start address, I can't imaging
that the engine would care about that.
What sort of "screen corruption" do you get?
Thomas
--
Thomas Winischhofer
Vienna/Austria
thomas AT winischhofer DOT net http://www.winischhofer.net/
twini AT xfree86 DOT org
next prev parent reply other threads:[~2004-06-03 20:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-03 2:36 [PATCH] fb accel capabilities (resend against 2.6.7-rc2) David Eger
2004-06-03 15:07 ` Antonino A. Daplas
2004-06-03 18:01 ` [Linux-fbdev-devel] " David Eger
2004-06-03 20:46 ` Thomas Winischhofer [this message]
2004-06-04 1:26 ` David Eger
2004-06-04 0:06 ` Antonino A. Daplas
2004-06-04 2:24 ` [PATCH] fbcon: prefer pan when available David Eger
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=40BF8E10.5020107@winischhofer.net \
--to=thomas@winischhofer.net \
--cc=adaplas@pol.net \
--cc=akpm@osdl.org \
--cc=eger@havoc.gtf.org \
--cc=eger@theboonies.us \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@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).