| Age | Commit message (Collapse) | Author |
|---|
|
I accidentally inverted the condition. :(
Broken since the commit 2579fe4044012a552c8be222ffae76b48de13592.
FDO bug #27851.
|
|
And reserve a little more space just in case.
|
|
libdrm-2.4.20 and earlier include the nouveau/nouveau_class.h header. A
later version of libdrm will not ship this header. Mesa also has this
header at src/gallium/drivers.
The symbol NV34TCL_VTXFMT_TYPE_HALF is needed by nvfx_vbo.c. This symbol
is not in the libdrm copy of the header but is in the Mesa copy of the
header. This patch moves src/gallium/drivers to the beginning of the
include paths such that when building on hosts with libdrm-2.4.20 or
ealier the build uses the copy in Mesa.
|
|
This has caused CS overflow since the commit
671f1e1229877d459cfd76e2cf5ea89c8d881036.
TA3D works here again.
|
|
|
|
An aligned stride is still needed for it to work.
I am slowly approaching the Sauerbraten milestone!
|
|
This allows us to put correct swizzles for undefined components in PSC.
|
|
|
|
we were only running the llvm paths when the input elts were linear,
now we can handle abritrary fetch elts arrays. we do this by generating
two paths - linear and fetch_elts one and just selecting the right one
at run time.
|
|
They cause lockups. The users doesn't seem to like them.
|
|
Though not nice, this is the correct way.
|
|
See also the libdrm commit af98ccf4dd5dcb1b904ec32b9bd1521e6bf7dda5.
|
|
Reviewed-by: Corbin Simpson <MostAwesomeDude@gmail.com>
Signed-off-by: Matt Turner <mattst88@gmail.com>
Signed-off-by: Marek Olšák <maraeo@gmail.com>
|
|
|
|
|
|
|
|
max_index must be observed to prevent crashes due to bad index data.
I've been using this patch for some time without regressions.
Some places, where we use internal vertex buffer, it is not entirely
clear what max_index should be, so passing just ~0 to avoid regressions
for now.
|
|
|
|
Whoo!
|
|
|
|
The POSIX function pthread_cond_wait can have spurious wakeups when
waiting on a condition variable.
Add a 64-bit counter that is incremented whenever the barrier becomes
full. A woken thread checks the counter. If the counter has not changed
then it has been spuriously woken and goes back to sleep. If the counter
has changed then it was properly signaled and exits the barrier.
Tested on Mac OS X.
This patch was based on ideas from Luca Barbieri.
|
|
I just broke the 2000 fps barrier on glxgears. Yay?
|
|
|
|
proc_name cannot be NULL after the switch statement. proc_name is
assigned a value or the function has already returned.
|
|
|
|
|
|
and disable batch splitting on these chipsets.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
commit 0c572c6828b6a338b07a6860280b3a314a81662e replaced
st_manager_create_api with st_gl_api_create.
Fixes MSVC build.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The struct st_module isn't needed as it is the same thing as the st_api
struct. That is they both represent the API. Instead just use a single
function entry point to the the API.
|
|
This allows u_sampler_view_default_dx9_template to do its magic on DX9.
|
|
Everybody should respect max_index, specially llvm generated code, which
likes to eat vertices 4 at a time, so it may end up chew a bit a bit more
than actually exists.
|
|
|
|
Transfer, being now a context operation, should happen in order with
all other contexts operations. If there is rendering pending on the
resource then the driver must flush and potentially wait itself
internally.
Instead of avoiding using transfers internally (as done in llvmpipe) I've
opted to simply pass PIPE_TRANSFER_UNSYNCHRONIZED in all internal
transfers, to avoid infinite recursion.
|
|
Recognize PIPE_TRANSFER_UNSYNCHRONIZED and PIPE_TRANSFER_DONTBLOCK.
|
|
|
|
|
|
Array formats without for channels were being advanced as four channels,
causing buffer overflows.
|
|
The un-optimized path relies on surface_fill which can only handle formats
with depth <= 32, so it is pointless to keep it around.
|
