From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Rahul Jain <rahul@rice.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: radeonfb.c has lots of undefined symbols
Date: 29 Dec 2002 14:30:25 +0100 [thread overview]
Message-ID: <1041168625.526.20.camel@zion> (raw)
In-Reply-To: <87hecxfhnf.fsf@localhost.localdomain>
On Sun, 2002-12-29 at 07:44, Rahul Jain wrote:
> I just decided to make the leap to 2.5, and in the process of compiling,
> I hit a bug: Many of the PCI IDs are defined as .._RADEON_.. instead of
> .._ATI_RADEON_.. as radeonfb.c has them and others aren't even defined
> in any way that I can see. Also, there are a few other undefined symbols
> in there. I don't use console much, so I just disabled the driver, but
> I'm sure some people would appreciate if the driver at least
> compiled. :)
I have a fixed version in PPC 2.5 tree
(bk://ppc.bkbits.net/linuxppc-2.5), I'll eventually send it myself to
Linus if Ani (the maintainer) don't do it.
Ben.
next prev parent reply other threads:[~2002-12-29 13:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.c8kskov.1c0eqjr@ifi.uio.no>
2002-12-29 6:44 ` radeonfb.c has lots of undefined symbols Rahul Jain
2002-12-29 13:30 ` Benjamin Herrenschmidt [this message]
2002-12-29 17:11 ` James Simmons
2002-12-29 17:10 ` James Simmons
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=1041168625.526.20.camel@zion \
--to=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rahul@rice.edu \
/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