From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: intel-xe@lists.freedesktop.org
Subject: [Intel-xe] [RFC PATCH] drm/xe/display: Select some missing configs
Date: Fri, 15 Sep 2023 20:06:10 +0200 [thread overview]
Message-ID: <20230915180610.39266-1-thomas.hellstrom@linux.intel.com> (raw)
When selecting CONFIG_XE_DISPLAY, the following missing symbols can be
seen unless something else has selected the corresponding configs.
ERROR: modpost: "cfb_copyarea" [drivers/gpu/drm/xe/xe.ko] undefined!
ERROR: modpost: "cfb_fillrect" [drivers/gpu/drm/xe/xe.ko] undefined!
ERROR: modpost: "cfb_imageblit" [drivers/gpu/drm/xe/xe.ko] undefined
Make sure these are included in the Xe Display build.
Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Signed-off-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>
---
drivers/gpu/drm/xe/Kconfig | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/gpu/drm/xe/Kconfig b/drivers/gpu/drm/xe/Kconfig
index 096bd066afa8..ed2dd73f153b 100644
--- a/drivers/gpu/drm/xe/Kconfig
+++ b/drivers/gpu/drm/xe/Kconfig
@@ -45,6 +45,9 @@ config DRM_XE
config DRM_XE_DISPLAY
bool "Enable display support"
depends on DRM_XE && EXPERT
+ select FB_CFB_COPYAREA
+ select FB_CFB_FILLRECT
+ select FB_CFB_IMAGEBLIT
select I2C
select I2C_ALGOBIT
default y
--
2.41.0
next reply other threads:[~2023-09-15 18:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-15 18:06 Thomas Hellström [this message]
2023-09-15 19:43 ` [Intel-xe] ✓ CI.Patch_applied: success for drm/xe/display: Select some missing configs Patchwork
2023-09-15 19:43 ` [Intel-xe] ✓ CI.checkpatch: " Patchwork
2023-09-15 19:44 ` [Intel-xe] ✓ CI.KUnit: " Patchwork
2023-09-15 19:51 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-09-15 19:51 ` [Intel-xe] ✗ CI.Hooks: failure " Patchwork
2023-09-15 19:53 ` [Intel-xe] ✓ CI.checksparse: success " Patchwork
2023-09-15 20:24 ` [Intel-xe] ✓ CI.BAT: " Patchwork
2023-09-18 14:17 ` [Intel-xe] [RFC PATCH] " Maarten Lankhorst
2023-09-18 14:18 ` Thomas Hellström
2023-09-18 15:42 ` Lucas De Marchi
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=20230915180610.39266-1-thomas.hellstrom@linux.intel.com \
--to=thomas.hellstrom@linux.intel.com \
--cc=intel-xe@lists.freedesktop.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.