On 02/17/2011 09:58 PM, Dave Airlie wrote:
From: Dave Airlie
This is because the HW doesn't always store a 1D array like a
2D texture, it more likely stores it like 2D texture (i.e.
alignments etc).
This means we upload each slice separately and let the driver
work out where to put it.
Signed-
1D array like a 2D texture, it more likely stores it like 2D texture
That's "2D texture" twice :)
Maarten.
On Fri, Feb 18, 2011 at 1:02 PM, Dave Airlie wrote:
>> This is because the HW doesn't always store a 1D array like a
>> 2D texture, it more likely stores it like 2D texture (i.e.
>> alignm
> This is because the HW doesn't always store a 1D array like a
> 2D texture, it more likely stores it like 2D texture (i.e.
> alignments etc).
>
> This means we upload each slice separately and let the driver
> work out where to put it.
Calim pointed out on irc that I missed texsubimage case, I'l
From: Dave Airlie
This is because the HW doesn't always store a 1D array like a
2D texture, it more likely stores it like 2D texture (i.e.
alignments etc).
This means we upload each slice separately and let the driver
work out where to put it.
Signed-off-by: Dave Airlie
---
src/mesa/state_tra
