| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
| |
Most of the time unfilled rendering requires a lot more thought than
just translating triangles to lines or points. But sometimes, you can
do exactly that, and it can be quite a bit quicker. Add code to do the
translation. The caller has to determine whether it's a legal thing
to do in the current state, in particular you'd need:
- culling disabled
- offset disabled
- same front and back fill modes
- possibly other stuff I can't think of.
|
| |
|
|
|
|
|
|
|
| |
This catches the linux-uclibc case and any others that were being set
prior to 98fcdf3f. Fixes bug 20345.
Signed-off-by: Dan Nicholson <[email protected]>
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
This fixed a minor bug but broke everything else.
This reverts commit 579ef8ab1984d895867f547afa60b3bec4c4599a.
|
| |
|
|
|
|
|
| |
Add asserts for expected values on wakeup and flush. Remove cases where
this flag is set or cleared except when waking up and flushing vbo module.
|
|
|
|
| |
See bug 20319.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The core reference counting code is centralized in p_refcnt.h.
This has some consequences related to struct pipe_buffer:
* The screen member of struct pipe_buffer must be initialized, or
pipe_buffer_reference() will crash trying to destroy a buffer with reference
count 0. u_simple_screen takes care of this, but I may have missed some of
the drivers not using it.
* Except for rare exceptions deep in winsys code, buffers must always be
allocated via pipe_buffer_create() or via screen->*buffer_create() rather
than via winsys->*buffer_create().
|
|
|
|
| |
Almost there. glxinfo still works, and AFAICT so does trivial/clear.
|
|
|
|
| |
s/migration/migrane/ , actually. Anyway, this has working glxinfo...
|
|
|
|
|
| |
For some reason makedepend doesn't seem to find the dependency on this
header in these two files. Directly including the header is a work-around.
|
|
|
|
|
|
|
| |
Front buffer rendering works as it stands but it completely
wrong. But as it stands fake front buffer rendering is
completely broken. So we keep it as it is. But lets atleast
handle it in the get buffers code.
|
|
|
|
|
| |
Doesn't do anything because we can't tell the X server about
any changes to the fake front buffer.
|
| |
|
| |
|
|
|
|
|
| |
Not needed since renderbuffers are ref-counted.
Fixes progs/demos/shadowtex.
|
| |
|
|
|
|
|
|
|
|
| |
When a hw driver fell back to swrast, swrast wasn't always getting informed
of program changes. When fixed function is translated into shaders, flags
like _NEW_LIGHT, _NEW_TEXTURE, etc. should really signal _NEW_PROGRAM.
In this case, swrast wasn't seeing _NEW_PROGRAM when new fragment shaders
were generated.
|
| |
|
| |
|
|
|
|
|
| |
Grabbed the latest copies from the GNU config repo at
http://git.savannah.gnu.org/cgit/config.git .
|
|\
| |
| |
| |
| | |
Conflicts:
src/gallium/auxiliary/pipebuffer/pb_buffer_fenced.c
|
| | |
|
| | |
|
| |
| |
| |
| | |
Add code so that existing driver behaviour doesn't change.
|
| | |
|
|\|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
scons/gallium.py
src/gallium/auxiliary/pipebuffer/pb_buffer_fenced.c
src/gallium/include/pipe/p_defines.h
src/mesa/vbo/vbo_exec_api.c
src/mesa/vbo/vbo_exec_draw.c
|
| | |
|
| |
| |
| |
| | |
Using PIPE_BUFFER_USAGE_DONTBLOCK.
|
| |
| |
| |
| |
| |
| | |
Previously would have to allocate a new VBO after firing a draw command
as subsequent call to Map() on old VBO might block if the driver had
submitted the commands to hardware.
|
| |
| |
| |
| |
| |
| | |
Will be needed in coming GL extensions (GL_map_buffer_range, GL 3.0).
Will be used by the vbo module to avoid reallocating vbo's at each
draw primitive call.
|
| |
| |
| |
| |
| | |
Provides notification to the VBO modules prior to the first immediate call.
Pairs with FlushVertices()
|
| | |
|
| |
| |
| |
| |
| |
| | |
Conflicts:
src/gallium/auxiliary/pipebuffer/pb_buffer_fenced.c
|
| |
| |
| |
| | |
To prevent blocking when mapping a buffer.
|
| |
| |
| |
| | |
No real change, as we're not tracking relocations read/write access yet.
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
DRI drivers can be build side by side with other non-DRI drivers, therefore
there is no need to build gallium twice.
|
| |
| |
| |
| | |
Like ccache, but works on all OSes.
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
This was based of the unfinnished code that Keith
Whitwell started on but never finnished. I moved
the code from the glx directory because dri drivers
can be used for more things then just glx.
|