From: "Joakim Tjernlund" <joakim.tjernlund@lumentis.se>
To: "'Wolfgang Denk'" <wd@denx.de>,
"'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 11:18:33 +0100 [thread overview]
Message-ID: <006301c3fd1b$0e58a2a0$0a01a8c0@LUMENTIS02> (raw)
In-Reply-To: <20040227094329.89EFCC0655@atlas.denx.de>
> In message
> <9CFB9DA5261CD611A29B00508B78904807F880ED@ex-deu-munich02.forc
> e.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).
Also, you must make sure you don't use any cache instructions such
as dcbz. I believe the optimized memset function i glibc uses dcbz.
The mpc8xx CPU has a HW bug which makes the TLB exceptions fail
for most cache instructions. There is a workaround for this, but it
is somewhat ugly. Search the embedded archives if you want to known more.
Jocke
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-02-27 10:18 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
2004-02-27 10:18 ` Joakim Tjernlund [this message]
-- 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='006301c3fd1b$0e58a2a0$0a01a8c0@LUMENTIS02' \
--to=joakim.tjernlund@lumentis.se \
--cc=Torsten.Demke@fci.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=wd@denx.de \
/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).