[Mesa-dev] [PATCH 1/4] gallium: add resource normalization flags (v3)

Luca Barbieri luca at luca-barbieri.com
Tue Aug 17 08:01:20 PDT 2010

> Again, I don't see why this needs to be per-resource information --
> surely the hardware has a single preference that it keeps under all
> circumstances?
For nv30 there are two layouts that each require one normalization, so
the "preference" (actually, a requirement) depends on the layout and
hence on the resource.

> Or even if it's more complex than that, it's hard to believe it is so
> random it needs to be handled per-resource.
In general, it is per internal texture layout, but since internal
texture layouts are not exposed, it needs to be per-resource.

I don't think this is a bad thing though at all: the user code is very
simple (just a check of a flag on the resource) and the driver has a
lot of flexibility.

More information about the mesa-dev mailing list