At least the second patch somehow addresses the memory waste concern, the reservation will be very transient, during late init the BO will get freed. Andrey On 04/06/2018 08:26 AM, Christian König wrote: > I feared that you would say that :( > > In this case the patches are Acked-by: Christian König > <christian.koenig at amd.com>. > > Thanks, > Christian. > > Am 06.04.2018 um 13:23 schrieb Andrey Grodzovsky: >> >> 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 >> >> >> On 04/06/2018 04:30 AM, Christian König wrote: >>>> 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. >>> >>> 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. >> >> >> >> _______________________________________________ >> amd-gfx mailing list >> amd-gfx at lists.freedesktop.org >> https://lists.freedesktop.org/mailman/listinfo/amd-gfx > -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/amd-gfx/attachments/20180406/7385e665/attachment.html>
