From: Yuli Barcohen <yuli@arabellasw.com>
To: Kumar Gala <kumar.gala@freescale.com>
Cc: debian-embedded@lists.debian.org, linuxppc-embedded@ozlabs.org
Subject: Re: Experiences with Debian Sarge on MPC8xx ?
Date: Mon, 25 Jul 2005 12:41:28 +0300 [thread overview]
Message-ID: <17124.46024.454586.233091@astp0002.localdomain> (raw)
In-Reply-To: <E5B7BB81-C268-448D-BCEC-6B619D81D793@freescale.com>
>>>>> Kumar Gala writes:
Kumar> Does that actually work or are you suggesting something to
Kumar> try?
This actually works, not with Sarge but with Sid, though glibc version
is the same AFAIK. On MPC8xx, I usually use BusyBox for core utilities
and self-compiled glibc (for performance reasons mentioned by Wolfgang),
and add ready Debian packages for more advanced functions (mail server,
for example). The self-compiled glibc is from the Sid source, so the
problem in it and in the Debian pre-compiled library was the same. I
don't know if it's the only problem on MPC8xx, but on our boards the
"fix" which I described was enough. As we already discussed a couple of
weeks ago, assembler version of memset looks broken for cache line sizes
smaller than (not equal to?) 32. Maybe it's the many times mentioned
dcbz problem. Anyway, the "fix" causes glibc to switch in run time to C
version of memset.
Hope this helps,
--
========================================================================
Yuli Barcohen | Phone +972-9-765-1788 | Software Project Leader
yuli@arabellasw.com | Fax +972-9-765-7494 | Arabella Software, Israel
========================================================================
prev parent reply other threads:[~2005-07-25 9:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-22 9:11 Experiences with Debian Sarge on MPC8xx ? Raphael Bossek
2005-07-22 9:50 ` Wolfgang Denk
2005-07-22 18:13 ` Yuli Barcohen
2005-07-22 21:58 ` Kumar Gala
2005-07-25 9:41 ` Yuli Barcohen [this message]
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=17124.46024.454586.233091@astp0002.localdomain \
--to=yuli@arabellasw.com \
--cc=debian-embedded@lists.debian.org \
--cc=kumar.gala@freescale.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).