From: Sam Ravnborg <sam@ravnborg.org>
To: Sean MacLennan <smaclennan@pikatech.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Wolfgang Denk <wd@denx.de>,
linuxppc-dev <linuxppc-dev@ozlabs.org>
Subject: Re: unexpected non-allocatable section
Date: Sun, 3 May 2009 22:51:38 +0200 [thread overview]
Message-ID: <20090503205138.GB1506@uranus.ravnborg.org> (raw)
In-Reply-To: <20090503163241.50bfcae4@lappy.seanm.ca>
On Sun, May 03, 2009 at 04:32:41PM -0400, Sean MacLennan wrote:
> On Sun, 3 May 2009 22:07:01 +0200
> "Sam Ravnborg" <sam@ravnborg.org> wrote:
>
> > On Sun, May 03, 2009 at 09:33:16PM +0200, Wolfgang Denk wrote:
>
> > > Which exact commands did you use to build the kenrel, and how did
> > > you set (and export?) the CROSS_COMPILE environment variable?
>
> export CROSS_COMPILE=ppc_4xxFP-
> export ARCH=powerpc
>
> The toolchain is in my path
>
> > > The thing is, that I cannot reproduce this - I tested it with
> > > v2.6.30-rc4, both with ELDK 4.1 (as you) and ELDK 4.2.
> > >
> > > Both build the kernel image without any such warnings.
> >
> > Anders already found the cause of this - it
> > was a missing endian conversion.
> > So you need to run this on a little endian target to
> > see it. And you need to do a full kernel build
> > so we run modpsot on vmlinux.
> >
> > I will push the patch in a few minutes.
>
> That patch gets rid of the warnings.
Thanks for the quick testing. I will add a "Tested-by: if I rebase the tree.
Sam
prev parent reply other threads:[~2009-05-03 20:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-03 2:41 unexpected non-allocatable section Sean MacLennan
2009-05-03 7:04 ` Sean MacLennan
2009-05-03 10:45 ` Stephen Rothwell
2009-05-03 16:39 ` Sean MacLennan
2009-05-03 19:33 ` Wolfgang Denk
2009-05-03 20:07 ` Sam Ravnborg
2009-05-03 20:19 ` Wolfgang Denk
2009-05-03 20:51 ` Sam Ravnborg
2009-05-03 20:32 ` Sean MacLennan
2009-05-03 20:51 ` Sam Ravnborg [this message]
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=20090503205138.GB1506@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=sfr@canb.auug.org.au \
--cc=smaclennan@pikatech.com \
--cc=wd@denx.de \
/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).