From: Stefan Roese <sr@denx.de>
To: Matt Porter <mporter@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, linuxppc64-dev@ozlabs.org
Subject: Re: 440EP FPU support missing
Date: Wed, 9 Nov 2005 10:47:32 +0100 [thread overview]
Message-ID: <200511091047.32662.sr@denx.de> (raw)
In-Reply-To: <20051108153036.F27232@cox.net>
On Tuesday 08 November 2005 23:30, Matt Porter wrote:
> On Tue, Nov 08, 2005 at 06:38:11PM +0100, Stefan Roese wrote:
> > 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)?
>
> arch/powerpc/kernel/fpu.S is being used now which doesn't have KernelFP.
> I don't know why the 44x fpu support wasn't using
> kernel_fp_unavailable_exception() before but I must have missed that
> reviewing it.
>
> Try this patch.
>
> -Matt
>
> diff --git a/arch/ppc/kernel/head_booke.h b/arch/ppc/kernel/head_booke.h
> index aeb349b..f3d274c 100644
> --- a/arch/ppc/kernel/head_booke.h
> +++ b/arch/ppc/kernel/head_booke.h
> @@ -358,6 +358,6 @@ label:
> NORMAL_EXCEPTION_PROLOG; \
> bne load_up_fpu; /* if from user, just load it up */ \
> addi r3,r1,STACK_FRAME_OVERHEAD; \
> - EXC_XFER_EE_LITE(0x800, KernelFP)
> + EXC_XFER_EE_LITE(0x800, kernel_fp_unavailable_exception)
>
> #endif /* __HEAD_BOOKE_H__ */
Thanks Matt. That fixes the problem. Please send this patch upstream.
Best regards,
Stefan
next prev parent reply other threads:[~2005-11-09 9:47 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 [this message]
2005-11-08 22:32 ` David Gibson
2005-11-08 22:46 ` Matt Porter
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=200511091047.32662.sr@denx.de \
--to=sr@denx.de \
--cc=linuxppc-dev@ozlabs.org \
--cc=linuxppc64-dev@ozlabs.org \
--cc=mporter@kernel.crashing.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 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.