From: "Gabriel Díaz" <gdiaz@rejaa.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] ctrl radeon: not working for ATI Radeon 9600 Mobility?
Date: Fri, 30 Apr 2010 05:30:15 -0700 [thread overview]
Message-ID: <589116.91988.qm@web1202.biz.mail.gq1.yahoo.com> (raw)
In-Reply-To: <cbdd776d81705893e47ed49a41671e1c@kw.quanstro.net>
hello
Vesa code has some problems to deal with ati hd5750 cards here. Themouse cursor disappear when a lot of scrolling is happening, vesa is unable to drive the card beyond 8bit depth modes or 1280x1024 resolutions. Besides that, the performance i see is almost the same i had with the radeon driver and the 9500 i had in the thinkpad, or the intel driver (given that my stress test is reading man pages and watching flickr photos. . . .)
I guess the radeon driver is unable to work with modern ati cards no?
I would love a book recommendation to learn something about graphics programming, so at least i can guess what or where to look to try to debug the problem.
slds.
gabi
----- Original Message ----
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Sent: Fri, April 30, 2010 2:07:07 PM
Subject: Re: [9fans] ctrl radeon: not working for ATI Radeon 9600 Mobility?
> I was curious to see how performance differs from vesa.
me, too. radeon performance is not good with vesa.
> 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?
cpu speed seems to have little to do with it. the main slowdown
is reading from the hardware framebuffer, which plan 9 does a lot.
on many modern cards there is no phsical framebuffer. it's
constructed by firmware (perhaps running in smm mode on the
cpu) on-the-fly.
> 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.
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. i'd love to have my nvidia mx400
back with a pcie interface.
- erik
next prev parent reply other threads:[~2010-04-30 12:30 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 [this message]
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=589116.91988.qm@web1202.biz.mail.gq1.yahoo.com \
--to=gdiaz@rejaa.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).