| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
Call the ctx->Driver.ChooseTextureFormat() function from core Mesa's
_mesa_[Copy]TexImage functions instead of in the driver functions.
One less thing for drivers to do.
|
|
|
|
|
|
| |
_ActualFormat is replaced by Format (MESA_FORMAT_x).
ColorEncoding, ComponentType, RedBits, GreenBits, BlueBits, etc. are
all replaced by MESA_FORMAT_x queries.
|
|
|
|
| |
And remove other unneeded #includes while we're at it.
|
|
|
|
| |
Use _mesa_is_format_compressed() instead.
|
|
|
|
|
|
| |
Now gl_texture_image::TexFormat is a simple MESA_FORMAT_x enum.
ctx->Driver.ChooseTexture format also returns a MESA_FORMAT_x.
gl_texture_format will go away next.
|
| |
|
|
|
|
|
| |
I inherited this and really it stayed around far too long,
make it nice and simple.
|
|
|
|
|
|
|
|
| |
There really need to use state emits under kms, otherwise
we end up with some dwords in the command buffer before we've
ever emitted any useful state.
Signed-off-by: Dave Airlie <[email protected]>
|
|
|
|
| |
CS checker found some issues.
|
|
|
|
| |
We need this for the CS bounds checking.
|
|
|
|
| |
Only very few places where realy converted so there isa lot of to do.
|
|
|
|
|
|
|
|
|
|
| |
These function are aiming to make it very simple to add and keep large amount
of debugging code without having runtime impact in relase builds. Basic idea
is to expose simple printf style debugging functions that are inlined.
Level parameter will be evalueted in compile time so compiler can optimise
some of debugging functions out if compile time request for debug level is too
tight.
|
|
|
|
|
|
| |
Problem was to find the correct place to run prediction. Only place that is
called for every primitive is ALLOC_VERTS so we have to do prediction there
before allocation.
|
|
|
|
| |
DRI1 didn't have support for command buffer emit for stripple.
|
| |
|
|
|
|
|
| |
Polygon stipple has to go to command buffer because special ioctl is disabled.
Piglit doesn't like HyperZ warning so disable it for kms.
|
|
|
|
| |
this makes gnome-shell work on r300 for me
|
|
|
|
|
| |
Swtcl calls flush everytime primitive changes so prediction has to made again
after flushing.
|
|
|
|
|
| |
We were check command buffer sizes too alte so allocated dma regions
were freed before relocations so space checking failed.
|
| |
|
|
|
|
| |
this is an untested port of the r100 OQ code
|
|
|
|
| |
Scissors are jsut one of states that we have to emit so it should be in state list
|
| |
|
|
|
|
| |
Scissor are emited for every primitive so fix that in prediction.
|
| |
|
|
|
|
|
|
| |
Prediction code making too small prediction may cause space check aserttion
failure later in rendering. So warning about any failure to predict correctly
should be fixed.
|
|
|
|
| |
Trying to make understanding code easier with small refactoring and renaming.
|
|
|
|
| |
Signed-off-by: Pauli Nieminen <[email protected]>
|
|
|
|
| |
Signed-off-by: Pauli Nieminen <[email protected]>
|
|
|
|
|
|
| |
Calling EnsureCmdBufSpace is not required because rendering pipeline has to quarentee free space.
Signed-off-by: Pauli Nieminen <[email protected]>
|
|
|
|
|
|
|
| |
This patch makes render emit size prediction count the corect maximum emit size
for state.
Signed-off-by: Pauli Nieminen <[email protected]>
|
|
|
|
|
|
|
|
|
|
|
| |
Patch adds prediction functionthat tries to predict emit size to the smallest
possible values that is quarenteed to be higher than worst case scenario in
rendering pipeline.
State emit size prediction code is in place but fix for emit sizes is included
in next patch.
Signed-off-by: Pauli Nieminen <[email protected]>
|
|
|
|
| |
Signed-off-by: Pauli Nieminen <[email protected]>
|
|
|
|
|
|
|
| |
This allows us to return the unused portion of the dma buffer
to the allocator instead of wasting nearly 16k a pop.
Cherry picked and ported to new code by Pauli.
|
|
|
|
| |
Signed-off-by: Pauli Nieminen <[email protected]>
|
|
|
|
|
|
|
|
|
|
| |
We keep dma buffer objects in list untill they have been unused for many
draw operations. Current limit of having 100 flushes is just guess for
good performance/memory trade off.
Moving WARN_ONCE macro to common context because it is used in multiple drivers.
Signed-off-by: Pauli Nieminen <[email protected]>
|
| |
|
|
|
|
|
| |
This stuff was a vestige of the r600 bring up and
now mostly serves to periodically break the build.
|
|
|
|
| |
Signed-off-by: Pauli Nieminen <[email protected]>
|
| |
|
| |
|
|
|
|
|
| |
both for normal and cube textures, this fixes demos/multiarb
(with 6 enabled texture units) and fixes #23142.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Move all the metaops to a dri_metaops file and port radeon/intel
to use the new common meta ops code.
|
|
|
|
|
|
| |
Fixes those formats in fbo_firecube.
Only tested with r300, radeon and r200 compile tested only.
|
|
|
|
|
|
| |
Fixes fgl_glxgears and progs/demos/fbotexture after pressing 'c'.
Tested with r300, radeon and r200 compile tested only.
|
|
|
|
| |
Need to retrieve the bits from the rrb not from screen struct
|
| |
|