On Wed, Jan 04, 2017 at 12:38:04AM -0800, St??phane Marchesin wrote: > On Wed, Jan 4, 2017 at 12:30 AM, Daniel Vetter <daniel@xxxxxxxx> wrote: > > On Wed, Dec 21, 2016 at 12:13:06PM -0600, vcaputo@xxxxxxxxxxx wrote: > >> Hello list, > >> > >> I've been playing with an unaccelerated drm program[1] and have been > >> annoyed that whenever this program exits the fbcon isn't restored, with > >> the display left completely off. > >> > >> This seems to happen because Xorg is still running from a different VT. > >> > >> Upon further investigation, it seems like the fb restore only occurs on > >> "lastclose", which explains what I'm observing. > >> > >> Why don't we perform the fb restore whenever the current master is > >> closed to cover this case, since masters are the ones that can change > >> modes? > > One case where it's useful not to do this is the handoff from a splash > screen to a display server. > If the handoff is avoiding the existing lastclose semantics somehow by having overlapping opens, couldn't drmDropMaster() be employed to avoid the masterclose restore when the splash screen closes? Regards, Vito Caputo _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
