diff options
author | Brian Paul <brianp@vmware.com> | 2009-08-14 11:23:18 -0600 |
---|---|---|
committer | Brian Paul <brianp@vmware.com> | 2009-08-14 11:23:18 -0600 |
commit | a7ca80ff6af8d3b28b981b518ca39baba20a2d89 (patch) | |
tree | a80c27d50d52b5ca3fb6a5ea30a5c78d72cf35ff | |
parent | 467b3d9a6f32b38c36a4be145b07c8f7b719215a (diff) |
Add a FAQ about internal buffer sizes.
(cherry picked from master, commit 9a8781bd24730374e14568f67f7db8a9cc444bb4)
-rw-r--r-- | docs/faq.html | 13 |
1 files changed, 13 insertions, 0 deletions
diff --git a/docs/faq.html b/docs/faq.html index 11b5d43255..65e279aac5 100644 --- a/docs/faq.html +++ b/docs/faq.html @@ -316,6 +316,19 @@ Basically, applying a translation of (0.375, 0.375, 0.0) to your coordinates will fix the problem. </p> +<h2>3.6 How can I change the maximum framebuffer size in Mesa's +<tt>swrast</tt> backend?</h2> +<p> +These can be overridden by using the <tt>--with-max-width</tt> and +<tt>--with-max-height</tt> options. The two need not be equal. +</p><p> +Do note that Mesa uses these values to size some internal buffers, +so increasing these sizes will cause Mesa to require additional +memory. Furthermore, increasing these limits beyond <tt>4096</tt> +may introduce rasterization artifacts; see the leading comments in +<tt>src/mesa/swrast/s_tritemp.h</tt>. +</p> + <br> <br> |