<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> </head> <body text="#000000" bgcolor="#FFFFFF"> <div class="moz-cite-prefix">I feared that you would say that :( In this case the patches are Acked-by: Christian König <a class="moz-txt-link-rfc2396E" href="mailto:christian.koenig@amd.com"><christian.koenig@amd.com></a>. Thanks, Christian. Am 06.04.2018 um 13:23 schrieb Andrey Grodzovsky: </div> <blockquote type="cite" cite="mid:40be8e12-8f2e-449f-d09e-aa46aa396f4c@amd.com"> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> Me and Alex talked to a BIOS guys yesterday exactly about that, a dynamic way to query this info from BIOS, he just told us to reserve 32M to cover 4K display. Andrey <div class="moz-cite-prefix">On 04/06/2018 04:30 AM, Christian König wrote: </div> <blockquote type="cite" cite="mid:1c6e6260-10cf-f189-45b3-74fd2d1c991c@gmail.com"> <blockquote type="cite" style="color: #000000;">I wonder if there's no way to determine which part of VRAM is being scanned out. If there was, we could just create a normal BO covering that, which would get destroyed once no CRTC references it anymore. </blockquote> Unfortunately it goes further than that. The stolen VRAM is needed for VGA emulation, not only for scanout. But yes I agree that we somehow figure that value out from the BIOS. If I'm not completely mistaken I've also seen some atombios table with that info in some discussion. Christian. </blockquote> <fieldset class="mimeAttachmentHeader"></fieldset> <pre wrap="">_______________________________________________ amd-gfx mailing list <a class="moz-txt-link-abbreviated" href="mailto:amd-gfx@lists.freedesktop.org">amd-gfx@lists.freedesktop.org</a> <a class="moz-txt-link-freetext" href="https://lists.freedesktop.org/mailman/listinfo/amd-gfx">https://lists.freedesktop.org/mailman/listinfo/amd-gfx</a> </pre> </blockquote> </body> </html>