linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dan@netx4.com>
To: bsimon@ctam.com.au
Cc: linuxppc-embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: mpc8xx-2.3.10 configuration questions.
Date: Thu, 16 Sep 1999 11:39:19 -0400	[thread overview]
Message-ID: <37E10F27.B4A844D6@netx4.com> (raw)
In-Reply-To: 37E03044.9653F5D2@ctam.com.au


Brendan Simon wrote:

> No, unfortunately I do not have access to a powermac.

I strongly recommend that anyone doing 8xx (or any PPC development)
use a PPC host of some type.  It is sooooo much easier.  No cross
development hassles, bytes in the proper world order, all of the
tools work......


> I do expect things not to work.


As I said, if it isn't directly 8xx related, you can probably
read about it on the other lists as well.


> .... I think I will do the port for the 2.2.5 first and
> then migrate it to the 2.3.x stuff later.  Does this sound reasonable ?

I think so.  After working with 2.3.18, 2.2.5 just feels "old".
In particular there are some configuration changes that work better
in the newer releases.

I wouldn't recommend 2.3.10 for anything right now.  In fact, I will
probably remove that tar image from the server the next time I visit.


	-- Dan

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~1999-09-16 15:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-09-15  1:25 mpc8xx-2.3.10 configuration questions Brendan Simon
1999-09-15 19:28 ` Dan Malek
1999-09-15 23:48   ` Brendan Simon
1999-09-16 15:39     ` Dan Malek [this message]
1999-09-16  7:36   ` Graham Stoney
1999-09-16 15:32     ` Dan Malek
1999-09-17  0:48       ` Graham Stoney
1999-09-17  1:47         ` Dan Malek

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=37E10F27.B4A844D6@netx4.com \
    --to=dan@netx4.com \
    --cc=bsimon@ctam.com.au \
    --cc=linuxppc-embedded@lists.linuxppc.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).