diff options
author | Ian Romanick <ian.d.romanick@intel.com> | 2009-08-18 12:20:36 -0700 |
---|---|---|
committer | Ian Romanick <ian.d.romanick@intel.com> | 2009-08-18 12:20:36 -0700 |
commit | a512985fd81c1ed4ccc5e69aaa05015cf7ff844d (patch) | |
tree | 69e6e898deaeaed2b4dfb5851707c68261c464de /docs/faq.html | |
parent | 0b5af41c6fae2809f4567a7cecbd207e5e4f3ab5 (diff) | |
parent | c80bc3abcd3939e5e2d45aea4b01ff22bfec244b (diff) |
Merge branch 'master' into asm-shader-rework-1
Conflicts:
src/mesa/shader/arbprogparse.c
Diffstat (limited to 'docs/faq.html')
-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> |