[PATCH v4 1/3] sysfb: Make config option dependencies explicit

efifb and vesafb requires sysfb implicitly but this is not stated in Kconfig. Add the dependency. With that all drivers that require sysfb depend on it so it can default to disabled. Signed-off-by: Michal Suchanek --- v4: new patch --- drivers/firmware/Kconfig| 5 ++--- drivers/video/fbdev

[PATCH v4 3/3] efifb: Remove redundant efifb_setup_from_dmi stub

efifb is the only user of efifb_setup_from_dmi which is provided by sysfb which is selected by efifb. That makes the stub redundant. Signed-off-by: Michal Suchanek --- v4: new patch --- include/linux/efi.h | 4 1 file changed, 4 deletions(-) diff --git a/include/linux/efi.h b/include

[PATCH v4 2/3] sysfb: Enable boot time VESA graphic mode selection

from fbdev to x86 Kconfig. Fixes: e3263ab389a7 ("x86: provide platform-devices for boot-framebuffers") Signed-off-by: Michal Suchanek Acked-by: Borislav Petkov --- v2: Select BOOT_VESA_SUPPORT from simplefb rather than simpledrm. The simpledrm driver uses the firmware provided video

[PATCH v3] simplefb: Enable boot time VESA graphic mode selection.

ned-off-by: Michal Suchanek --- v2: Select BOOT_VESA_SUPPORT from simplefb rather than simpledrm. The simpledrm driver uses the firmware provided video modes only indirectly through simplefb, and both can be enabled independently. v3: Move BOOT_VESA_SUPPORT from fbdev to x86 --- arch/x

[PATCH v2] simplefb: Enable boot time VESA graphic mode selection.

BOOT_VESA_SUPPORT on FB, also drop the FB_ prefix, and select the option when simpledrm is built-in on x86. Fixes: e3263ab389a7 ("x86: provide platform-devices for boot-framebuffers") Signed-off-by: Michal Suchanek --- v2: Select BOOT_VESA_SUPPORT from simplefb rather than simpledrm. The simple

[PATCH] simpldrm: Enable boot time VESA graphic mode selection.

on FB, also drop the FB_ prefix, and select the option when simpledrm is built-in on x86. Fixes: 11e8f5fd223b ("drm: Add simpledrm driver") Signed-off-by: Michal Suchanek --- arch/x86/boot/video-vesa.c | 4 ++-- drivers/gpu/drm/tiny/Kconfig | 1 + drivers/video/fbdev/Kconfig | 9 ++

[PATCH] drm/amdgpu/dc: Really fix DCN3.1 Makefile for PPC64

Also copy over the part that makes old gcc handling cross-platform. Fixes: df7a1658f257 ("drm/amdgpu/dc: fix DCN3.1 Makefile for PPC64") Fixes: 926d6972efb6 ("drm/amd/display: Add DCN3.1 blocks to the DC Makefile") Signed-off-by: Michal Suchanek --- The fact that the old gcc

Exynos Snow board display regression

On 29 January 2016 at 18:18, Javier Martinez Canillas wrote: > Hello Michal, > > On 01/29/2016 02:07 PM, Michal Suchanek wrote: >> >> Hello, >> >> after commit a9fa852886fd5a7ccec3b7e9eff75f85072f009c >> >> display no longer works on the Snow boa

Exynos Snow board display regression

Hello, after commit a9fa852886fd5a7ccec3b7e9eff75f85072f009c display no longer works on the Snow board. The built-in panel is no longer probed. The commit *supposedly* provides for backwards compatibility and at first glance only new options for probing the panel are added. However, reverting

Future desktop on dumb frame buffers?

On 21 March 2011 20:25, Jesse Barnes wrote: > On Mon, 21 Mar 2011 19:19:43 + > timofonic timofonic wrote: >> So if KMS is so cool and provides many advantages over fbdev and >> such... Why isn't more widely used intead of still relying on fbdev? >> Why still using fbdev emulation (that is par

Re: Future desktop on dumb frame buffers?

On 21 March 2011 20:25, Jesse Barnes wrote: > On Mon, 21 Mar 2011 19:19:43 + > timofonic timofonic wrote: >> So if KMS is so cool and provides many advantages over fbdev and >> such... Why isn't more widely used intead of still relying on fbdev? >> Why still using fbdev emulation (that is par