From: Dan Malek <dan@embeddededge.com>
To: "Schaefer-Hutter, Peter" <Peter.Schaefer-Hutter@tfk-racoms.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: MPC8xx soft-float userspace ...
Date: Fri, 21 Oct 2005 10:00:42 -0400 [thread overview]
Message-ID: <e08bcb4de7fa6a71f103ce2c50c067f8@embeddededge.com> (raw)
In-Reply-To: <8E342283C2100540AAC5D103097054778A4189@rcexc.racoms.loc>
On Oct 21, 2005, at 5:31 AM, Schaefer-Hutter, Peter wrote:
> Due to the fact that the in-kernel FPU emulation looks
> broken on MPC8xx i want to build a complete soft-float
> userspace.
How does it "look broken?" It's always worked for me :-)
> .... Does anybody have some pointers what else
> needs to be removed?
Well, if you found it, you should be able to trace this to a
source file and remove it, right?
Thanks.
-- Dan
next prev parent reply other threads:[~2005-10-21 13:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-21 9:31 MPC8xx soft-float userspace Schaefer-Hutter, Peter
2005-10-21 14:00 ` Dan Malek [this message]
2005-10-24 8:27 ` Matej Kupljen
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=e08bcb4de7fa6a71f103ce2c50c067f8@embeddededge.com \
--to=dan@embeddededge.com \
--cc=Peter.Schaefer-Hutter@tfk-racoms.com \
--cc=linuxppc-embedded@ozlabs.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 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).