Commit 93b7eea6 authored by Nerdopolis Turfwalker's avatar Nerdopolis Turfwalker Committed by Vlad Zahorodnii

[platforms/fbdev] Use a better way to correct activating framebuffer devices

My change in 304528e8 has been reported to
cause issues for PostMarketOS
I originally submitted the change to activate Framebuffer devices
as secondary framebuffer devices are not on by default, (such as a
secondary DisplayLink device). Changing attributes usually forced
some framebuffer devices to turn on, however I have found a more
accurate way to turn on framebuffer devices, without messing with
the color layout.

Reviewers: #kwin, davidedmundson, graesslin, zzag

Reviewed By: #kwin, zzag

Subscribers: kwin

Tags: #kwin

Differential Revision:
parent f740aa2e
......@@ -126,20 +126,8 @@ bool FramebufferBackend::handleScreenInfo()
return false;
// correct the color info, and try to turn on screens, assuming this is a non-primary framebuffer device
varinfo.grayscale = 0;
varinfo.transp.offset = 24;
varinfo.transp.length = 8;
varinfo.transp.msb_right = 0; = 16; = 8; = 0; = 8; = 8; = 0; = 0; = 8; = 0;
// Activate the framebuffer device, assuming this is a non-primary framebuffer device
ioctl(m_fd, FBIOPUT_VSCREENINFO, &varinfo);
// Probe the device for new screen information.
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment