Commit 8c9b9aac authored by Marek Olšák's avatar Marek Olšák

gallium: change comments to remove 'state tracker'

Acked-by: Eric Anholt's avatarEric Anholt <eric@anholt.net>
Acked-by: Alyssa Rosenzweig's avatarAlyssa Rosenzweig <alyssa.rosenzweig@collabora.com>
Acked-by: Pierre-Eric Pelloux-Prayer's avatarPierre-Eric Pelloux-Prayer <pierre-eric.pelloux-prayer@amd.com>
Part-of: <!4902>
parent d6287a94
......@@ -430,7 +430,7 @@ Mesa EGL supports different sets of environment variables. See the
options.</dd>
</dl>
<h3>Clover state tracker environment variables</h3>
<h3>Clover environment variables</h3>
<dl>
<dt><code>CLOVER_EXTRA_BUILD_OPTIONS</code></dt>
......@@ -507,7 +507,7 @@ Mesa EGL supports different sets of environment variables. See the
<code>wglSwapIntervalEXT()</code> will have no effect.</dd>
</dl>
<h3>VA-API state tracker environment variables</h3>
<h3>VA-API environment variables</h3>
<dl>
<dt><code>VAAPI_MPEG4_ENABLED</code></dt>
<dd>enable MPEG4 for VA-API, disabled by default.</dd>
......
......@@ -76,7 +76,7 @@ option(
type : 'combo',
value : 'auto',
choices : ['auto', 'true', 'false'],
description : 'enable gallium vdpau state tracker.',
description : 'enable gallium vdpau frontend.',
)
option(
'vdpau-libs-path',
......@@ -89,7 +89,7 @@ option(
type : 'combo',
value : 'auto',
choices : ['auto', 'true', 'false'],
description : 'enable gallium xvmc state tracker.',
description : 'enable gallium xvmc frontend.',
)
option(
'xvmc-libs-path',
......@@ -102,7 +102,7 @@ option(
type : 'combo',
value : 'auto',
choices : ['auto', 'disabled', 'bellagio', 'tizonia'],
description : 'enable gallium omx state tracker.',
description : 'enable gallium omx frontend.',
)
option(
'omx-libs-path',
......@@ -115,7 +115,7 @@ option(
type : 'combo',
value : 'auto',
choices : ['auto', 'true', 'false'],
description : 'enable gallium va state tracker.',
description : 'enable gallium va frontend.',
)
option(
'va-libs-path',
......@@ -128,26 +128,26 @@ option(
type : 'combo',
value : 'auto',
choices : ['auto', 'true', 'false'],
description : 'enable gallium xa state tracker.',
description : 'enable gallium xa frontend.',
)
option(
'gallium-nine',
type : 'boolean',
value : false,
description : 'build gallium "nine" Direct3D 9.x state tracker.',
description : 'build gallium "nine" Direct3D 9.x frontend.',
)
option(
'gallium-opencl',
type : 'combo',
choices : ['icd', 'standalone', 'disabled'],
value : 'disabled',
description : 'build gallium "clover" OpenCL state tracker.',
description : 'build gallium "clover" OpenCL frontend.',
)
option(
'opencl-spirv',
type : 'boolean',
value : false,
description : 'build gallium "clover" OpenCL state tracker with SPIR-V binary support.',
description : 'build gallium "clover" OpenCL frontend with SPIR-V binary support.',
)
option(
'd3d-drivers-path',
......
......@@ -3,7 +3,7 @@
= General Considerations =
The state tracker and winsys driver support a rather limited number of
The frontend and winsys driver support a rather limited number of
platforms. However, the pipe drivers are meant to run in a wide number of
platforms. Hence the pipe drivers, the auxiliary modules, and all public
headers in general, should strictly follow these guidelines to ensure
......
......@@ -39,7 +39,7 @@ if env['platform'] == 'windows':
#
# State trackers and targets
# Frontends and targets
#
if not env['embedded']:
......
......@@ -71,7 +71,7 @@ cso_set_samplers(struct cso_context *cso,
const struct pipe_sampler_state **states);
/* Alternate interface to support state trackers that like to modify
/* Alternate interface to support gallium frontends that like to modify
* samplers one at a time:
*/
void
......@@ -100,7 +100,7 @@ void cso_set_stream_outputs(struct cso_context *ctx,
* We don't provide shader caching in CSO. Most of the time the api provides
* object semantics for shaders anyway, and the cases where it doesn't
* (eg mesa's internally-generated texenv programs), it will be up to
* the state tracker to implement their own specialized caching.
* gallium frontends to implement their own specialized caching.
*/
void cso_set_fragment_shader_handle(struct cso_context *ctx, void *handle);
......
......@@ -633,7 +633,7 @@ aaline_stage_from_pipe(struct pipe_context *pipe)
/**
* This function overrides the driver's create_fs_state() function and
* will typically be called by the state tracker.
* will typically be called by the gallium frontend.
*/
static void *
aaline_create_fs_state(struct pipe_context *pipe,
......
......@@ -734,7 +734,7 @@ aapoint_stage_from_pipe(struct pipe_context *pipe)
/**
* This function overrides the driver's create_fs_state() function and
* will typically be called by the state tracker.
* will typically be called by the gallium frontend.
*/
static void *
aapoint_create_fs_state(struct pipe_context *pipe,
......
......@@ -334,7 +334,7 @@ pstip_stage_from_pipe(struct pipe_context *pipe)
/**
* This function overrides the driver's create_fs_state() function and
* will typically be called by the state tracker.
* will typically be called by the gallium frontend.
*/
static void *
pstip_create_fs_state(struct pipe_context *pipe,
......
......@@ -47,7 +47,7 @@
* that varies .x from 0 to 1 horizontally across the point and varies .y
* vertically from 0 to 1 down the sprite.
*
* With geometry shaders, the state tracker could create a GS to do
* With geometry shaders, the gallium frontends could create a GS to do
* most/all of this.
*/
......
......@@ -425,7 +425,7 @@ draw_pt_arrays_restart(struct draw_context *draw,
}
else {
/* Non-indexed prims (draw_arrays).
* Primitive restart should have been handled in the state tracker.
* Primitive restart should have been handled in gallium frontends.
*/
draw_pt_arrays(draw, prim, start, count);
}
......@@ -556,7 +556,7 @@ draw_vbo(struct draw_context *draw,
/*
* TODO: We could use draw->pt.max_index to further narrow
* the min_index/max_index hints given by the state tracker.
* the min_index/max_index hints given by gallium frontends.
*/
for (instance = 0; instance < info->instance_count; instance++) {
......
......@@ -40,7 +40,7 @@
* TGSI translation limits.
*
* Some are slightly above SM 3.0 requirements to give some wiggle room to
* the state trackers.
* the gallium frontends.
*/
#define LP_MAX_TGSI_TEMPS 4096
......
......@@ -143,11 +143,11 @@ static void init_native_targets()
extern "C" void
lp_set_target_options(void)
{
/* The llvm target registry is not thread-safe, so drivers and state-trackers
/* The llvm target registry is not thread-safe, so drivers and gallium frontends
* that want to initialize targets should use the lp_set_target_options()
* function to safely initialize targets.
*
* LLVM targets should be initialized before the driver or state-tracker tries
* LLVM targets should be initialized before the driver or gallium frontend tries
* to access the registry.
*/
call_once(&init_native_targets_once_flag, init_native_targets);
......
......@@ -179,7 +179,7 @@ lp_sampler_static_sampler_state(struct lp_static_sampler_state *state,
* spurious recompiles, as the sampler static state is part of the shader
* key.
*
* Ideally the state tracker or cso_cache module would make all state
* Ideally gallium frontends or cso_cache module would make all state
* canonical, but until that happens it's better to be safe than sorry here.
*
* XXX: Actually there's much more than can be done here, especially
......
......@@ -3124,7 +3124,7 @@ lp_build_sample_soa_code(struct gallivm_state *gallivm,
* here which would say it's pure int despite such formats should sample
* the depth component).
* In GL such filters make the texture incomplete, this makes it robust
* against state trackers which set this up regardless (we'd crash in the
* against gallium frontends which set this up regardless (we'd crash in the
* lerp later otherwise).
* At least in some apis it may be legal to use such filters with lod
* queries and/or gather (at least for gather d3d10 says only the wrap
......
......@@ -27,7 +27,7 @@
/* This head-up display module can draw transparent graphs on top of what
* the app is rendering, visualizing various data like framerate, cpu load,
* performance counters, etc. It can be hook up into any state tracker.
* performance counters, etc. It can be hook up into any gallium frontend.
*
* The HUD is controlled with the GALLIUM_HUD environment variable.
* Set GALLIUM_HUD=help for more info.
......
......@@ -107,7 +107,7 @@ util_draw_max_index(
max_index = MIN2(max_index, buffer_max_index);
}
else {
/* Per-instance data. Simply make sure the state tracker didn't
/* Per-instance data. Simply make sure gallium frontends didn't
* request more instances than those that fit in the buffer */
if ((info->start_instance + info->instance_count)/element->instance_divisor
> (buffer_max_index + 1)) {
......
......@@ -165,7 +165,7 @@ util_upload_index_buffer(struct pipe_context *pipe,
* CPU cores that share the same L3 cache. This is needed for good multi-
* threading performance on AMD Zen CPUs.
*
* \param upper_thread thread in the state tracker that also needs to be
* \param upper_thread thread in gallium frontends that also needs to be
* pinned.
*/
void
......
......@@ -111,7 +111,7 @@ u_pipe_screen_get_param_defaults(struct pipe_screen *pscreen,
return 120;
case PIPE_CAP_ESSL_FEATURE_LEVEL:
/* Tell state-tracker to fallback to PIPE_CAP_GLSL_FEATURE_LEVEL */
/* Tell gallium frontend to fallback to PIPE_CAP_GLSL_FEATURE_LEVEL */
return 0;
case PIPE_CAP_QUADS_FOLLOW_PROVOKING_VERTEX_CONVENTION:
......
......@@ -238,7 +238,7 @@ threaded_context_flush(struct pipe_context *_pipe,
{
struct threaded_context *tc = threaded_context(_pipe);
/* This is called from the state-tracker / application thread. */
/* This is called from the gallium frontend / application thread. */
if (token->tc && token->tc == tc) {
struct tc_batch *last = &tc->batch_slots[tc->last];
......
......@@ -27,7 +27,7 @@
/**
* RGBA/float tile get/put functions.
* Usable both by drivers and state trackers.
* Usable both by drivers and gallium frontends.
*/
......
......@@ -82,7 +82,7 @@ struct u_transfer_vtbl {
* Must be implemented if separate stencil or fake_rgtc is used. The
* internal_format is the format the resource was created with. In
* the case of separate stencil or fake_rgtc, prsc->format is set back
* to the state tracker visible format (e.g. Z32_FLOAT_S8X24_UINT or
* to the gallium-frontend-visible format (e.g. Z32_FLOAT_S8X24_UINT or
* PIPE_FORMAT_{RTGC,LATC}* after the resource is created.
*/
enum pipe_format (*get_internal_format)(struct pipe_resource *prsc);
......
......@@ -382,7 +382,7 @@ Queries
^^^^^^^
Queries gather some statistic from the 3D pipeline over one or more
draws. Queries may be nested, though not all state trackers exercise this.
draws. Queries may be nested, though not all gallium frontends exercise this.
Queries can be created with ``create_query`` and deleted with
``destroy_query``. To start a query, use ``begin_query``, and when finished,
......@@ -856,7 +856,7 @@ for particular texture types or formats.
Device resets
^^^^^^^^^^^^^
The state tracker can query or request notifications of when the GPU
Gallium frontends can query or request notifications of when the GPU
is reset for whatever reason (application error, driver error). When
a GPU reset happens, the context becomes unusable and all related state
should be considered lost and undefined. Despite that, context
......
......@@ -21,7 +21,7 @@ OpenGL: glClampColor(GL_CLAMP_VERTEX_COLOR) in GL 3.0 or GL_ARB_color_buffer_flo
D3D11: seems always disabled
Note the PIPE_CAP_VERTEX_COLOR_CLAMPED query indicates whether or not the
driver supports this control. If it's not supported, the state tracker may
driver supports this control. If it's not supported, gallium frontends may
have to insert extra clamping code.
......@@ -36,7 +36,7 @@ OpenGL: glClampColor(GL_CLAMP_FRAGMENT_COLOR) in GL 3.0 or ARB_color_buffer_floa
D3D11: seems always disabled
Note the PIPE_CAP_FRAGMENT_COLOR_CLAMPED query indicates whether or not the
driver supports this control. If it's not supported, the state tracker may
driver supports this control. If it's not supported, gallium frontends may
have to insert extra clamping code.
......@@ -184,7 +184,7 @@ the state of 'sprite_coord_mode' (see below).
If any bit is set, then point_smooth MUST be disabled (there are no
round sprites) and point_quad_rasterization MUST be true (sprites are
always rasterized as quads). Any mismatch between these states should
be considered a bug in the state-tracker.
be considered a bug in the gallium frontend.
This feature is implemented in the :ref:`Draw` module but may also be
implemented natively by GPUs or implemented with a geometry shader.
......
......@@ -46,8 +46,8 @@ the shader sanity checker prints its warnings and errors to stderr.
Whether the :ref:`Draw` module will attempt to use LLVM for vertex and geometry shaders.
State tracker-specific
""""""""""""""""""""""
GL State tracker-specific
"""""""""""""""""""""""""
.. envvar:: ST_DEBUG <flags> (0x0)
......
Distribution
============
Along with the interface definitions, the following drivers, state trackers,
Along with the interface definitions, the following drivers, gallium frontends,
and auxiliary modules are shipped in the standard Gallium distribution.
Drivers
......@@ -78,8 +78,8 @@ Rbug
Wrapper driver. :ref:`rbug` driver used with stand alone rbug-gui.
State Trackers
--------------
Gallium frontends
-----------------
Clover
^^^^^^
......@@ -101,9 +101,9 @@ GLX
MesaGL
^^^^^^
Tracker implementing a GL state machine. Not usable as a standalone tracker;
Mesa should be built with another state tracker, such as :ref:`DRI` or
:ref:`EGL`.
The gallium frontend implementing a GL state machine. Not usable as
a standalone frontend; Mesa should be built with another gallium frontend,
such as :ref:`DRI` or :ref:`EGL`.
VDPAU
^^^^^
......
......@@ -85,7 +85,7 @@ The integer capabilities:
per-instance vertex attribs.
* ``PIPE_CAP_FRAGMENT_COLOR_CLAMPED``: Whether fragment color clamping is
supported. That is, is the pipe_rasterizer_state::clamp_fragment_color
flag supported by the driver? If not, the state tracker will insert
flag supported by the driver? If not, gallium frontends will insert
clamping code into the fragment shaders when needed.
* ``PIPE_CAP_MIXED_COLORBUFFER_FORMATS``: Whether mixed colorbuffer formats are
......@@ -99,7 +99,7 @@ The integer capabilities:
the vertex colors are never clamped. This is the default for DX10 hardware.
If both clamped and unclamped CAPs are supported, the clamping can be
controlled through pipe_rasterizer_state. If the driver cannot do vertex
color clamping, the state tracker may insert clamping code into the vertex
color clamping, gallium frontends may insert clamping code into the vertex
shader.
* ``PIPE_CAP_GLSL_FEATURE_LEVEL``: Whether the driver supports features
equivalent to a specific GLSL version. E.g. for GLSL 1.3, report 130.
......@@ -121,7 +121,7 @@ The integer capabilities:
* ``PIPE_CAP_QUADS_FOLLOW_PROVOKING_VERTEX_CONVENTION``: Whether quads adhere to
the flatshade_first setting in ``pipe_rasterizer_state``.
* ``PIPE_CAP_USER_VERTEX_BUFFERS``: Whether the driver supports user vertex
buffers. If not, the state tracker must upload all data which is not in hw
buffers. If not, gallium frontends must upload all data which is not in hw
resources. If user-space buffers are supported, the driver must also still
accept HW resource buffers.
* ``PIPE_CAP_VERTEX_BUFFER_OFFSET_4BYTE_ALIGNED_ONLY``: This CAP describes a hw
......@@ -164,7 +164,7 @@ The integer capabilities:
input that will always be replaced with sprite coordinates.
* ``PIPE_CAP_PREFER_BLIT_BASED_TEXTURE_TRANSFER``: Whether it is preferable
to use a blit to implement a texture transfer which needs format conversions
and swizzling in state trackers. Generally, all hardware drivers with
and swizzling in gallium frontends. Generally, all hardware drivers with
dedicated memory should return 1 and all software rasterizers should return 0.
* ``PIPE_CAP_QUERY_PIPELINE_STATISTICS``: Whether PIPE_QUERY_PIPELINE_STATISTICS
is supported.
......@@ -256,7 +256,7 @@ The integer capabilities:
for enabling ARB_clip_control.
* ``PIPE_CAP_VERTEXID_NOBASE``: If true, the driver only supports
TGSI_SEMANTIC_VERTEXID_NOBASE (and not TGSI_SEMANTIC_VERTEXID). This means
state trackers for APIs whose vertexIDs are offset by basevertex (such as GL)
gallium frontends for APIs whose vertexIDs are offset by basevertex (such as GL)
will need to lower TGSI_SEMANTIC_VERTEXID to TGSI_SEMANTIC_VERTEXID_NOBASE
and TGSI_SEMANTIC_BASEVERTEX, so drivers setting this must handle both these
semantics. Only relevant if geometry shaders are supported.
......@@ -310,11 +310,11 @@ The integer capabilities:
supported in vertex shaders.
* ``PIPE_CAP_TGSI_PACK_HALF_FLOAT``: Whether the ``UP2H`` and ``PK2H``
TGSI opcodes are supported.
* ``PIPE_CAP_TGSI_FS_POSITION_IS_SYSVAL``: If state trackers should use
* ``PIPE_CAP_TGSI_FS_POSITION_IS_SYSVAL``: If gallium frontends should use
a system value for the POSITION fragment shader input.
* ``PIPE_CAP_TGSI_FS_POINT_IS_SYSVAL``: If state trackers should use
* ``PIPE_CAP_TGSI_FS_POINT_IS_SYSVAL``: If gallium frontends should use
a system value for the POINT fragment shader input.
* ``PIPE_CAP_TGSI_FS_FACE_IS_INTEGER_SYSVAL``: If state trackers should use
* ``PIPE_CAP_TGSI_FS_FACE_IS_INTEGER_SYSVAL``: If gallium frontends should use
a system value for the FACE fragment shader input.
Also, the FACE system value is integer, not float.
* ``PIPE_CAP_SHADER_BUFFER_OFFSET_ALIGNMENT``: Describes the required
......@@ -528,7 +528,7 @@ The integer capabilities:
A driver might rely on the input mapping that was defined with the original
GLSL code.
* ``PIPE_CAP_IMAGE_LOAD_FORMATTED``: True if a format for image loads does not need to be specified in the shader IR
* ``PIPE_CAP_THROTTLE``: Whether or not state trackers should throttle pipe_context
* ``PIPE_CAP_THROTTLE``: Whether or not gallium frontends should throttle pipe_context
execution. 0 = throttling is disabled.
* ``PIPE_CAP_DMABUF``: Whether Linux DMABUF handles are supported by
resource_from_handle and resource_get_handle.
......@@ -537,7 +537,7 @@ The integer capabilities:
* ``PIPE_CAP_FRAGMENT_SHADER_INTERLOCK``: True if fragment shader interlock
functionality is supported.
* ``PIPE_CAP_CS_DERIVED_SYSTEM_VALUES_SUPPORTED``: True if driver handles
gl_LocalInvocationIndex and gl_GlobalInvocationID. Otherwise, state tracker will
gl_LocalInvocationIndex and gl_GlobalInvocationID. Otherwise, gallium frontends will
lower those system values.
* ``PIPE_CAP_ATOMIC_FLOAT_MINMAX``: Atomic float point minimum,
maximum, exchange and compare-and-swap support to buffer and shared variables.
......@@ -552,7 +552,7 @@ The integer capabilities:
types with texture functions having interaction with LOD of texture lookup.
* ``PIPE_CAP_SHADER_SAMPLES_IDENTICAL``: True if the driver supports a shader query to tell whether all samples of a multisampled surface are definitely identical.
* ``PIPE_CAP_TGSI_ATOMINC_WRAP``: Atomic increment/decrement + wrap around are supported.
* ``PIPE_CAP_PREFER_IMM_ARRAYS_AS_CONSTBUF``: True if the state tracker should
* ``PIPE_CAP_PREFER_IMM_ARRAYS_AS_CONSTBUF``: True if gallium frontends should
turn arrays whose contents can be deduced at compile time into constant
buffer loads, or false if the driver can handle such arrays itself in a more
efficient manner.
......@@ -667,7 +667,7 @@ MOV OUT[0], CONST[0][3] # copy vector 3 of constbuf 0
ignore tgsi_declaration_range::Last for shader inputs and outputs.
* ``PIPE_SHADER_CAP_MAX_UNROLL_ITERATIONS_HINT``: This is the maximum number
of iterations that loops are allowed to have to be unrolled. It is only
a hint to state trackers. Whether any loops will be unrolled is not
a hint to gallium frontends. Whether any loops will be unrolled is not
guaranteed.
* ``PIPE_SHADER_CAP_MAX_SHADER_BUFFERS``: Maximum number of memory buffers
(also used to implement atomic counters). Having this be non-0 also
......@@ -677,7 +677,7 @@ MOV OUT[0], CONST[0][3] # copy vector 3 of constbuf 0
program. It should be a mask of ``pipe_shader_ir`` bits.
* ``PIPE_SHADER_CAP_MAX_SHADER_IMAGES``: Maximum number of image units.
* ``PIPE_SHADER_CAP_LOWER_IF_THRESHOLD``: IF and ELSE branches with a lower
cost than this value should be lowered by the state tracker for better
cost than this value should be lowered by gallium frontends for better
performance. This is a tunable for the GLSL compiler and the behavior is
specific to the compiler.
* ``PIPE_SHADER_CAP_TGSI_SKIP_MERGE_REGISTERS``: Whether the merge registers
......
......@@ -2506,7 +2506,7 @@ after lookup.
If per-sample shading is not in effect or the source resource or render
target is not multisampled, the result is (0.5, 0.5, undef, undef).
NOTE: no driver has implemented this opcode yet (and no state tracker
NOTE: no driver has implemented this opcode yet (and no gallium frontend
emits it). This information is subject to change.
.. opcode:: SAMPLE_INFO
......@@ -2525,7 +2525,7 @@ after lookup.
If per-sample shading is not in effect or the source resource or render
target is not multisampled, the result is (1, 0, 0, 0).
NOTE: no driver has implemented this opcode yet (and no state tracker
NOTE: no driver has implemented this opcode yet (and no gallium frontend
emits it). This information is subject to change.
.. opcode:: LOD - level of detail
......
......@@ -574,7 +574,7 @@ etna_context_create(struct pipe_screen *pscreen, void *priv, unsigned flags)
/* context ctxate setup */
ctx->screen = screen;
/* need some sane default in case state tracker doesn't set some state: */
/* need some sane default in case gallium frontends don't set some state: */
ctx->sample_mask = 0xffff;
/* Set sensible defaults for state */
......
......@@ -90,7 +90,7 @@ etna_set_constant_buffer(struct pipe_context *pctx,
util_copy_constant_buffer(&so->cb[index], cb);
/* Note that the state tracker can unbind constant buffers by
/* Note that the gallium frontends can unbind constant buffers by
* passing NULL here. */
if (unlikely(!cb || (!cb->buffer && !cb->user_buffer))) {
so->enabled_mask &= ~(1 << index);
......
......@@ -380,7 +380,7 @@ fd_context_init(struct fd_context *ctx, struct pipe_screen *pscreen,
(void) mtx_init(&ctx->gmem_lock, mtx_plain);
/* need some sane default in case state tracker doesn't
/* need some sane default in case gallium frontends don't
* set some state:
*/
ctx->sample_mask = 0xffff;
......
......@@ -380,7 +380,7 @@ fd_try_shadow_resource(struct fd_context *ctx, struct fd_resource *rsc,
* Uncompress an UBWC compressed buffer "in place". This works basically
* like resource shadowing, creating a new resource, and doing an uncompress
* blit, and swapping the state between shadow and original resource so it
* appears to the state tracker as if nothing changed.
* appears to the gallium frontends as if nothing changed.
*/
void
fd_resource_uncompress(struct fd_context *ctx, struct fd_resource *rsc)
......
......@@ -104,7 +104,7 @@ fd_set_constant_buffer(struct pipe_context *pctx,
util_copy_constant_buffer(&so->cb[index], cb);
/* Note that the state tracker can unbind constant buffers by
/* Note that gallium frontends can unbind constant buffers by
* passing NULL here.
*/
if (unlikely(!cb)) {
......
......@@ -888,7 +888,7 @@ static void i915_set_clip_state( struct pipe_context *pipe,
/* Called when driver state tracker notices changes to the viewport
/* Called when gallium frontends notice changes to the viewport
* matrix:
*/
static void i915_set_viewport_states( struct pipe_context *pipe,
......
......@@ -731,7 +731,7 @@ _iris_batch_flush(struct iris_batch *batch, const char *file, int line)
*/
if (ret == -EIO && replace_hw_ctx(batch)) {
if (batch->reset->reset) {
/* Tell the state tracker the device is lost and it was our fault. */
/* Tell gallium frontends the device is lost and it was our fault. */
batch->reset->reset(batch->reset->data, PIPE_GUILTY_CONTEXT_RESET);
}
......
......@@ -189,7 +189,7 @@ iris_is_format_supported(struct pipe_screen *pscreen,
/* Don't advertise 3-component RGB formats for non-buffer textures.
* This ensures that they are renderable from an API perspective since
* the state tracker will fall back to RGBA or RGBX, which are
* gallium frontends will fall back to RGBA or RGBX, which are
* renderable. We want to render internally for copies and blits,
* even if the application doesn't.
*
......
......@@ -1334,7 +1334,7 @@ iris_create_zsa_state(struct pipe_context *ctx,
state->stencil[0].writemask != 0 ||
(two_sided_stencil && state->stencil[1].writemask != 0);
/* The state tracker needs to optimize away EQUAL writes for us. */
/* gallium frontends need to optimize away EQUAL writes for us. */
assert(!(state->depth.func == PIPE_FUNC_EQUAL && state->depth.writemask));
iris_pack_command(GENX(3DSTATE_WM_DEPTH_STENCIL), cso->wmds, wmds) {
......@@ -1987,7 +1987,7 @@ iris_upload_sampler_states(struct iris_context *ice, gl_shader_stage stage)
struct iris_shader_state *shs = &ice->state.shaders[stage];
const struct shader_info *info = iris_get_shader_info(ice, stage);
/* We assume the state tracker will call pipe->bind_sampler_states()
/* We assume gallium frontends will call pipe->bind_sampler_states()
* if the program's number of textures changes.
*/
unsigned count = info ? util_last_bit(info->textures_used) : 0;
......@@ -2586,7 +2586,7 @@ iris_create_surface(struct pipe_context *ctx,
* texture, the tile offsets may be anything and we can't rely on
* X/Y Offset.
*
* Return NULL to force the state tracker to take fallback paths.
* Return NULL to force gallium frontends to take fallback paths.
*/
if (view->array_len > 1 || GEN_GEN == 8)
return NULL;
......
......@@ -440,7 +440,7 @@ lp_setup_try_clear_color_buffer(struct lp_setup_context *setup,
else {
/* Put ourselves into the 'pre-clear' state, specifically to try
* and accumulate multiple clears to color and depth_stencil
* buffers which the app or state-tracker might issue
* buffers which the app or gallium frontend might issue
* separately.
*/
set_scene_state( setup, SETUP_CLEARED, __FUNCTION__ );
......@@ -504,7 +504,7 @@ lp_setup_try_clear_zs(struct lp_setup_context *setup,
else {
/* Put ourselves into the 'pre-clear' state, specifically to try
* and accumulate multiple clears to color and depth_stencil
* buffers which the app or state-tracker might issue
* buffers which the app or gallium frontend might issue
* separately.
*/
set_scene_state( setup, SETUP_CLEARED, __FUNCTION__ );
......