On Tuesday, 9 November 2021 01:30:03 CET nerdopolis wrote: > +++ b/debian/config/kernelarch-x86/config > @@ -75,6 +75,7 @@ CONFIG_IA32_EMULATION=y > ## file: arch/x86/Kconfig.cpu > ## > # CONFIG_PROCESSOR_SELECT is not set > +CONFIG_X86_SYSFB=y
It is now in a different location and quoting the relevant part of the Kconfig
file for easier evaluation. 8633ef82f101c040427b57d4df7b706261420b94 seems to
be the commit that changed it.
~/dev/kernel.org/linux$ grep -A 28 "config SYSFB" drivers/firmware/Kconfig
config SYSFB
bool
select BOOT_VESA_SUPPORT
config SYSFB_SIMPLEFB
bool "Mark VGA/VBE/EFI FB as generic system framebuffer"
depends on X86 || EFI
select SYSFB
help
Firmwares often provide initial graphics framebuffers so the BIOS,
bootloader or kernel can show basic video-output during boot for
user-guidance and debugging. Historically, x86 used the VESA BIOS
Extensions and EFI-framebuffers for this, which are mostly limited
to x86 BIOS or EFI systems.
This option, if enabled, marks VGA/VBE/EFI framebuffers as generic
framebuffers so the new generic system-framebuffer drivers can be
used instead. If the framebuffer is not compatible with the generic
modes, it is advertised as fallback platform framebuffer so legacy
drivers like efifb, vesafb and uvesafb can pick it up.
If this option is not selected, all system framebuffers are always
marked as fallback platform framebuffers as usual.
Note: Legacy fbdev drivers, including vesafb, efifb, uvesafb, will
not be able to pick up generic system framebuffers if this option
is selected. You are highly encouraged to enable simplefb as
replacement if you select this option. simplefb can correctly deal
with generic system framebuffers. But you should still keep vesafb
and others enabled as fallback if a system framebuffer is
incompatible with simplefb.
If unsure, say Y.
signature.asc
Description: This is a digitally signed message part.
