diff options
| author | Emil Velikov <[email protected]> | 2015-04-02 08:37:12 +0000 |
|---|---|---|
| committer | Emil Velikov <[email protected]> | 2015-04-12 23:14:07 +0100 |
| commit | 61c6cc4a4aa23724bd51089b38741feed67617bc (patch) | |
| tree | 00960da9f2c4660c6148fc1fae8257daa2e8ec67 | |
| parent | 0e742b1cb39c0df5846068d36c4f32c126b83fac (diff) | |
docs: remove the --with-max-{width,height} note
Missed out with commit d99135b2e9b(configure: nuke
--with-max-{width,height})
Signed-off-by: Emil Velikov <[email protected]>
Reviewed-by: Brian Paul <[email protected]>
| -rw-r--r-- | docs/faq.html | 13 |
1 files changed, 0 insertions, 13 deletions
diff --git a/docs/faq.html b/docs/faq.html index d4037e83c08..b7c6fbf8a9c 100644 --- a/docs/faq.html +++ b/docs/faq.html @@ -327,19 +327,6 @@ 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> |