From: "Anton.Pavlovetsky" <pavlovetsky@gmail.com>
To: 9fans@9fans.net
Subject: Re: [9fans] ctrl radeon: not working for ATI Radeon 9600 Mobility?
Date: Fri, 30 Apr 2010 08:53:42 +0000 [thread overview]
Message-ID: <9e5fc5ec-43d5-4cf3-be92-3fc8c4829ba0@l32g2000yqm.googlegroups.com> (raw)
In-Reply-To: <7caa7a0a-fb6d-4ffa-81ef-ad3256100f2c@g21g2000yqk.googlegroups.co>
On Apr 29, 2:23 pm, quans...@quanstro.net (erik quanstrom) wrote:
> the vesa driver works.
I was curious to see how performance differs from vesa. And,
meanwhile, am I right if I think that the whole graphics math is done
on cpu (I mean - not on gpu), so the faster the cpu the better vesa
(and any) driver performance? Proprietary drivers use gpu and many
things built in the graphics controller and so they unload the cpu.
Plan 9 drivers are there to initialize and set up the device, scroll
and fill and this is, basically all, right? If this is so, the brute
force through powerful cpu + vesa is easiest solution, the way to go.
next prev parent reply other threads:[~2010-04-30 8:53 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 [this message]
[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
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=9e5fc5ec-43d5-4cf3-be92-3fc8c4829ba0@l32g2000yqm.googlegroups.com \
--to=pavlovetsky@gmail.com \
--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).