Lines Matching +full:mesa +full:- +full:rules

5 --------------------------------
8 llvmpipe) in the Mesa tree. Two important reasons for this:
10  * Architecture - given our focus on scientific visualization, our
16  * Historical - Intel had developed a high performance software
19    with Mesa to provide a high quality API layer while at the same
24 ------------------------
26 SWR is a tile based immediate mode renderer with a sort-free threading
36 Our pipeline uses just-in-time compiled code for the fetch shader that
47 -----------------------
49 For the types of high-geometry workloads we're interested in, we are
57 OpenGL driver to Mesa we regressed performance severely, some due to
63 -----------------------
75 so doesn't match the strict line rendering rules).  The majority of
76 the piglit failures are errors in our driver layer interfacing Mesa
81 -------------------------------
84    download the Mesa source and enable our driver makes life much
90  * It's easier to work with the Mesa community when the source we're
94 --------------------------------
96  * Performance - see the performance section earlier for details.
98  * Conformance - see the conformance section earlier for details.
100  * Features - core SWR has a lot of functionality we have yet to
107 ----------------------------------
109  * All code is under the normal Mesa MIT license.
112 ----------------------
118 Will this work on ARM, MIPS, POWER, <other non-x86 architecture>?
119 -------------------------------------------------------------------------
122    intrinsics in our code and the in-tree JIT creation.  It is not the
123    intention for this codebase to support non-x86 architectures.
126 ------------------------
132  * You don't need a fire-breathing Xeon machine to work on SWR - we do
133    day-to-day development with laptops and desktop CPUs.
136 -----------------------------------------