public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Roland Dreier <roland@topspin.com>
To: "" <simon@baydel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PPC 440 System
Date: 14 Jul 2003 09:16:38 -0700	[thread overview]
Message-ID: <524r1pw0bd.fsf@topspin.com> (raw)
In-Reply-To: <3F12A1B9.3086.614B56@localhost>

    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.

Your best bet is probably to download ELDK (a free Embedded Linux
Development Kit) from www.denx.de.  Dan Kegel also has some good PPC
4xx cross development information at www.kegel.com.

Best,
  Roland

  reply	other threads:[~2003-07-14 16:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-14 11:27 PPC 440 System simon
2003-07-14 16:16 ` Roland Dreier [this message]
2003-07-14 21:55   ` Matt Mackall
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=524r1pw0bd.fsf@topspin.com \
    --to=roland@topspin.com \
    --cc=linux-kernel@vger.kernel.org \
    --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