All of lore.kernel.org
 help / color / mirror / Atom feed
From: Raphael Bossek <raphael.bossek@gmx.de>
To: linuxppc-embedded@ozlabs.org
Cc: debian-embedded@lists.debian.org
Subject: Experiences with Debian Sarge on MPC8xx ?
Date: Fri, 22 Jul 2005 11:11:02 +0200	[thread overview]
Message-ID: <42E0B826.2070800@gmx.de> (raw)

Hi,

Debian GNU/Linux v3.1 (Sarge) is out so give it a try on my MPC850
running Debian v3.0 for more then 1 year with Denx's 2.4.20 kernel.

It failed with more or less the same reason as described May 2004
in this posting 
http://lists.debian.org/debian-embedded/2004/05/msg00032.html

Things changed since May 2004 but the problem seams to be. I'm using
100% binary compatible Debian GNU/Linux 3.0 (Woody) without any
problems on my MPC860 board with kernel FPU emulation enabled. This
math-emu implementation seams to be stable enought to work with libc6
2.2.5 and very many server application and large C++ application at high
load (our stress tests are really horrible for the compleate system!).

I've also heard from people on IRC that 100% Sarge works for them on
FPU-less MPC boards without trouble. So while I'm investigating the
problem would like to hear some more respond on this issue from
people who spend more time on getting Sarge running with 100% Debian
v3.1 (Sarge) on their MPC8xx environment.

The -msoft-float advice is not what I'm looking for. I'm not sure if
the FPU is responsible for the problem. Maybe the Debian libc6 2.3.2
package is missing something important for the MPC8xx PowerPC (the
cache-line-size is 4 for Debian's libc on PowerPC by default). The
big advantage using a standard distribution is the big number of
precompiled packages. I do not intent to recompile more then 18000
due to this first failed tests.

-- 
Raphael Bossek

             reply	other threads:[~2005-07-22  9:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-22  9:11 Raphael Bossek [this message]
2005-07-22  9:50 ` Experiences with Debian Sarge on MPC8xx ? Wolfgang Denk
2005-07-22 18:13 ` Yuli Barcohen
2005-07-22 21:58   ` Kumar Gala
2005-07-25  9:41     ` Yuli Barcohen

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=42E0B826.2070800@gmx.de \
    --to=raphael.bossek@gmx.de \
    --cc=debian-embedded@lists.debian.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.