From: James Hilliard <james.hilliard1@gmail.com>
To: dri-devel@lists.freedesktop.org
Cc: Randy Dunlap <rdunlap@infradead.org>,
James Hilliard <james.hilliard1@gmail.com>,
Patrik Jakobsson <patrik.r.jakobsson@gmail.com>,
David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
linux-kernel@vger.kernel.org
Subject: [PATCH v3] drm/gma500: depend on framebuffer
Date: Fri, 8 Apr 2022 22:23:21 -0600 [thread overview]
Message-ID: <20220409042321.3184493-1-james.hilliard1@gmail.com> (raw)
Select the efi framebuffer if efi is enabled.
This appears to be needed for video output to function correctly.
Signed-off-by: James Hilliard <james.hilliard1@gmail.com>
---
Changes v2 -> v3:
- select EFI_FB instead of depending on it
Changes v1 -> v2:
- use depends instead of select
---
drivers/gpu/drm/gma500/Kconfig | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/gpu/drm/gma500/Kconfig b/drivers/gpu/drm/gma500/Kconfig
index 0cff20265f97..a422fa84d53b 100644
--- a/drivers/gpu/drm/gma500/Kconfig
+++ b/drivers/gpu/drm/gma500/Kconfig
@@ -2,11 +2,13 @@
config DRM_GMA500
tristate "Intel GMA500/600/3600/3650 KMS Framebuffer"
depends on DRM && PCI && X86 && MMU
+ depends on FB
select DRM_KMS_HELPER
# GMA500 depends on ACPI_VIDEO when ACPI is enabled, just like i915
select ACPI_VIDEO if ACPI
select BACKLIGHT_CLASS_DEVICE if ACPI
select INPUT if ACPI
+ select FB_EFI if EFI
help
Say yes for an experimental 2D KMS framebuffer driver for the
Intel GMA500 (Poulsbo), Intel GMA600 (Moorestown/Oak Trail) and
--
2.25.1
next reply other threads:[~2022-04-09 4:23 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-09 4:23 James Hilliard [this message]
2022-04-09 4:33 ` Randy Dunlap
2022-04-10 19:36 ` Patrik Jakobsson
2022-04-10 19:40 ` James Hilliard
2022-04-10 19:52 ` Patrik Jakobsson
2022-04-10 20:05 ` James Hilliard
2022-04-11 9:27 ` Patrik Jakobsson
2022-04-12 1:47 ` James Hilliard
2022-04-12 8:29 ` Patrik Jakobsson
2022-04-19 23:42 ` James Hilliard
2022-04-21 11:10 ` Patrik Jakobsson
2022-04-21 11:49 ` Thomas Zimmermann
2022-04-21 12:39 ` Patrik Jakobsson
2022-04-21 12:47 ` Javier Martinez Canillas
2022-04-21 12:54 ` Patrik Jakobsson
2022-04-21 13:20 ` Thomas Zimmermann
2022-04-21 17:48 ` James Hilliard
2022-04-21 19:10 ` Patrik Jakobsson
2022-04-21 13:22 ` Javier Martinez Canillas
2022-04-21 17:39 ` James Hilliard
2022-04-21 18:22 ` Thomas Zimmermann
2022-04-21 18:23 ` Thomas Zimmermann
2022-04-21 18:24 ` James Hilliard
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=20220409042321.3184493-1-james.hilliard1@gmail.com \
--to=james.hilliard1@gmail.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patrik.r.jakobsson@gmail.com \
--cc=rdunlap@infradead.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
all inboxes | Powered by JetHome®