From db94a2d03d3d888da2091dc20048bc178e243966 Mon Sep 17 00:00:00 2001 From: Marek Olšák Date: Tue, 12 May 2020 16:19:10 -0400 Subject: gallium: remove more "state tracker" occurences Trivial. Part-of: --- src/gallium/frontends/nine/README | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'src/gallium/frontends/nine') diff --git a/src/gallium/frontends/nine/README b/src/gallium/frontends/nine/README index 34e928d4da3..4f478de1d6c 100644 --- a/src/gallium/frontends/nine/README +++ b/src/gallium/frontends/nine/README @@ -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 -- cgit v1.2.3