From: Jiri Slaby <jslaby@suse.cz>
To: Dave Airlie <airlied@redhat.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
dri-devel@lists.freedesktop.org, Jiri Slaby <jirislaby@gmail.com>
Subject: [-next] DRM_CIRRUS_QEMU breaks build
Date: Sun, 20 May 2012 00:23:14 +0200 [thread overview]
Message-ID: <4FB81D52.5050106@suse.cz> (raw)
Hi,
when that option is selected to be Y, I'm getting linking errors like:
(.text+0xefd8d): undefined reference to `ttm_tt_init'
drivers/built-in.o: In function `cirrus_mm_init':
and many others, like undefined sys_fillrect.
You perhaps have a patch on your queue already and I need not to turn
this into a patch, right :):
--- a/drivers/gpu/drm/cirrus/Kconfig
+++ b/drivers/gpu/drm/cirrus/Kconfig
@@ -1,10 +1,11 @@
config DRM_CIRRUS_QEMU
tristate "Cirrus driver for QEMU emulated device"
depends on DRM && PCI && EXPERIMENTAL
- select FB_CFB_FILLRECT
- select FB_CFB_COPYAREA
- select FB_CFB_IMAGEBLIT
+ select FB_SYS_FILLRECT
+ select FB_SYS_COPYAREA
+ select FB_SYS_IMAGEBLIT
select DRM_KMS_HELPER
+ select DRM_TTM
help
This is a KMS driver for emulated cirrus device in qemu.
It is *NOT* intended for real cirrus devices. This requires
regards,
--
js
suse labs
reply other threads:[~2012-05-19 22:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4FB81D52.5050106@suse.cz \
--to=jslaby@suse.cz \
--cc=airlied@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jirislaby@gmail.com \
--cc=linux-kernel@vger.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