Re: [Mesa-dev] ARB_texture_buffer_range offsets

2014-11-06 Thread Roland Scheidegger
But even dword offsets aren't translatable right now to pipe_sampler_view first_elements if the format has more than 32 bits. Roland Am 06.11.2014 um 18:21 schrieb Marek Olšák: > For radeonsi, I think only x8, x8y8, and x16 fetches can be > byte-aligned. Everything else is dword-aligned (the 2 lo

Re: [Mesa-dev] ARB_texture_buffer_range offsets

2014-11-06 Thread Marek Olšák
For radeonsi, I think only x8, x8y8, and x16 fetches can be byte-aligned. Everything else is dword-aligned (the 2 lowest bits are ignored). I guess the cap should be 4 then. Marek On Thu, Nov 6, 2014 at 4:55 PM, Roland Scheidegger wrote: > Am 06.11.2014 um 16:15 schrieb Marek Olšák: >> I'd say i

Re: [Mesa-dev] ARB_texture_buffer_range offsets

2014-11-06 Thread Roland Scheidegger
Am 06.11.2014 um 16:15 schrieb Marek Olšák: > I'd say it's a spec bug. ARB_texture_buffer_range should say that the > offset should be a multiple of an element size, but it doesn't. The > question is, what should the element size be? One component or the > whole pixel? Imho whole pixel (for block c

Re: [Mesa-dev] ARB_texture_buffer_range offsets

2014-11-06 Thread Marek Olšák
I'd say it's a spec bug. ARB_texture_buffer_range should say that the offset should be a multiple of an element size, but it doesn't. The question is, what should the element size be? One component or the whole pixel? Marek On Wed, Nov 5, 2014 at 9:08 PM, Roland Scheidegger wrote: > Trying to fi

[Mesa-dev] ARB_texture_buffer_range offsets

2014-11-05 Thread Roland Scheidegger
Trying to fix some bug due to alignment issues in llvmpipe's vertex fetch, I came across some issue with ARB_texture_buffer_range. Namely, it looks like the offsets specified there are always in bytes, regardless the actual format (hence, as long as the TEXTURE_BUFFER_OFFSET_ALIGNMENT is 1, it woul