All of lore.kernel.org
 help / color / mirror / Atom feed
From: Helmut Jarausch <jarausch@igpm.rwth-aachen.de>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: nouveau driver fails to build
Date: Fri, 23 Nov 2012 18:13:25 +0100	[thread overview]
Message-ID: <1353690805.30841.0@numa-i> (raw)
In-Reply-To: <1353684679.1420.7.camel@x61.thuisdomein>

On 11/23/2012 04:31:19 PM, Paul Bolle wrote:
> On Fri, 2012-11-23 at 15:42 +0100, Helmut Jarausch wrote:
> > with 3.7_rc6 and
> >
> > CONFIG_ACPI_VIDEO=m
> > CONFIG_DRM=y
> > CONFIG_DRM_KMS_HELPER=y
> > CONFIG_DRM_TTM=y
> > CONFIG_DRM_NOUVEAU=y
> > CONFIG_NOUVEAU_DEBUG=5
> > CONFIG_NOUVEAU_DEBUG_DEFAULT=3
> > CONFIG_DRM_NOUVEAU_BACKLIGHT=y
> >
> > with/ without
> > CONFIG_DRM_LOAD_EDID_FIRMWARE=y
> >
> >
> > The kernel fails to build with
> > drivers/built-in.o: In function `nouveau_acpi_edid':
> > (.text+0x12bf21): undefined reference to `acpi_video_get_edid'
> >
> >
> > What am I missing?
> 
> I'd guess it should build (at least without this error) with
> CONFIG_ACPI_VIDEO=y. Is that correct?

Yes, but this is very unnatural.

To get CONFIG_ACPI_VIDEO=y  I need to have VIDEO_OUTPUT_CONTROL=y
for which I have to select the Intel GMA500 Stub Driver although I don't
have such a device and therefore don't need that driver.
Furthermore, I had to chase through quite some flags to find this.

If it's not a bug, it's surprising, at least.

Thanks,
Helmut.


  reply	other threads:[~2012-11-23 17:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-23 14:42 nouveau driver fails to build Helmut Jarausch
2012-11-23 15:31 ` Paul Bolle
2012-11-23 17:13   ` Helmut Jarausch [this message]
2012-11-23 17:49     ` Paul Bolle
2012-12-09 17:05       ` Michal Marek

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=1353690805.30841.0@numa-i \
    --to=jarausch@igpm.rwth-aachen.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pebolle@tiscali.nl \
    /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.