[Mesa-dev] [PATCH] swr: update gallium driver docs
Emil Velikov
emil.l.velikov at gmail.com
Fri Apr 14 17:49:22 UTC 2017
On 13 April 2017 at 19:41, Tim Rowley <timothy.o.rowley at intel.com> wrote:
> ---
> src/gallium/docs/source/drivers/openswr.rst | 2 +-
> src/gallium/docs/source/drivers/openswr/usage.rst | 9 +++------
> 2 files changed, 4 insertions(+), 7 deletions(-)
>
> diff --git a/src/gallium/docs/source/drivers/openswr.rst b/src/gallium/docs/source/drivers/openswr.rst
> index 84aa51f..e254d7b 100644
> --- a/src/gallium/docs/source/drivers/openswr.rst
> +++ b/src/gallium/docs/source/drivers/openswr.rst
> @@ -7,7 +7,7 @@ geometry heavy workloads there is a considerable speedup over llvmpipe,
> which is to be expected as the geometry frontend of llvmpipe is single
> threaded.
>
> -This rasterizer is x86 specific and requires AVX or AVX2. The driver
> +This rasterizer is x86 specific and requires AVX or above. The driver
> fits into the gallium framework, and reuses gallivm for doing the TGSI
> to vectorized llvm-IR conversion of the shader kernels.
>
> diff --git a/src/gallium/docs/source/drivers/openswr/usage.rst b/src/gallium/docs/source/drivers/openswr/usage.rst
> index e55b421..d2a664e 100644
> --- a/src/gallium/docs/source/drivers/openswr/usage.rst
> +++ b/src/gallium/docs/source/drivers/openswr/usage.rst
> @@ -4,8 +4,9 @@ Usage
> Requirements
> ^^^^^^^^^^^^
>
> -* An x86 processor with AVX or AVX2
> -* LLVM version 3.6 or later
> +* An x86 processor with AVX or above
> +* LLVM version 3.9 or later
> +* C++14 capable compiler
>
> Building
> ^^^^^^^^
> @@ -22,10 +23,6 @@ On Linux, building will create a drop-in alternative for libGL.so into::
>
There is a hunk just outside of the diff that wants a
s/building will/building with autotools will/
> lib/gallium/libGL.so
>
> -or::
s/or/Alternatively, building with SCons will produce/
> -
> - build/foo/gallium/targets/libgl-xlib/libGL.so
> -
and then keep this line.
Considering George wired everything, one might as well have it documented ;-)
Either way not my call, so feel free to ignore.
-Emil
More information about the mesa-dev
mailing list