From: Matt Mackall <mpm@selenic.com>
To: Roland Dreier <roland@topspin.com>
Cc: simon@baydel.com, linux-kernel@vger.kernel.org
Subject: Re: PPC 440 System
Date: Mon, 14 Jul 2003 16:55:01 -0500 [thread overview]
Message-ID: <20030714215501.GB19001@waste.org> (raw)
In-Reply-To: <524r1pw0bd.fsf@topspin.com>
On Mon, Jul 14, 2003 at 09:16:38AM -0700, Roland Dreier wrote:
> simon> If I remove /sbin/init from the nfs root the kernel panics
> simon> as expected, so I assume root is mounted ok. I have tried
> simon> to build a minimum root filesystem which contains
> simon> /dev/console, /dev/ttyS0 and a statically linked
> simon> /sbin/init. The init just does a printf but I do not see
> simon> this message. Does anyone know it this should work ?
>
> Yes, a static /sbin/init should work.
>
> simon> Initially I tried to build a root filesystem from files on
> simon> a Mac Clone running Yellow Dog Linux. I believe this has a
> simon> PPC 604e processor. Should this systems binaries/libraries
> simon> run on the 440GP ?
>
> simon> Can I expect a statically linked executable, made on the
> simon> Mac, to run on the 440GP?
>
> Probably not. The 440GP has no floating point hardware, so you will
> need (at least) to build a special glibc without FP instructions and
> also make sure your gcc is set up not to generate FP instructions.
You can build a 440 kernel with FPU emulation and it will run native
apps just fine, otherwise they'll core dump. I bootstrapped a full
native Debian PPC system on an Ebony board a few months ago.
--
Matt Mackall : http://www.selenic.com : of or relating to the moon
next prev parent reply other threads:[~2003-07-14 21:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-14 11:27 simon
2003-07-14 16:16 ` Roland Dreier
2003-07-14 21:55 ` Matt Mackall [this message]
2003-07-15 9:24 ` simon
2003-07-15 14:35 ` Matt Porter
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=20030714215501.GB19001@waste.org \
--to=mpm@selenic.com \
--cc=linux-kernel@vger.kernel.org \
--cc=roland@topspin.com \
--cc=simon@baydel.com \
/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
all inboxes | Powered by JetHome®