loongarch: kernel: Remove references to VESA

We don't have VESA.
This commit is contained in:
Xi Ruoyao 2025-02-18 23:49:56 +08:00
parent 10dd2f4b51
commit c18b8a7cc0
No known key found for this signature in database
GPG Key ID: ACAAD20E19E710E3

View File

@ -273,7 +273,7 @@
on panic. As of Linux-6.12, none of the dedicated drivers for on panic. As of Linux-6.12, none of the dedicated drivers for
mainstream GPU models really supports this, but it's supported by mainstream GPU models really supports this, but it's supported by
the <quote>Simple framebuffer driver</quote> which runs on the the <quote>Simple framebuffer driver</quote> which runs on the
VESA (or EFI) framebuffer before the dedicated GPU driver is EFI framebuffer before the dedicated GPU driver is
loaded. If the dedicated GPU driver is built as a module loaded. If the dedicated GPU driver is built as a module
(instead of a part of the kernel image) and no initramfs is (instead of a part of the kernel image) and no initramfs is
used, this functionality will work just fine before the root used, this functionality will work just fine before the root
@ -312,10 +312,9 @@
<parameter>Simple framebuffer driver</parameter> <parameter>Simple framebuffer driver</parameter>
</term> </term>
<listitem> <listitem>
<para>These allow to use the VESA framebuffer (or the EFI <para>These allow to use the EFI framebuffer as a DRM device.
framebuffer if booting the LFS system via UEFI) as a DRM device. The EFI
The VESA framebuffer will be set up by GRUB (or the EFI framebuffer will be set up by the UEFI firmware, so the DRM panic
framebuffer will be set up by the UEFI firmware), so the DRM panic
handler can function before the GPU-specific DRM driver is handler can function before the GPU-specific DRM driver is
loaded.</para> loaded.</para>
</listitem> </listitem>