<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED NOTOURBUG - Using 2 screens impossible again with gen3" href="https://bugs.freedesktop.org/show_bug.cgi?id=67846#c6">Comment # 6</a> on <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED NOTOURBUG - Using 2 screens impossible again with gen3" href="https://bugs.freedesktop.org/show_bug.cgi?id=67846">bug 67846</a> from <a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> Chris Wilson</a> <pre>xrandr actually reports that the maximum fb size is 32k by 32k because the hardware doesn't impose any such limitation on the fb. Individual CRTCs are pruned to fit in the 4096x4096 hw limit of the pipes (and modes are pruned in case they advertise a mode too large for an individual CRTC or too be able to fit into memory). All this can be hardware accelerated even though the 3D pipeline is limited to maximum coordinate values of 2048x2048 (most operations do not exceed 2048x2048 and those that do can be tiled). Unity however has to respect the GL limits, which I think at the moment report a maximum framebuffer size of 4096x4096. Leading to the hilarity you have discovered. I share the opinion of the GL team, that one should not use GL in any system critical component.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>