From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: "Carlos R. Mafra" <crmafra2@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.36-rc2 drm compilation failure
Date: Mon, 23 Aug 2010 08:48:37 -0700 [thread overview]
Message-ID: <20100823084837.2f181fdd@virtuousgeek.org> (raw)
In-Reply-To: <20100823113248.GA18594@Pilar.aei.mpg.de>
On Mon, 23 Aug 2010 13:32:48 +0200
"Carlos R. Mafra" <crmafra2@gmail.com> wrote:
> The compilation of 2.6.36-rc2 fails with the following error
>
> LD .tmp_vmlinux1
> drivers/built-in.o: In function `vga_get_uninterruptible':
> /home/mafra/linux-2.6/include/linux/vgaarb.h:120: undefined reference to `vga_get'
> drivers/built-in.o: In function `i915_disable_vga':
> /home/mafra/linux-2.6/drivers/gpu/drm/i915/intel_display.c:5990: undefined reference to `vga_put'
> make[1]: *** [.tmp_vmlinux1] Fehler 1
> make: *** [sub-make] Fehler 2
>
> but 2.6.36-rc1 compiled fine.
>
> The machine is a Vaio 64-bit laptop with
>
> VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller
>
> and my .config has
>
> CONFIG_DRM_I915=y
> CONFIG_DRM_I915_KMS=y
>
> but also
>
> # CONFIG_VGA_ARB is not set
>
> I guess the following commit introduced the error 9cce37f4855a30cc
> ("drm/i915: fix VGA plane disable for Ironlake+").
>
> If there's any other information I should provide, please let me know.
Ah so we need to select VGA arb or make sure stubs are provided
for !VGA_ARB configs.
--
Jesse Barnes, Intel Open Source Technology Center
next prev parent reply other threads:[~2010-08-23 15:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-23 11:32 2.6.36-rc2 drm compilation failure Carlos R. Mafra
2010-08-23 15:48 ` Jesse Barnes [this message]
2010-08-23 23:22 ` Jesse Barnes
2010-08-23 23:49 ` Carlos R. Mafra
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=20100823084837.2f181fdd@virtuousgeek.org \
--to=jbarnes@virtuousgeek.org \
--cc=crmafra2@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