From: Thomas Zimmermann <tzimmermann@suse.de>
To: tzungbi@kernel.org, briannorris@chromium.org,
jwerner@chromium.org, javierm@redhat.com, samuel@sholland.org,
maarten.lankhorst@linux.intel.com, mripard@kernel.org,
airlied@gmail.com, simona@ffwll.ch
Cc: chrome-platform@lists.linux.dev, dri-devel@lists.freedesktop.org,
Thomas Zimmermann <tzimmermann@suse.de>
Subject: [PATCH v4 05/12] firmware: google: framebuffer: Fix dependencies
Date: Tue, 17 Feb 2026 16:56:15 +0100 [thread overview]
Message-ID: <20260217155836.96267-6-tzimmermann@suse.de> (raw)
In-Reply-To: <20260217155836.96267-1-tzimmermann@suse.de>
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>
---
drivers/firmware/google/Kconfig | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/firmware/google/Kconfig b/drivers/firmware/google/Kconfig
index 41b78f5cb735..3ab3e089328b 100644
--- a/drivers/firmware/google/Kconfig
+++ b/drivers/firmware/google/Kconfig
@@ -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"
--
2.52.0
next prev parent reply other threads:[~2026-02-17 15:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-17 15:56 [PATCH v4 00/12] drm, coreboot: Add DRM coreboot driver Thomas Zimmermann
2026-02-17 15:56 ` [PATCH v4 01/12] firmware: google: framebuffer: Do not unregister platform device Thomas Zimmermann
2026-02-17 15:56 ` [PATCH v4 02/12] firmware: google: framebuffer: Do not mark framebuffer as busy Thomas Zimmermann
2026-02-17 15:56 ` [PATCH v4 03/12] firmware: google: framebuffer: Init memory resource with helper macro Thomas Zimmermann
2026-02-17 15:56 ` [PATCH v4 04/12] firmware: google: framebuffer: Tie platform device to PCI hardware Thomas Zimmermann
2026-02-17 15:56 ` Thomas Zimmermann [this message]
2026-02-17 15:56 ` [PATCH v4 06/12] firmware: google: Init coreboot bus with subsys_initcall() Thomas Zimmermann
2026-02-17 15:56 ` [PATCH v4 07/12] firmware: google: Clean up include statements in coreboot_table.h Thomas Zimmermann
2026-02-17 15:56 ` [PATCH v4 08/12] firmware: google: Export coreboot table entries Thomas Zimmermann
2026-02-17 15:56 ` [PATCH v4 09/12] firmware: google: Pack structures for " Thomas Zimmermann
2026-02-17 15:56 ` [PATCH v4 10/12] drm/sysfb: Generalize pixel-format matching Thomas Zimmermann
2026-02-17 15:56 ` [PATCH v4 11/12] drm/sysfb: corebootdrm: Add DRM driver for coreboot framebuffers Thomas Zimmermann
2026-02-17 15:56 ` [PATCH v4 12/12] drm/sysfb: corebootdrm: Support panel orientation Thomas Zimmermann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260217155836.96267-6-tzimmermann@suse.de \
--to=tzimmermann@suse.de \
--cc=airlied@gmail.com \
--cc=briannorris@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=dri-devel@lists.freedesktop.org \
--cc=javierm@redhat.com \
--cc=jwerner@chromium.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=samuel@sholland.org \
--cc=simona@ffwll.ch \
--cc=tzungbi@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox