Age | Commit message (Collapse) | Author |
|
|
|
This reverts commit b6d40213935da702570eca2c0861bd4b1d7f5254.
This actually breaks gears here on my rv670.
|
|
TRUNC is neither a scalar instruction nor exclusive to the Trans unit.
Signed-off-by: Dave Airlie <airlied@redhat.com>
|
|
Signed-off-by: Dave Airlie <airlied@redhat.com>
|
|
|
|
Make the s3tc upload code more generic.
Signed-off-by: Dave Airlie <airlied@redhat.com>
|
|
This adds EXT_texture_array support to r600g, it passes the piglit
array-texture test but I suspect may not be complete.
It currently requires a kernel patch to fix the CS checker to allow
these, so you need to use R600_ARRAY_TEXTURE=true for now
to enable them.
Signed-off-by: Dave Airlie <airlied@redhat.com>
|
|
The spec says that the offsets in the vertex-fetch instructions need to be byte-aligned and makes no specification with regard to the required alignment of the offset and stride in the vertex resource constant register.
However, testing indicates that all three values need to be DWORD aligned.
|
|
when the cs checker fixes go upstream a lot of this can disappear
into a drm version check.
Signed-off-by: Dave Airlie <airlied@redhat.com>
|
|
the current clause
Signed-off-by: Dave Airlie <airlied@redhat.com>
|
|
Signed-off-by: Dave Airlie <airlied@redhat.com>
|
|
this doesn't do anything much since the rest of mesa doesn't
support RGTC yet.
|
|
Some cards don't appear to work correctly with the UNORM type,
so switch to the integer type, however since gallium has no
integer types yet from what I can see we need to do a hack to
workaround it for the blitter.
Signed-off-by: Dave Airlie <airlied@redhat.com>
|
|
|
|
pointed out by Marek on irc.
|
|
this fixes the piglit mipmap generation sRGB on my rv730.
Signed-off-by: Dave Airlie <airlied@redhat.com>
|
|
this fixes piglit fbo-generatemipmap-formats on my rv730.
Signed-off-by: Dave Airlie <airlied@redhat.com>
|
|
we need to translate the destination box as well.
fixes piglit's s3tc-texsubimage test.
Signed-off-by: Dave Airlie <airlied@redhat.com>
|
|
|
|
|
|
I typod this when copy-pasting.
|
|
On r600, s3tc formats require a 1D tiled texture format,
so we have to do uploads using a blit, via the 64-bit and 128-bit formats
Based on the r600c code we use a 64 and 128-bit type to do the
blits.
Still requires R600_ENABLE_S3TC until the kernel fixes are in,
this has only been tested on evergreen where the kernel doesn't
yet get in the way.
|
|
the miptree setup and pitch storing didn't work so well for block
based things like compressed textures. The CB takes blocks, where
the texture sampler takes pixels, and transfers need bytes,
So now we store blocks/bytes and translate to pixels in the sampler.
This is necessary for s3tc to work properly.
|
|
we can work this out from the array_mode and it makes more sense
to do that.
Signed-off-by: Dave Airlie <airlied@redhat.com>
|
|
Also implement the redefine_user_buffer hook in the drivers.
|
|
Matches the drm and ddx.
Signed-off-by: Alex Deucher <alexdeucher@gmail.com>
|
|
Because we only translate a subrange of the buffer.
|
|
useful for s3tc
|
|
these were NOPs anyways.
Signed-off-by: Dave Airlie <airlied@redhat.com>
|
|
add support for the 32-bit types, also fixup the
export setting to handle types with channels > 11 bits properly
Signed-off-by: Dave Airlie <airlied@redhat.com>
|
|
|
|
u_default_transfer_inline_write uses util_copy_rect, which is kinda slow.
|
|
|
|
This should reduce memory consumption.
|
|
|
|
|
|
This reverts commit 1c2a4f0820ff2272f993e6da28dcf8bcbbc3252a.
|
|
Relative addressing of constant buffers can't work properly through the
kcache, since you can only address within the currently locked kcache window.
Instead, this patch binds the constant buffer as a shader resource, and then
explicitly fetches the constant using a vertex fetch with fetch type
VTX_FETCH_NO_INDEX_OFFSET from the shader. There's probably still some room
for improvement, doing the fetch right before the instruction that needs the
value may not be quite optimal for example.
|
|
|
|
|
|
This allows them to be used for VS or PS buffer resources as well.
|
|
These are practically unused, only the vs_resource array is being abused for
fetch shader resources.
|
|
|
|
r600_shader_from_tgsi().
|
|
The r600_bc_alu_src structure is used in two different ways, as a vector and
for the individual channels of that same vector. This is somewhat fragile,
and probably confusing.
|
|
This is much easier to work with, and allows use to get rid of some of the
literal handling hacks.
|
|
|
|
|
|
|
|
|