From: Matt Porter <mporter@kernel.crashing.org>
To: Stefan Roese <sr@denx.de>,
linuxppc-dev@ozlabs.org, linuxppc64-dev@ozlabs.org
Subject: Re: 440EP FPU support missing
Date: Tue, 8 Nov 2005 15:46:51 -0700 [thread overview]
Message-ID: <20051108154651.G27232@cox.net> (raw)
In-Reply-To: <20051108223202.GA25185@localhost.localdomain>; from david@gibson.dropbear.id.au on Wed, Nov 09, 2005 at 09:32:02AM +1100
On Wed, Nov 09, 2005 at 09:32:02AM +1100, David Gibson wrote:
> On Tue, Nov 08, 2005 at 06:38:11PM +0100, Stefan Roese wrote:
> > In the current linux version, Bamboo (440EP) won't compile anymore, because of
> > missing fpu support:
> >
> > make uImage
> > ...
> > LD init/built-in.o
> > LD .tmp_vmlinux1
> > arch/ppc/kernel/head_44x.o(.text+0x868): In function `_start':
> > : undefined reference to `KernelFP'
> > make: *** [.tmp_vmlinux1] Error 1
> >
> > Somehow arch/ppc/kernel/fpu.S has disappeared. :-( I assume, this happened in
> > the ppc/ppc64 -> powerpc merge. Any thoughts, why this file disappeared and
> > how to solve this problem (just restore the original file)?
>
> It's just moved to arch/powerpc/kernel/fpu.S. All you should need is
> to tweak the Makefiles so that it's included in your build.
Actually, the version in arch/powerpc/kernel/ is older than the version
removed from arch/ppc/kernel/. It is already being built...see my other
post.
-Matt
prev parent reply other threads:[~2005-11-08 22:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-07 19:49 [PATCH] ppc32: fix perf_irq extern on e500 Matt Porter
2005-11-08 3:01 ` Andrew Morton
2005-11-08 4:35 ` Matt Porter
2005-11-08 16:37 ` Matt Porter
2005-11-08 17:38 ` 440EP FPU support missing Stefan Roese
2005-11-08 22:30 ` Matt Porter
2005-11-08 22:32 ` Josh Boyer
2005-11-08 23:02 ` Matt Porter
2005-11-09 16:50 ` Josh Boyer
2005-11-09 9:47 ` Stefan Roese
2005-11-08 22:32 ` David Gibson
2005-11-08 22:46 ` Matt Porter [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=20051108154651.G27232@cox.net \
--to=mporter@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=linuxppc64-dev@ozlabs.org \
--cc=sr@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).