linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Simmons <jsimmons@infradead.org>
To: Jan Huijsmans <huysmans@xs4all.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test 2 & matroxfb or orinoco wifi card
Date: Tue, 29 Jul 2003 22:22:07 +0100 (BST)	[thread overview]
Message-ID: <Pine.LNX.4.44.0307292221130.5874-100000@phoenix.infradead.org> (raw)
In-Reply-To: <XFMail.20030729223514.huysmans@xs4all.nl>


> After digging a bit in the archives I couldn't find the solution to my problem,
> so I'm asking you guys.
> 
> I found the "matroxfb and 2.6.0-test2" thread, so it's possible to compile the
> kernel with the matrox framebuffer, but I can't find what I'm missing. Did I
> forget to set a config option (all copied from the 2.4.21 config except the
> nForce2 agp chipset)?
> 
> This is the error I'm getting while linking. 
> 
> drivers/built-in.o(.text+0x89c80): In function `matroxfb_set_par':
> : undefined reference to `default_grn'
> drivers/built-in.o(.text+0x89c85): In function `matroxfb_set_par':
> : undefined reference to `default_blu'
> drivers/built-in.o(.text+0x89c93): In function `matroxfb_set_par':
> : undefined reference to `color_table'
> drivers/built-in.o(.text+0x89c9b): In function `matroxfb_set_par':
> : undefined reference to `default_red'

Ug. There is a patch for that but it never got included. BTW this means 
you didn't turn on Framebuffer console. Please turn it on.



  reply	other threads:[~2003-07-29 21:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-29 20:35 2.6.0-test 2 & matroxfb or orinoco wifi card Jan Huijsmans
2003-07-29 21:22 ` James Simmons [this message]
2003-07-30 12:27 ` Adam Voigt
2003-07-29 20:37 Jan Huijsmans
2003-07-29 20:49 Petr Vandrovec
2003-07-29 21:31 ` Jan Huijsmans
2003-07-29 21:46 Petr Vandrovec

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=Pine.LNX.4.44.0307292221130.5874-100000@phoenix.infradead.org \
    --to=jsimmons@infradead.org \
    --cc=huysmans@xs4all.nl \
    --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;
as well as URLs for NNTP newsgroup(s).