fdo-mirrors/mesa
1
0
Fork 0
mirror of https://gitlab.freedesktop.org/mesa/mesa.git synced 2026-03-14 08:40:30 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions 1

gallium: remove more "state tracker" occurences

Browse source 
Trivial.

Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4902>
This commit is contained in:
Marek Olšák 2020-05-12 16:19:10 -04:00
parent 7480069703
commit db94a2d03d
6 changed files with 11 additions and 13 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
src/gallium/auxiliary/driver_rbug/README
View file

@ -22,7 +22,7 @@ information is in that directory. Also for a gui see:
= Integrating =
You can integrate the rbug pipe driver either inside the state tracker or the
You can integrate the rbug pipe driver either inside the gallium frontend or the
target. The procedure on both cases is the same. Let's assume you have a
pipe_screen obtained by the usual means (variable and function names are just
for illustration purposes):

2
src/gallium/auxiliary/driver_trace/README
View file

@ -33,7 +33,7 @@ For remote debugging see:
= Integrating =
You can integrate the trace pipe driver either inside the state tracker or the
You can integrate the trace pipe driver either inside the gallium frontend or the
target. The procedure on both cases is the same. Let's assume you have a
pipe_screen obtained by the usual means (variable and function names are just
for illustration purposes):

2
src/gallium/auxiliary/postprocess/ADDING
View file

@ -6,7 +6,7 @@ These shaders may be written in any supported language, but are added here in TG
assembly.
You can translate GLSL/ARB fairly easily via llvmpipe (LP_DEBUG=tgsi). I don't know the
status of the D3D state tracker, but if/when that works, I'd assume HLSL would be possible
status of the D3D gallium frontend, but if/when that works, I'd assume HLSL would be possible
too.

2
src/gallium/frontends/README
View file

@ -1,2 +0,0 @@
This directory is a placeholder for incubating state-trackers. Mesa's
state-tracker is in src/mesa.

4
src/gallium/frontends/nine/README
View file

@ -49,7 +49,7 @@ ID3DAdapter9 is completely devoid of window system code, meaning this can be
provided by wine, Xlib, Wayland, etc. It's inadvisible to write a non-Windows
backend though, as we don't want to encourage linux developers to use this API.
The state tracker is compiled, along with pipe-loader, into a library called
The gallium frontend is compiled, along with pipe-loader, into a library called
libd3dadapter9.so. This library loads pipe_[driver].so drivers on demand and
exports a single symbol for getting a subsystem driver. Currently only DRM is
supported.
@ -68,7 +68,7 @@ The former is the global on-switch. The latter is per-exe.
The driver search path can be set at configure time with
--with-gallium-driver-dir and overridden at runtime with D3D9_DRIVERS_PATH.
Debugging information can be gotten with the WINEDEBUG channels d3d9 and
d3dadapter, and state_tracker debug information can be gotten with NINE_DEBUG.
d3dadapter, and gallium frontend debug information can be gotten with NINE_DEBUG.
Help on NINE_DEBUG is shown through NINE_DEBUG=help
Finally, the ID3DPresent[Group] and ID3DAdapter9 interfaces are not set in

12
src/gallium/frontends/xa/README
View file

@ -27,11 +27,11 @@
* Thomas Hellstrom <thellstrom-at-vmware-dot-com>
*/
The XA state tracker is intended as a versioned interface to gallium for
The XA gallium frontend is intended as a versioned interface to gallium for
xorg driver writers. Initially it's mostly based on Zack Rusin's
composite / video work for the Xorg state tracker.
composite / video work for the Xorg gallium frontend.
The motivation behind this state tracker is that the Xorg state tracker has
The motivation behind this gallium frontend is that the Xorg gallium frontend has
a number of interfaces to work with:
1) The Xorg sdk (versioned)
@ -39,11 +39,11 @@ a number of interfaces to work with:
3) KMS modesetting (versioned)
4) Driver-private (hopefully versioned)
Since Gallium3D is not versioned, the Xorg state tracker needs to be compiled
Since Gallium3D is not versioned, the Xorg gallium frontend needs to be compiled
with Gallium, but it's really beneficial to be able to compile xorg drivers
standalone.
Therefore the xa state tracker is intended to supply the following
Therefore the xa gallium frontend is intended to supply the following
functionality:
1) Versioning.
@ -56,7 +56,7 @@ functionality:
The first user will be the vmwgfx xorg driver. When there are more users,
we need to be able to load the appropriate gallium pipe driver, and we
should investigate sharing the loadig mechanism with the EGL state tracker.
should investigate sharing the loadig mechanism with the EGL gallium frontend.
IMPORTANT:
Version compatibilities: