| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
This was a regression in 59b2c2adbbece27ccf54e58b598ea29cb3a5aa85 that broke
blender, among other apps.
|
| |
|
|
|
|
|
|
| |
As far as I can read in the docs, VS threads can be 1:1 with the pairs of
VUE handles allocated for them. Also, G4X can run twice as many threads as
before (though we won't unless the we bump the preferred URB entries for VS).
|
|
|
|
|
|
| |
We were dividing the number of URB entries by two to get number of threads,
which looks suspiciously like a copy'n'paste-o from brw_vs_state.c. Also, the
maximum number of threads is 24, not 12.
|
|
|
|
|
|
|
|
|
| |
The clip thread could potentially deadlock when processing tristrips since
being moved back to dual-thread mode, as the two threads could each have 4 VUEs
referenced and not be able to allocate another one since SF processing
wasn't able to continue (needing 5 entries before it freed 2).
In constrained URB mode, similar deadlock could even have occurred with
polygons (so we cut back max_threads if we can't handle it any primitive type).
|
| |
|
|
|
|
|
| |
It shouldn't offer anything new over what's in the docs (except for G4X notes),
but here it's all in one place.
|
|
|
|
| |
Trunc is a more accurate description; there's no type conversion involved.
|
|
|
|
|
|
| |
Now i965 also uses the vertex program created by Mesa Core, but this vertex program
is not only depend on mesa state _NEW_PROGRAM, so always check the current vertex
program is updated or not. This fixes broken demo cubemap.
|
|
|
|
| |
OPCODE_NOISE4 coming later.
|
| |
|
|
|
|
| |
This cuts one MOV out when setting a zero header.
|
|
|
|
|
| |
The mobile and desktop chipsets are the same, and having them separate is
more typing and more chances to screw up.
|
|
|
|
| |
Also, add a comment explaining what brw->urb.constrained tries to do.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Quoting section 11.3.10, paragraph 10.2 of the 965PRM:
10.2. If ExecSize is 1, dst.HorzStride must not be 0. Note that this is
relaxed from rule 10.1.2. Also note that this rule for destination
horizontal stride is different from that for source as stated in
rule #7.
GM45 gets very angry when rule 10.2 is violated.
Patch 58dc8b7 (i965: support destination horiz strides in align1 access mode)
added support for additional horizontal strides in the ExecSize 1 case, but
failed to notice that mesa occasionally re-purposes a register as a
temporary destination, even though it was constructed as a repeating source
with HorzStride = 0.
While, ideally, we should probably fix the code using these register
specifications, this patch simply rewrites them to use HorzStride 1 as the
pre-58dc8b7 code did.
Signed-off-by: Keith Packard <[email protected]>
|
|
|
|
| |
(Only in fragment shaders, so far. Support for NOISE3 and NOISE4 to come.)
|
|
|
|
| |
This is required for scatter writes in destination regions to work.
|
|
|
|
|
|
|
|
| |
Previously, since my check_aperture API change, we would check each piece of
state against the batchbuffer individually, but not all the state against the
batchbuffer at once. In addition to not being terribly useful in assuring
success, it probably also increased CPU load by calling check_aperture many
times per primitive.
|
|
|
|
|
|
|
| |
This avoids issues with dereferencing stale cliprects around intel_draw_buffer
time. Additionally, take advantage of cliprects staying constant for FBOs and
DRI2, and emit cliprects in the batchbuffer instead of having to flush batch
each time they change.
|
|
|
|
|
| |
This is required for threads to be spawned with correctly sized GRF
register blocks.
|
| |
|
| |
|
|
|
|
| |
This ensures there is an unfilled batchbuffer used for emitting states again. Partial fix for #17964.
|
| |
|
|
|
|
|
| |
The fallback was introduced to fix bug #16697, but made the test it was
fixing run excessively long.
|
| |
|
| |
|
| |
|
|
|
|
| |
See volume 4, SAMPLER_BORDER_COLOR_STATE programming notes.
|
|
|
|
| |
Fixes black borders around windows in compiz. Bug #17233.
|
|
|
|
|
|
|
|
| |
The i965 driver previously had it's own set of code to convert
fixed-function TNL state to a vertex program. Core Mesa has code to
do this, so there is no reason to duplicate that effort in the driver.
In fact, this duplication leads to bugs when other aspects of the Mesa
infrastructure change.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
This isn't required for GEM (at least, yet), but the check_aperture code
for non-GEM results in batch getting flushed during emit. brw_state_upload
restarts state emits, but a bunch of the state emit functions were assuming
that they would be called exactly once, after prepare and before new_batch.
Bug #17179.
|
|
|
|
| |
This fixes bugzilla #17718.
|
|
|
|
| |
Found By: Tinderbox
|
|
|
|
| |
Makefile.template
|
| |
|
| |
|
| |
|
|
|
|
| |
(Reverts a change to work around the problem on 965).
|
| |
|
|
|
|
|
|
| |
A thread switch is implicitly invoked after the issuance of an IF/ELSE/ENDIF
instruction if necessary. Unfortunately it seems sometimes a forced thread
switch is needed.
|
| |
|
| |
|
|
|
|
| |
This reverts commit 7c81124d7c4a4d1da9f48cbf7e82ab1a3a970a7a.
|
|
|
|
|
|
|
|
| |
This reverts commit 53675e5c05c0598b7ea206d5c27dbcae786a2c03.
Conflicts:
src/mesa/drivers/dri/i965/brw_wm_surface_state.c
|
|
|
|
|
| |
Fix incorrect backface culling for OGL tunnel in wireframe and
point mode.
|
|
|
|
| |
Patch is correctly applied this time.
|