From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] ctrl radeon: not working for ATI Radeon 9600 Mobility?
Date: Sat, 1 May 2010 10:08:12 -0400 [thread overview]
Message-ID: <44c6dddc491d4dead1518fcd7e7de7cd@brasstown.quanstro.net> (raw)
In-Reply-To: <x2qf75780241005010653uf164703bxea0fa70d26b9231f@mail.gmail.com>
> erik quanstrom wrote:
> > i think it's mainly a question of getting the best graphics
> > performance. but these days the 2d accelleration (especially
> > for radeon) is fairly poor.
>
> Do you happen to have any workloads where this is a problem? There is
> a lot more we can do for the radeon, particularly the r100-r300 chips,
> which could improve draw performance.
i didn't make it clear that i'm using the vesa
interface. and it's very slow for every day
use with acme, but it sure displays pictures quickly.
; pci | grep vid | grep 1002
1.5.0: vid 03.00.00 1002/791e 10 0:d800000c 134217728 1:00000000 16 2:fbff0004 65536 3:00000000 16 4:0000a001 256 5:fbe00000 1048576
; pci 1002/791e
1002/791e
ATI Technologies Inc RS690 [Radeon X1200 Series]
> To ask the radeon gpu to do anything interesting for you, you must
> carry out a series of register writes - for example, to fill a
> rectangle with a solid color, you write the rectangle's color to
> DP_BRUSH_FGRD_CLR (register 0x147c), the start to DST_X_Y, and the
> width and height to DST_WIDTH_HEIGHT. Everything you can ask the
> radeon to do is ultimately done via register writes.
i wonder if this pio doesn't explain a lot of the slowness.
i would have thought that they would have used a ring.
i hope you don't also pio the image data in?
- erik
next prev parent reply other threads:[~2010-05-01 14:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <d7a540d6-2751-4e30-8766-e3511bb8c202@g11g2000yqe.googlegroups.co>
2010-04-26 13:15 ` erik quanstrom
2010-04-29 9:58 ` Anton.Pavlovetsky
[not found] ` <7caa7a0a-fb6d-4ffa-81ef-ad3256100f2c@g21g2000yqk.googlegroups.co>
2010-04-29 11:17 ` erik quanstrom
2010-04-29 12:44 ` Venkatesh Srinivas
2010-04-30 8:53 ` Anton.Pavlovetsky
2010-04-30 8:53 ` Anton.Pavlovetsky
[not found] ` <9e5fc5ec-43d5-4cf3-be92-3fc8c4829ba0@l32g2000yqm.googlegroups.co>
2010-04-30 12:07 ` erik quanstrom
2010-04-30 12:30 ` Gabriel Díaz
2010-05-01 13:53 ` Venkatesh Srinivas
2010-05-01 14:08 ` erik quanstrom [this message]
2010-05-01 19:05 ` Venkatesh Srinivas
2010-05-01 22:48 ` Venkatesh Srinivas
2010-05-02 0:42 ` erik quanstrom
2010-05-04 8:47 ` Anton.Pavlovetsky
2010-04-26 11:17 Anton.Pavlovetsky
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=44c6dddc491d4dead1518fcd7e7de7cd@brasstown.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.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).