From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Josh Boyer <jwboyer@gmail.com>
Cc: "Frank Svendsbøe" <frank.svendsboe@gmail.com>,
"Wolfgang Denk" <wd@denx.de>,
robert.karl.berger@gmail.com, linuxppc-dev@ozlabs.org
Subject: Re: kilauea compilation breaks with v3.3 kernel and ELDK 4.2
Date: Tue, 03 Apr 2012 07:08:30 +1000 [thread overview]
Message-ID: <1333400910.30734.54.camel@pasglop> (raw)
In-Reply-To: <CA+5PVA6jQgme0sS=i8yYX6b_R5179+BtWPh7QXCGNfoLTCt46A@mail.gmail.com>
On Mon, 2012-04-02 at 08:10 -0400, Josh Boyer wrote:
> On Fri, Mar 30, 2012 at 8:03 PM, Benjamin Herrenschmidt
> <benh@kernel.crashing.org> wrote:
> > On Sat, 2012-03-31 at 00:53 +0200, Frank Svendsbøe wrote:
> >
> >> Hi Josh Boyer,
> >>
> >> just wanted to add that I'm experiencing the same problem that Robert
> >> reported, but on 8xx instead of 4xx. The mpc8xx does not support the
> >> mfdcrx instruction, so maybe it's more to it than just a binutils bug?
> >
> > The kernel shouldn't have tried to build that instruction on 8xx, though
> > I suppose if it's in arch/powerpc/boot, we are a bit too eager at
> > building everything including what's not relevant, we might to be a bit
> > more careful at excluding 4xx stuff on a 8xx kernel.
>
> It's still a binutils issue. Sounds like the toolchain being used to
> build the 8xx kernel is specifically built for 8xx. A generally built
> binutils should have worked fine (assuming it was new enough), since
> we pass -mcpu=405.
Still, it makes sense to limit the building of the wrappers to the CPU
family of the kernel...
Cheers,
Ben.
next prev parent reply other threads:[~2012-04-02 21:08 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-21 12:10 kilauea compilation breaks with v3.3 kernel and ELDK 4.2 Robert Berger
2012-03-21 13:29 ` Josh Boyer
2012-03-21 16:25 ` Wolfgang Denk
2012-03-24 23:53 ` Benjamin Herrenschmidt
2012-03-26 13:36 ` Josh Boyer
2012-03-30 22:53 ` Frank Svendsbøe
2012-03-31 0:03 ` Benjamin Herrenschmidt
2012-04-01 22:14 ` Frank E. Svendsbøe
2012-04-02 2:01 ` Benjamin Herrenschmidt
2012-04-02 6:28 ` Tony Breeds
2012-04-02 8:37 ` Frank E. Svendsbøe
2012-05-06 14:37 ` Robert Berger
2012-05-17 14:37 ` Frank Svendsbøe
2012-04-02 12:10 ` Josh Boyer
2012-04-02 21:08 ` Benjamin Herrenschmidt [this message]
2012-04-02 21:26 ` Josh Boyer
2012-04-04 19:21 ` Wolfgang Denk
2012-04-05 0:02 ` Stephen Rothwell
2012-04-05 17:44 ` Wolfgang Denk
2012-03-21 22:14 ` Tony Breeds
2012-03-21 22:34 ` Wolfgang Denk
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=1333400910.30734.54.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=frank.svendsboe@gmail.com \
--cc=jwboyer@gmail.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=robert.karl.berger@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.