Age | Commit message (Collapse) | Author |
|
This has some advantages over the traditional way of first waiting for the
target vertical blank and then emitting the buffer swap, e.g.
* glXSwapBuffers returns immediately, only the next time the driver needs the
hardware lock will it block until the target vertical blank. This should
allow applications that don't intermix rendering and other processing to
start processing for the next frame right away.
* It's less likely to produce tearing.
|
|
This can be used by drivers to determine the current swap interval of a
drawable.
|
|
|
|
Also some minor fixes for detecting when the deadline is met or missed, in
particular wrt wraparounds of the sequence number.
|
|
This prevents the first wait for vertical blank from timing out when the X
server has been running for a long time.
|
|
Remove r200 dependency from the code as r200 merged
driver never worked (right ?) and we want to clean
the code.
|
|
Remove r200*.h files dependency.
|
|
|
|
|
|
|
|
defined to some default value by the spec (fogcoord yzw, normal w, secondary color w), by replacing those components with zero/one respectively using swizzling.
|
|
|
|
|
|
|
|
miptree object.
|
|
mesa's texstore functions whenever possible for r200 and r300. r200 can use hw formats argb8888, rgba8888 and abgr8888 (or the opposite on big endian), r300 can use argb8888, bgra8888, rgba8888 and abgr8888 regardless of endian, as it supports free component swizzling.
|
|
blits and the different ways of specifying a blit on this hardware.
|
|
|
|
|
|
(GL_OBJECT_LINEAR, GL_EYE_LINEAR). This is a chip limitation, try to hack it up regardless or use a tcl fallback in some cases. Might still produce wrong results if fixed up, but so far this corrects celestia ring shadows (in multitexture mode), doom3 (arb renderer), quake4 (arb renderer and some less visible bugs in r200 renderer), and even the remaining texgenmix broken case (this is pure luck though, it is easy to construct artifical cases where it will break).
|
|
|
|
identify context switches between members of a share group -
ie. multiple contexts in a single application, possibly on different
threads. In this case the contexts share a bufmgr instance and there
is no need to evict textures - so don't.
2) Use a new flag 'need_flush' to ensure hardware rendering is flushed
prior to starting a software fallback.
|
|
|
|
|
|
|
|
|
|
|
|
function.
|
|
|
|
specifically {8,16,32}.
|
|
faster memcopy path in mesa (at least on little endian systems, possibly on big endian too)
|
|
ensures texture cache gets flushed in case the new texture has the same offset as the old one (fixes glean pixelFormat test at least on r200).
|
|
we call the blend/logic op functions. Fixes glean logicOp test on r200.
|
|
is not enabled (?). This fixes demos/cubemap as well as glean texCube test.
|
|
|
|
|
|
|
|
and fixing a couple of warning. More cleanup and shuffle
to come. I have tested this change they might broke things
especialy with r300_texstate.c change (format_x doesn't
seems to be use at all by r300).
|
|
|
|
between the vertex cache, the vertex shader and the clipping stages,
all of which are competitors for URB entries assigned to the VS unit.
This change reduces the maximum number of clip and VS threads by
enough to ensure that they cannot consume all the available URB
entries, and then reduces the number somewhat more up to an arbitary
amount I discovered by trial and error. Unfortunately trial and error
solutions don't inspire total confidence...
|
|
|
|
|
|
|
|
targets (swtcl tex coord translation stage, tcl tex matrix adaption) and use the chip's native handling of such coords instead (!!!). Seems noone noticed those bits in the se_coord_fmt reg, even though it works fairly similar to r200 (except it's set per-unit and always active, so only enable it for texture rectangles).
|
|
conversion appears only to work on first unit.
|
|
hack to the drm to disable command verification on the cmd_buffer
ioctl. Doesn't exactly replay as commands are normally delivered as
batchbuffers but are captured and replayed as commands on the ring.
|
|
drivers, otherwise we'll mix up tcl and vtxfmt path for some reason. This fixes a warzone2100 asssertion failure.
|
|
Get aubfile generation working again.
|
|
rendering operations to take place after evicting all resident
buffers.
Cope better with memory allocation failures throughout the driver and
improve tracking of failures.
|
|
|