From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: David Eger <eger@havoc.gtf.org>
Cc: Linux Fbdev development list <linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: [PATCH] radeonfb: make pan and copyarea() play nice
Date: Fri, 04 Jun 2004 14:12:00 +1000 [thread overview]
Message-ID: <1086322320.1876.64.camel@gaston> (raw)
In-Reply-To: <20040604022838.GB4175@havoc.gtf.org>
On Fri, 2004-06-04 at 12:28, David Eger wrote:
> Dear Ben,
>
> Please apply this to radeon with the previous fb accel capabilities patch
> I sent you. This patch solves a couple of screen garbage issues I saw when
> trying to use both panning and copyarea()/fillrect().
>
> For some reason, I've got to sync() the engine after each copyarea()/
> fillrect() call. I don't know why this should be, but when I do, the
> corruption goes away...
Hrm... that isn't normal. Have you dbl checked that the fifo space
required by all other operations is correct ? Tried increasing it a bit
? One possibility is something tapping video memory without requesting a
sync first ... maybe the cursor code still has some breakage there...
Ben.
-------------------------------------------------------
This SF.Net email is sponsored by the new InstallShield X.
From Windows to Linux, servers to mobile, InstallShield X is the one
installation-authoring solution that does it all. Learn more and
evaluate today! http://www.installshield.com/Dev2Dev/0504
prev parent reply other threads:[~2004-06-04 4:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-04 2:28 [PATCH] radeonfb: make pan and copyarea() play nice David Eger
2004-06-04 4:12 ` Benjamin Herrenschmidt [this message]
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=1086322320.1876.64.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=eger@havoc.gtf.org \
--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).