public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Soeren Sonnenburg <sonne@debian.org>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: [PATCH] resolving Re: 2.6.30-rc3 still fails to build in intel_opregion_init
Date: Sun, 26 Apr 2009 17:53:51 +0200	[thread overview]
Message-ID: <1240761231.5513.3.camel@localhost> (raw)
In-Reply-To: <1240608012.5488.0.camel@localhost>

On Fri, 2009-04-24 at 23:20 +0200, Soeren Sonnenburg wrote:
> still the same thing...
> 
>   MODPOST vmlinux.o
> WARNING: modpost: Found 1 section mismatch(es).
> To see full details build your kernel with:
> 'make CONFIG_DEBUG_SECTION_MISMATCH=y'
>   GEN     .version
>   CHK     include/linux/compile.h
>   UPD     include/linux/compile.h
>   CC      init/version.o
>   LD      init/built-in.o
>   LD      .tmp_vmlinux1
> drivers/built-in.o: In function `intel_opregion_init':
> (.text+0xcf239): undefined reference to `acpi_video_register'
> make: *** [.tmp_vmlinux1] Error 1

Argh, looks like one could select ACPI_VIDEO to be build as module
though DRM_I915 requires it to be compiled inside, so I guess this patch
should fix things:

Signed-off-by: Soeren Sonnenburg <sonne@debian.org>

diff --git a/drivers/gpu/drm/Kconfig b/drivers/gpu/drm/Kconfig
index 3a22eb9..71ebf04 100644
--- a/drivers/gpu/drm/Kconfig
+++ b/drivers/gpu/drm/Kconfig
@@ -71,6 +71,7 @@ config DRM_I915
 	select FB_CFB_COPYAREA
 	select FB_CFB_IMAGEBLIT
 	select FB
+	select ACPI_VIDEO
 	tristate "i915 driver"
 	help
 	  Choose this option if you have a system that has Intel 830M, 845G,


-- 
For the one fact about the future of which we can be certain is that it
will be utterly fantastic. -- Arthur C. Clarke, 1962

      reply	other threads:[~2009-04-26 15:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-24 21:20 2.6.30-rc3 still fails to build Soeren Sonnenburg
2009-04-26 15:53 ` Soeren Sonnenburg [this message]

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=1240761231.5513.3.camel@localhost \
    --to=sonne@debian.org \
    --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