> 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. _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
