| Age | Commit message (Collapse) | Author |
|---|
|
Tested with Wayland.
|
|
Signed-off-by: Thomas Hellstrom <thellstrom@vmware.com>
|
|
When linked with certain builds of libstdc++, it appears like powf is resolved
by a symbol in that library. Other builds of libstdc++ doesn't contain that
symbol resulting in a linker / loader error. Optionally
resolve that symbol and replace it with calls to logf and expf.
Signed-off-by: Thomas Hellstrom <thellstrom@vmware.com>
|
|
Signed-off-by: Thomas Hellstrom <thellstrom@vmware.com>
|
|
|
|
Fixes this GCC warning.
graw.h:93: warning: 'struct pipe_surface' declared inside parameter list
graw.h:93: warning: its scope is only this definition or declaration,
which is probably not what you want
|
|
|
|
Allows applications to dump surfaces to file without
referencing gallium/auxiliary entry points statically.
Existing test apps have been modified such that
they save the contents of the fronbuffer only
when the `-o' option's specified.
|
|
Otherwise we'll get garbled data on Windows.
|
|
|
|
|
|
|
|
And run SConscripts if they are present.
Also make dri depend on both drm and x11.
|
|
Drivers scons files for a later time
|
|
|
|
This is a temporary work around to prevent crashes with glean/glsl1
(for example) which try to do vertex shader texturing.
|
|
|
|
Need to increment the array index to point to the last value.
Before, we were calling lp_build_array_alloca() over and over for
no reason.
|
|
|
|
|
|
|
|
|
|
We want to do the scatter store to sequential locations in memory
for the vector of pixels we're processing in SOA format.
|
|
|
|
The requested window size is of the client area,
so account for surrounding borders and bars when
creating the window.
|
|
|
|
|
|
Commit 8dfafbf0861fe3d2542332658dd5493851053c78 forgot to update r300g.
There is a buf == NULL check, but buf is used before for var init.
Tested-by: Guillermo S. Romero <gsromero@infernal-iceberg.com>
|
|
Make private those functions that are used internally only.
|
|
|
|
As a result remove some nasty macros.
|
|
|
|
Something is not quite right, however. The piglit tests mentioned in
fd.o bug 31226 still don't pass.
|
|
Trivial change that avoids a segmentation fault when the blitter state
happens to be bound when the context is destroyed.
The free calls should probably removed altogether in the future -- the
responsibility to destroy the state atoms lies with whoever created it,
and the safest thing for the pipe driver is to not touch any bound state
in its destructor.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Discard fractional bits from linewidth. This matches the nvidia
closed drivers, my reading of the OpenGL SI and current llvmpipe
behaviour.
It looks a lot nicer & avoids ugliness where lines alternate between n
and n+1 pixels in width along their length.
Also fix up r600g to match.
|
|
|
|
Should do better than this and actually unbind the buffer, but haven't
yet gotten it to work.
|
|
native_display_buffer is just a wrapper to resource_{from,get}_handle
for drm backend.
|
|
The interface is a wrapper to pipe_screen::resource_from_handle and
pipe_screen::resource_get_handle. A winsys handle is
platform-dependent.
|
|
This allows a backend to be written in C++.
|
|
These were previously being left in the default (D3D) mode. This mean
that triangles were drawn slightly incorrectly, but also because this
state is relied on by the u_blitter code, all blits were half a pixel
off.
|
|
These were being set but not used anywhere.
|
|
Generalize the existing tiled_buffer path in texture transfers for use
in some non-tiled up and downloads.
Use a staging buffer, which the winsys will restrict to GTT memory.
GTT buffers have the major advantage when they are mapped, they are
cachable, which is a very nice property for downloads, usually the CPU
will want to do look at the data it downloaded.
|
|
This opens the question of what interface the winsys layer should
really have for talking about these concepts.
For now I'm using the existing gallium resource usage concept, but
there is no reason not use terms closer to what the hardware
understands - eg. the domains themselves.
|
