You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Increase screen pixmap size beyond initial video RAM if needed
If FBBase is not backed by grant tables, it's now possible to reallocate
it. This is especially useful when new external display is connected and
the overall resolution is increased.
Note the realloc() call may change FBBase address. In practice, FBBase
is given to fbScreenInit, and it does save it at some point
(fbScreenInit->fbFinishScreenInit->miScreenInit->miScreenDevPrivateInit),
but then it's used only to attach it to the screen pixmap, which is
updated via ModifyPixmapHeader() call few lines below anyway.
Another place where it's used is DUMMY_OpenFramebuffer() and
DUMMYDGAInit(). Avoid issues there by enabling DGA extension only if
FBBase is backed by grant tables, so it won't be moved. DGA extension
seems to be useless in purely virtual case anyway, as the framebuffer
isn't displayed anywhere.
This change adjusts also pScrn->videoRam. But fortunately X server seems
to use it only at startup, and only to validate initial modes list.
FixesQubesOS/qubes-issues#7448
0 commit comments