| Age | Commit message (Collapse) | Author |
|---|
|
|
|
passing them to the kernel. This works because all drawing commands
in the 965 driver are emitted with the lock held and the batchbuffer
is always flushed prior to releasing the lock. This allows multiple
cliprects to be dealt with, without replaying entire batchbuffers and
redundantly re-emitting state.
|
|
default/fallback functions are already plugged in by the call to
_mesa_init_driver_functions().
|
|
like 'fire' that display a help message or fps number this way.
|
|
|
|
|
|
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.
|
|
|
|
rendering operations to take place after evicting all resident
buffers.
Cope better with memory allocation failures throughout the driver and
improve tracking of failures.
|
|
we render. Currenly requires that some state be re-examined after
every LOCK_HARDWARE().
|
|
glean, and we no longer need to export it to keep Mesa happy as we did
at one time.
|
|
This driver comes from Tungsten Graphics, with a few further modifications by
Intel.
|
