firmware: google: framebuffer: Fix dependencies

The framebuffer on the coreboot bus represents an entry in the
coreboot payload table; not the actual device. [1] Hence it must
not depend on any other driver setting.

Signed-off-by: Thomas Zimmermann <tzimmermann@suse.de>
Link: https://lore.kernel.org/dri-devel/CAODwPW9_ym3E4za3yoUAs0+1sQfaKTDOau4Oh9Zm8+2uvYVgFQ@mail.gmail.com/ # [1]
Acked-by: Tzung-Bi Shih <tzungbi@kernel.org>
Acked-by: Julius Werner <jwerner@chromium.org>
Link: https://patch.msgid.link/20260217155836.96267-6-tzimmermann@suse.de
This commit is contained in:
Thomas Zimmermann
2026-02-17 16:56:15 +01:00
parent 0d847e16ca
commit 73d8aa63b2

View File

@@ -59,11 +59,11 @@ config GOOGLE_MEMCONSOLE_X86_LEGACY
config GOOGLE_FRAMEBUFFER_COREBOOT
tristate "Coreboot Framebuffer"
depends on FB_SIMPLE || DRM_SIMPLEDRM
depends on GOOGLE_COREBOOT_TABLE
help
This option enables the kernel to search for a framebuffer in
the coreboot table. If found, it is registered with simplefb.
the coreboot table. If found, it is registered with a platform
device of type simple-framebuffer.
config GOOGLE_MEMCONSOLE_COREBOOT
tristate "Firmware Memory Console"