summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorfeydun <feydun@gmail.com>2012-09-18 19:35:51 +0100
committerSt├ęphane Marchesin <marcheu@chromium.org>2012-10-08 15:30:34 -0700
commit2c803deeb009ff3b6a133500c2cc5ab5f46c3d6e (patch)
tree2dd4bf285d7724802fbb22aecd24e754c9c972b1
parent848e171ba9589dcdc8c3dd91eeecb746e66b0ff4 (diff)
minor changes to chapter 10, gallium 3dHEADmaster
-rw-r--r--linuxgraphicsdrivers.lyx34
1 files changed, 17 insertions, 17 deletions
diff --git a/linuxgraphicsdrivers.lyx b/linuxgraphicsdrivers.lyx
index 8ad801e..5901748 100644
--- a/linuxgraphicsdrivers.lyx
+++ b/linuxgraphicsdrivers.lyx
@@ -9153,8 +9153,8 @@ Winsys
\end_layout
\begin_layout Standard
-The name Winsys is actually a bit of a misnaming, but it wasn't changed
- since Gallium was introduced.
+The name Winsys is actually a bit of a misnomer, but it hasn't changed since
+ Gallium was introduced.
The Winsys provides the hardware drivers with an internal fixed interface
to talk to the operating system.
You can easily imagine a driver for the same hardware working on different
@@ -9175,10 +9175,9 @@ Pipe driver
\begin_layout Standard
\lang english
-Pipe drivers are the components that are actually implementing the Gallium
- interface.
- They are talking directly to the hardware, through the Winsys or direct
- usage of the respective operating system routines.
+Pipe drivers are the components that actually implement the Gallium interface.
+ They talk directly to the hardware, through the Winsys or direct usage
+ of the respective operating system routines.
The pipe driver has to fully hide how your hardware works internally.
\end_layout
@@ -9191,10 +9190,10 @@ State trackers
\begin_layout Standard
\lang english
-State trackers are sitting on top of the Gallium interface and implement
- a specific API like OpenGL, OpenCL or other custom APIs that use the GPU
- to accelerate something.
- They do so by turning the API calls into hardware independent acceleration
+State trackers sit on top of the Gallium interface and implement a specific
+ API like OpenGL, OpenCL or other custom APIs that use the GPU to accelerate
+ something.
+ They do so by turning the API calls into hardware-independent acceleration
operations covered by Gallium.
\end_layout
@@ -9202,9 +9201,9 @@ State trackers are sitting on top of the Gallium interface and implement
\begin_layout Standard
\lang english
-Gallium abstracts away most of the internals of the GPU, however it can
- not hide the different featuresets exposed by the large numbers of GPUs
- used today.
+Gallium abstracts away most of the internals of the GPU, however it cannot
+ hide the different featuresets exposed by the large numbers of GPUs used
+ today.
Some things are hidden internally, like some drivers using a JIT compiler
to do fallbacks when the GPU can't execute a specific shader and it seems
worthwhile to do a software fallback, but mostly the differences in capabilitie
@@ -9267,15 +9266,16 @@ In order to operate shaders, Gallium features an internal shader description
In particular, v.x is the first component of vector v, v.xyzw are all 4 component
s of v in that order, and swizzling is allowed, for example v.wzyx reverses
the component order.
- It is also legal to replicate a component, for example v.xxxx means four
- times the x component of v and v.yyzz means two times y and two times z.
+ It is also legal to replicate a component, for example v.xxxx means the
+ x component of v is cloned to all four components and v.yyzz means two identical
+ y and two identical z.
\end_layout
\begin_layout Standard
\lang english
-These components usually carry no semantics, and despite their name they
- can very well carry a color or an opacity value indifferently.
+These components usually carry no semantics, and despite their coordinate
+ names they can just as easily represent a color or an opacity value.
\end_layout