From: Michael Brian Willis <willis@arlut.utexas.edu>
To: Clemens Koller <clemens.koller@anagramm.de>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Fedora 7 on a non FPU system
Date: Wed, 08 Aug 2007 17:18:22 -0500 [thread overview]
Message-ID: <1186611502.12665.26.camel@louie> (raw)
In-Reply-To: <46B8E76F.3020403@anagramm.de>
On Tue, 2007-08-07 at 23:43 +0200, Clemens Koller wrote:
> You can either use FPU emulation or do the floating point stuff on the e500
> core's SPE (Signal Processing Engine) which is AFAIK not supported by any
> major distribution.
I do have FPU emulation enabled in the kernel. I was able to get a
Yellow Dog 4.1 root filesystem to work. However when I move up to
YellowDog 5.0 or to Fedora 7, I have system lags. (For example, shortly
after boot-up, date and top do not behave properly. For example top
displays "nan" values. However a few minutes after boot up everything
seems fine.)
I suspect that the newest distribution versions rely more heavily on
full FPU functionality while the older distributions don't. Which might
be why older distributions seem to work a little better.
> CRUX - not a "major distro", because it's targeted at "experienced Linux users".
> I am running my selfmade version of "embedded CRUX" on my MPC8540 Boards
> based on http://cruxppc.sunsite.dk/wp/index.php which now fully supports
> the e500 core features.
Thanks, I will start looking into using CRUX.
> I bootstrapped the toolchain (binutils, (e)glibc, gcc and friends) from scratch
Did you find any documentation that was helpful when you did this?
I'm not really sure how to start this process. Do you basically just
download binutils, glibc etc... and compile them using the gcc that
comes with CRUX?
Thanks again for all your help!
Regards,
Michael Willis
Applied Research Labs-University of Texas
willis@arlut.utexas.edu
prev parent reply other threads:[~2007-08-08 22:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-12 17:00 Problem in compiling a kernel module Matthias Fechner
2007-03-12 18:36 ` Grant Likely
2007-03-13 4:30 ` Matthias Fechner
2007-03-13 4:55 ` Grant Likely
2007-03-13 12:55 ` Ben Warren
2007-03-14 4:33 ` Matthias Fechner
2007-03-14 6:54 ` Domen Puncer
2007-03-15 4:27 ` Matthias Fechner
2007-08-07 17:42 ` Fedora 7 on a non FPU system Michael Brian Willis
2007-08-07 19:11 ` Roland Dreier
2007-08-07 19:29 ` Josh Boyer
2007-08-07 21:43 ` Clemens Koller
2007-08-08 22:18 ` Michael Brian Willis [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=1186611502.12665.26.camel@louie \
--to=willis@arlut.utexas.edu \
--cc=clemens.koller@anagramm.de \
--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