From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Ken Offer <koffer@arlut.utexas.edu>
Cc: Jens Schmalzing <jens.schmalzing@physik.uni-muenchen.de>,
linuxppcdev <linuxppc-dev@lists.linuxppc.org>
Subject: Re: Need a Linux PPC kernel which supports the Radeon Mobility 9600
Date: Wed, 15 Oct 2003 10:19:16 +0200 [thread overview]
Message-ID: <1066205955.644.55.camel@gaston> (raw)
In-Reply-To: <40CB1A40-FE93-11D7-AB64-000393467F1A@arlut.utexas.edu>
> Hi Jens,
>
> I'm trying that myself, but I'm running into undefined symbols, plus
> problems with compiling PCNET32 (whatever that is).
>
> I started with the ".config" file copied from
> "arch/ppc/configs/pmac_defconfig", but that might not be the best. I'm
> not sure how all the creative config names map to specific machines,
> like the PowerBook.
>
> What config file did you compile 2.5-benh with?
The pmac_defconfig should be correct. pcnet32 is known to have problems
in current 2.6 though, just disable it. What undefined symbols do you
have ?
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-10-15 8:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-14 22:10 Need a Linux PPC kernel which supports the Radeon Mobility 9600 Ken Offer
2003-10-15 8:19 ` Benjamin Herrenschmidt [this message]
2003-10-15 15:09 ` Ken Offer
2003-10-15 15:22 ` Benjamin Herrenschmidt
2003-10-16 14:37 ` Ken Offer
2003-10-16 15:24 ` Benjamin Herrenschmidt
-- strict thread matches above, loose matches on Subject: below --
2003-10-10 21:56 Ken Offer
2003-10-10 22:07 ` Benjamin Herrenschmidt
2003-10-11 21:44 ` Jens Schmalzing
2003-10-12 10:07 ` Benjamin Herrenschmidt
2003-10-12 11:10 ` Sam Ravnborg
2003-10-12 12:18 ` Jens Schmalzing
2003-10-12 16:17 ` Dale Harris
2003-10-14 14:37 ` Ken Offer
2003-10-14 15:14 ` Jens Schmalzing
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=1066205955.644.55.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=jens.schmalzing@physik.uni-muenchen.de \
--cc=koffer@arlut.utexas.edu \
--cc=linuxppc-dev@lists.linuxppc.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).