Mailinglist Archive: radeonhd (300 mails)
| < Previous | Next > |
Re: [radeonhd] State of DRI on r5xx
- From: "Alex Deucher" <alexdeucher@xxxxxxxxx>
- Date: Mon, 19 May 2008 11:12:15 -0400
- Message-id: <a728f9f90805190812n27e3982u6504f6fb46bb1cc6@xxxxxxxxxxxxxx>
On 5/19/08, Matthias Hopf <mhopf@xxxxxxx> wrote:
Same driver for r3xx/r4xx/r5xx as most of the hw is the same. We're
just adding new functionality to the r300 driver.
Mostly it's just separated out since the r5xx FP setup and format is
different. There are probably some optimizations for r3xx/r4xx that
could be implemented as well now that we have docs.
Alex
To unsubscribe, e-mail: radeonhd+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: radeonhd+help@xxxxxxxxxxxx
On May 19, 08 09:29:39 -0400, Alex Deucher wrote:
R5xx mesa still has some issues with textures. you can follow the
progress here:
http://cgit.freedesktop.org/mesa/mesa/log/?h=r500-support
and on the IRC logs.
The commit messages state 'r5xx/r500' in the subject line - but as they
still live in the r300 directory, I assume that the driver is still
called "r300", right?
Same driver for r3xx/r4xx/r5xx as most of the hw is the same. We're
just adding new functionality to the r300 driver.
Also I wonder why r500_fragprog.c is almost a complete rewrite of
r300_fragprog.c - while some of the work done there could be helpful for
r300 as well (CMP instead of MAD as MOV replacement) or for r400
(SIN/COS implemented natively).
Mostly it's just separated out since the r5xx FP setup and format is
different. There are probably some optimizations for r3xx/r4xx that
could be implemented as well now that we have docs.
Alex
--
CU
Matthias
--
Matthias Hopf <mhopf@xxxxxxx> __ __ __
Maxfeldstr. 5 / 90409 Nuernberg (_ | | (_ |__ mat@xxxxxxxxx
Phone +49-911-74053-715 __) |_| __) |__ R & D www.mshopf.de
To unsubscribe, e-mail: radeonhd+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: radeonhd+help@xxxxxxxxxxxx
| < Previous | Next > |