From: "Michel Dänzer" <michel@daenzer.net>
To: random <eger-temp_addy-1075244930.6ef584@theboonies.us>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: Re: [PATCH] Radeon 2D Acceleration for 2.6
Date: Fri, 23 Jan 2004 02:22:56 +0100 [thread overview]
Message-ID: <1074820975.367.179.camel@thor.asgaard.local> (raw)
In-Reply-To: <Pine.LNX.4.50L0.0401210008080.16594-100000@rosencrantz.pok.ibm.com>
On Wed, 2004-01-21 at 00:09, random wrote:
>
> +void radeonfb_prim_fillrect(struct radeonfb_info *rinfo,
> + const struct fb_fillrect *region)
> +{
> + radeon_fifo_wait(4);
> +
> + OUTREG(DP_GUI_MASTER_CNTL,
> + rinfo->dp_gui_master_cntl /* contains, like GMC_DST_32BPP */
> + | GMC_BRUSH_SOLID_COLOR
> + | ROP3_P);
> + OUTREG(DP_BRUSH_FRGD_CLR, region->color);
> + OUTREG(DP_WRITE_MSK, 0xffffffff);
You could probably take this out of the acceleration functions, you
don't seem to need a different write mask?
> + OUTREG(DP_CNTL, (DST_X_LEFT_TO_RIGHT | DST_Y_TOP_TO_BOTTOM));
> +
> + radeon_fifo_wait(2);
> + OUTREG(DST_Y_X, (region->dy << 16) | region->dx);
> + OUTREG(DST_WIDTH_HEIGHT, (region->width << 16) | region->height);
> + radeon_engine_idle ();
Why idle the engine in every acceleration function? Doesn't the API
provide a way to only do it when necessary?
PS: You lost my last reply to your private mails to your temporary
address scheme.
--
Earthling Michel Dänzer | Debian (powerpc), X and DRI developer
Libre software enthusiast | http://svcs.affero.net/rm.php?r=daenzer
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
next prev parent reply other threads:[~2004-01-23 1:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-20 14:44 [PATCH] Radeon 2D Acceleration for 2.6 random
2004-01-20 21:40 ` Benjamin Herrenschmidt
2004-01-20 22:47 ` Benjamin Herrenschmidt
2004-01-20 23:09 ` random
2004-01-21 11:10 ` Benjamin Herrenschmidt
2004-01-23 1:22 ` Michel Dänzer [this message]
2004-01-23 2:19 ` 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=1074820975.367.179.camel@thor.asgaard.local \
--to=michel@daenzer.net \
--cc=benh@kernel.crashing.org \
--cc=eger-temp_addy-1075244930.6ef584@theboonies.us \
--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).