Mailinglist Archive: radeonhd (352 mails)

["Alex Deucher" <alexdeucher@xxxxxxxxx>]

On Thu, Apr 10, 2008 at 1:38 AM, Florian Echtler <floe@xxxxxxxxxxxxxx> wrote:
> Hello everybody,
>
>  please forgive me for posting a fglrx-related question on this list, but I
> have been unable to find answers anywhere else.. and at least to a certain
> degree, it's also related to the recently-posted ATI documentation.
>
>  I'm currently rewriting an older GPGPU application to be nicely standards-
> compliant so that it runs on ATI,Nvidia and Mac,Win,Linux. A lofty goal, to
> be sure.. :-) Anyway, I'm having problems with the ATI-Linux combination.
> Lacking an alternative, I'm using fglrx (side question: is there a guess
> possible as to when radeonhd will support stuff such as textures, FBOs,
> shaders, VBOs..?).

These will be supported in the r300 mesa driver as they are 3D
related.  Dave has an r500-test branch, but about all it supports at
the moment is gears.

>  The core problem now is that the card obviously has a hard time deciding
> whether an internal buffer is RGBA or BRGA (integer and floating point
> alike). This even seems to flip sometimes after buffer initialization, e.g.
> when using the buffer as a FBO render target. Can somebody give me pointers
> into the newly-released R400 and R500 specs on internal buffer formats, or
> give me some general hints?

There's no detection, you have to explicitly choose the formats and
swizzling.  The render target formats are controlled by the
colorbuffer regsiters (CB, RB3D in the documentation).  For shaders
and textures the hw can do arbitrary swizzling of components.  For
more information see the TX (texture) and US (fragment shader)
documentation in the r3xx and r5xx documents.

Alex
-- 
To unsubscribe, e-mail: radeonhd+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: radeonhd+help@xxxxxxxxxxxx