diff options
| author | Tom Fogal <[email protected]> | 2009-08-13 19:51:57 -0600 |
|---|---|---|
| committer | Brian Paul <[email protected]> | 2009-08-14 08:58:59 -0600 |
| commit | 9a8781bd24730374e14568f67f7db8a9cc444bb4 (patch) | |
| tree | 2f6bc51b97c07d84ce19f35073e5a670ad67f0cf | |
| parent | 7085dce750f478312a47f474330d63cc900a8448 (diff) | |
Add a FAQ about internal buffer sizes.
| -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 11b5d432558..65e279aac57 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> |