Am 05.02.2018 um 03:04 schrieb Roland Scheidegger:
> Am 04.02.2018 um 20:13 schrieb Dave Airlie:
>> On 2 February 2018 at 18:02, Roland Scheidegger wrote:
>>> Are you sure of that? You only get 11 stride bits to program, and they
>>> are in bytes. Therefore I can't see how you
Am 04.02.2018 um 20:13 schrieb Dave Airlie:
> On 2 February 2018 at 18:02, Roland Scheidegger wrote:
>> Are you sure of that? You only get 11 stride bits to program, and they
>> are in bytes. Therefore I can't see how you could program 2048 (unless
>> the hw would interpet 0
On 2 February 2018 at 18:02, Roland Scheidegger wrote:
> Are you sure of that? You only get 11 stride bits to program, and they
> are in bytes. Therefore I can't see how you could program 2048 (unless
> the hw would interpet 0 as 2048 but I think stride 0 is valid there?).
>
Are you sure of that? You only get 11 stride bits to program, and they
are in bytes. Therefore I can't see how you could program 2048 (unless
the hw would interpet 0 as 2048 but I think stride 0 is valid there?).
Roland
Am 02.02.2018 um 07:23 schrieb Dave Airlie:
> From: Dave Airlie
From: Dave Airlie
This fixes:
KHR-GL45.limits.max_vertex_attrib_stride
looks like a typo from the first commit.
Signed-off-by: Dave Airlie
---
src/gallium/drivers/r600/r600_pipe.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git