From: Sam Ravnborg <sam@ravnborg.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Jens Schmalzing <jens.schmalzing@physik.uni-muenchen.de>,
linuxppc-dev list <linuxppc-dev@lists.linuxppc.org>
Subject: Re: Need a Linux PPC kernel which supports the Radeon Mobility 9600
Date: Sun, 12 Oct 2003 13:10:14 +0200 [thread overview]
Message-ID: <20031012111014.GB1677@mars.ravnborg.org> (raw)
In-Reply-To: <1065953260.992.11.camel@gaston>
On Sun, Oct 12, 2003 at 12:07:41PM +0200, Benjamin Herrenschmidt wrote:
>
> On Sat, 2003-10-11 at 23:44, Jens Schmalzing wrote:
> > Hi,
> >
> > Benjamin Herrenschmidt writes:
> >
> > > I just fixed that in my 2.6 and I'll backport to 2.4 soon
> >
> > I compiled the latest version of that tree in order to get radeonfb
> > working on my 17" Powerbook. A few questions:
> >
> > 1. The resulting kernel is more than 30MB in size. Is this normal?
Check that CONFIG_DEBUG_INFO is unset.
Otherwise the kernel will be much bigger - due to the symbolic info.
Sam
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-10-12 11:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-10 21:56 Need a Linux PPC kernel which supports the Radeon Mobility 9600 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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2003-10-14 22:10 Ken Offer
2003-10-15 8:19 ` Benjamin Herrenschmidt
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
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=20031012111014.GB1677@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=benh@kernel.crashing.org \
--cc=jens.schmalzing@physik.uni-muenchen.de \
--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).