linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Michel Angelo da Silva Pereira <michel@michel.eti.br>
Cc: linux-kernel@vger.kernel.org,
	Denis Oliver Kropp <dok@directfb.org>,
	jsimmons@infradead.org, geert@linux-m68k.org,
	linux-fbdev-devel@lists.sourceforge.net
Subject: Re: drivers/built-in.o(.text+0x1411f): In function `neo_scan_monitor
Date: Sun, 10 Oct 2004 01:36:42 +0200	[thread overview]
Message-ID: <20041009233641.GB3727@stusta.de> (raw)
In-Reply-To: <415B2974.2020208@michel.eti.br>

On Wed, Sep 29, 2004 at 06:30:28PM -0300, Michel Angelo da Silva Pereira wrote:

> 	I'm getting this error on compiling 2.6.9-rc2 with FrameBuffer 
> 	support for my ThinkPad.
> 	01:00.0 VGA compatible controller: Neomagic Corporation NM2200 
> 	[MagicGraph 256AV] (rev 20)
> 
>   LD      .tmp_vmlinux1
> drivers/built-in.o(.text+0x1411f): In function `neo_scan_monitor':
> : undefined reference to `vesa_modes'
> drivers/built-in.o(.text+0x141bf): In function `neo_scan_monitor':
> : undefined reference to `vesa_modes'
> drivers/built-in.o(.text+0x1420b): In function `neo_scan_monitor':
> : undefined reference to `vesa_modes'
> make: ** [.tmp_vmlinux1] Erro 1
> root@nerdbook:/usr/src/linux#


Thanks for this report!

This is a bug still present in both 2.6.9-rc3 and 2.6.9-rc3-mm3.

The following patch should fix it:


Signed-off-by: Adrian Bunk <bunk@stusta.de>

--- linux-2.6.9-rc3-mm3/drivers/video/Kconfig.old	2004-10-10 01:31:52.000000000 +0200
+++ linux-2.6.9-rc3-mm3/drivers/video/Kconfig	2004-10-10 01:32:26.000000000 +0200
@@ -793,6 +793,7 @@
 config FB_NEOMAGIC
 	tristate "NeoMagic display support"
 	depends on FB && PCI
+	select FB_MODE_HELPERS
 	help
 	  This driver supports notebooks with NeoMagic PCI chips.
 	  Say Y if you have such a graphics card. 

           reply	other threads:[~2004-10-09 23:36 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <415B2974.2020208@michel.eti.br>]

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=20041009233641.GB3727@stusta.de \
    --to=bunk@stusta.de \
    --cc=dok@directfb.org \
    --cc=geert@linux-m68k.org \
    --cc=jsimmons@infradead.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michel@michel.eti.br \
    /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;
as well as URLs for NNTP newsgroup(s).