From: Dan Malek <dan@embeddededge.com>
To: "Fillod Stephane" <stephane.fillod@thomson.net>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] invalid instructions in kernel mode
Date: Tue, 5 Apr 2005 12:16:28 -0400 [thread overview]
Message-ID: <eb2265e895a6c9f6d6996813d564b4db@embeddededge.com> (raw)
In-Reply-To: <1CFEB358338412458B21FAA0D78FE86D4F0D30@rennsmail02.eu.thmulti.com>
On Apr 5, 2005, at 8:24 AM, Fillod Stephane wrote:
> Speaking for myself, I don't plan on using the SPE FPU of the e500,
Why?
> It seems you didn't like my last patch which lets make enter the
> math-emu
> subdirectory only to compile the load/store (8xx could do that too).
> Would you prefer a fix along the line of Soft_emulate_8xx() ?
I'm not sure. I need to think about it for a moment. I was rushed to
do some travel, and now I'm back to work on it.
> I don't know what Kumar and his team have in mind for the e500,
The e500 tools use the SPE FPU for all single precision floating
point. For our initial development we used the floating point
emulation.
-- Dan
next prev parent reply other threads:[~2005-04-05 16:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-05 12:24 [PATCH] invalid instructions in kernel mode Fillod Stephane
2005-04-05 16:16 ` Dan Malek [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-04-08 17:36 Fillod Stephane
2005-04-11 15:39 ` Kumar Gala
2005-04-05 12:25 Fillod Stephane
2005-03-31 19:17 Fillod Stephane
2005-04-01 3:45 ` Dan Malek
2005-03-31 17:47 Fillod Stephane
2005-03-31 18:15 ` Dan Malek
2005-04-01 10:04 ` Kumar Gala
2005-04-07 17:38 ` Tom Rini
2005-04-07 21:41 ` Kumar Gala
2005-04-07 22:14 ` Tom Rini
2005-04-07 22:29 ` Kumar Gala
2005-04-08 16:02 ` Kumar Gala
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=eb2265e895a6c9f6d6996813d564b4db@embeddededge.com \
--to=dan@embeddededge.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=stephane.fillod@thomson.net \
/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).