From: Wolfgang Denk <wd@denx.de>
To: "Demke, Torsten" <Torsten.Demke@fci.com>
Cc: "Linuxppc-Embedded (E-mail)" <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: problem with standard libc on 8xx
Date: Fri, 27 Feb 2004 10:43:24 +0100 [thread overview]
Message-ID: <20040227094329.89EFCC0655@atlas.denx.de> (raw)
In-Reply-To: Your message of "Fri, 27 Feb 2004 09:55:12 +0100." <9CFB9DA5261CD611A29B00508B78904807F880ED@ex-deu-munich02.force.de>
In message <9CFB9DA5261CD611A29B00508B78904807F880ED@ex-deu-munich02.force.de> you wrote:
>
> I created my own root-fs for a MPC8xx platform
> using standard Debian packages (including libc).
> When I start the system, the init scripts hangs
...
> I guess that the Debian libc uses floating point - which
Thi sis definitely one cause of the problem. Another one might be
optimization for a incorrect cache line size (32 instead of 16
bytes).
> is not available on MPC8xx - but I thougt the kernel would
> emulate this calls (CONFIG_MATH_EMULATION=y).
This has never been working reliably for any real-life code. And it's
awfully slow.
Also note that you CANNOT mix standard binaries (from Debian) and 8xx
specific libraries (from ELDK) - this will crash as soon as an
application attempts to use floating point.
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
Above all else -- sky.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-02-27 9:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-27 8:55 problem with standard libc on 8xx Demke, Torsten
2004-02-27 9:43 ` Wolfgang Denk [this message]
2004-02-27 10:18 ` Joakim Tjernlund
-- strict thread matches above, loose matches on Subject: below --
2004-02-27 10:11 Demke, Torsten
2004-02-27 10:36 ` 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=20040227094329.89EFCC0655@atlas.denx.de \
--to=wd@denx.de \
--cc=Torsten.Demke@fci.com \
--cc=linuxppc-embedded@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).