linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.muc.de>
To: Marcus Sundberg <erammsu@kieraypc01.p.y.ki.era.ericsson.se>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: MPC8xx: Bad emulation
Date: Fri, 11 Jun 1999 11:11:17 +0200	[thread overview]
Message-ID: <199906110911.LAA32422@denx.muc.de> (raw)
In-Reply-To: Your message of "Fri, 11 Jun 1999 09:23:16 +0200." <3760B964.E1424E37@switchboard.ericsson.se>


In message <3760B964.E1424E37@switchboard.ericsson.se>
Marcus Sundberg wrote:
> 
> Don't use floating point instructions in the programs, embedded PPC
> doesn't have FPUs. Use -mcpu=860 -msoft-float when compiling to use

Yes, I know this.

> soft floats (note that all FP using programs and libraries must
> be recompiled with these options to work properly).
> You will also need to patch glibc to remove the FP inline assembly
> and the inline memcpy  which assumes 32 byte cache lines.

And this is exactly the point that  makes  this  option  unacceptable
from  the  practical  point  of  view. We would have to build special
MPC8xx releases of LinuxPPC then. 

How does this work for you? You may have a small embedded system with
just  a  small  set  of  applications  in  mind,   where   `-mcpu=860
-msoft-float'  works  fine; but once you have Linux running on such a
board, it *always* happens that you run  into  situations  where  you
want  to  do some things in native mode - well, no problem: mount the
Linux environment over NFS. Then you can dynamically load and  unload
(and debug) device drivers, etc.

And suddenly you will need this tool and that one, too.

Your customer asks: And could I run a web server on  this  box,  too?
You say: well, no problem, just start appache - and "Bad emulation".

There are *many* situations where it is really necessary to  be  able
to run _any_ binary from a standrad LinuxPPC distribution on the 860,
too.  I agree that it makes sense to recompile dedicated applications
for an embedded solution.

Wolfgang Denk

-- 
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
"He only drinks when he gets depressed." "Why does he get depressed?"
"Sometimes it's because he hasn't had a drink."
                                     - Terry Pratchett, _Men at Arms_

[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

  reply	other threads:[~1999-06-11  9:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-06-04 21:29 MPC8xx: `init' problems / Bad emulation -- was: wrong zimage_start Wolfgang Denk
1999-06-11  7:23 ` Marcus Sundberg
1999-06-11  9:11   ` Wolfgang Denk [this message]
1999-06-14  2:41     ` MPC8xx: Bad emulation Michael R. Zucca
1999-06-14  3:31       ` Kolbjørn Barmen
1999-06-14  5:16         ` 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=199906110911.LAA32422@denx.muc.de \
    --to=wd@denx.muc.de \
    --cc=erammsu@kieraypc01.p.y.ki.era.ericsson.se \
    --cc=linuxppc-dev@lists.linuxppc.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).