From: Roland Dreier <rdreier@cisco.com>
To: Miles Lane <miles.lane@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Ben Skeggs <bskeggs@redhat.com>,
Maarten Maathuis <madman2003@gmail.com>
Subject: Re: 2.6.36-rc8 -- drivers/built-in.o: In function `nouveau_acpi_edid': (.text+0xf7c04): undefined reference to `acpi_video_get_edid'
Date: Sat, 16 Oct 2010 13:58:50 -0700 [thread overview]
Message-ID: <adad3r9hn1x.fsf@cisco.com> (raw)
In-Reply-To: <AANLkTik8pvkueU8YyUwjODz53QnurUqKycaTYJ-McYqB@mail.gmail.com> (Miles Lane's message of "Thu, 14 Oct 2010 22:46:51 -0400")
> drivers/built-in.o: In function `nouveau_acpi_edid':
> (.text+0xf7c04): undefined reference to `acpi_video_get_edid'
> make: *** [.tmp_vmlinux1] Error 1
The problem is:
> CONFIG_ACPI=y
> CONFIG_ACPI_VIDEO=m
but
> CONFIG_DRM_NOUVEAU=y
So the built-in nouveau code tries to reference the modular acpi video
code. I'm not sure what the correct fix is... does the following make
things work?
drivers/gpu/drm/nouveau/Makefile | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/gpu/drm/nouveau/Makefile b/drivers/gpu/drm/nouveau/Makefile
index e9b06e4..4e295b5 100644
--- a/drivers/gpu/drm/nouveau/Makefile
+++ b/drivers/gpu/drm/nouveau/Makefile
@@ -28,6 +28,6 @@ nouveau-y := nouveau_drv.o nouveau_state.o nouveau_channel.o nouveau_mem.o \
nouveau-$(CONFIG_DRM_NOUVEAU_DEBUG) += nouveau_debugfs.o
nouveau-$(CONFIG_COMPAT) += nouveau_ioc32.o
nouveau-$(CONFIG_DRM_NOUVEAU_BACKLIGHT) += nouveau_backlight.o
-nouveau-$(CONFIG_ACPI) += nouveau_acpi.o
+nouveau-$(CONFIG_ACPI_VIDEO) += nouveau_acpi.o
obj-$(CONFIG_DRM_NOUVEAU)+= nouveau.o
next prev parent reply other threads:[~2010-10-16 20:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-15 2:46 2.6.36-rc8 -- drivers/built-in.o: In function `nouveau_acpi_edid': (.text+0xf7c04): undefined reference to `acpi_video_get_edid' Miles Lane
2010-10-16 20:58 ` Roland Dreier [this message]
2010-10-17 1:00 ` Miles Lane
2010-10-17 1:33 ` Roland Dreier
2010-10-17 3:50 ` Miles Lane
2010-10-17 7:18 ` Sven Joachim
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=adad3r9hn1x.fsf@cisco.com \
--to=rdreier@cisco.com \
--cc=bskeggs@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=madman2003@gmail.com \
--cc=miles.lane@gmail.com \
/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