linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Paul Mackerras <paulus@samba.org>
To: Tom Rini <trini@kernel.crashing.org>
Cc: Scott Carroll <scottcar@us.ibm.com>, linuxppc-dev@lists.linuxppc.org
Subject: Re: Power3 problem?
Date: Thu, 16 Aug 2001 10:24:54 +1000 (EST)	[thread overview]
Message-ID: <15227.4822.809371.11593@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <20010815162545.C25310@cpe-24-221-152-185.az.sprintbbd.net>


Tom Rini writes:

> Well, pretending is a bad choice of words.  They are real chrp machines,
> but they aren't 'ALL_PPC', since you can't run on a power3 and a 604 :)

No, but if you had a prep or pmac with a power3 cpu, you could run the
same vmlinux as on a chrp power3. :)

> Well, I don't think it will be as bad as that.  It _should_ be possible
> to split them out, and move the functions it uses from pmac_setup.c into
> a common file.  If I have time I'll play with it sometime and post patches.
> If it can be done cleanly, I don't think it'd be a bad idea, but...

There is an argument for splitting out prep but I would rather keep
pmac and chrp together since they are quite similar.

Paul.

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

  reply	other threads:[~2001-08-16  0:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20010815145449.A16297@entropy.crashing.org>
2001-08-15 22:01 ` Power3 problem? Tom Rini
2001-08-15 22:44   ` Tom Gall
2001-08-15 23:15   ` Paul Mackerras
2001-08-15 23:25     ` Tom Rini
2001-08-16  0:24       ` Paul Mackerras [this message]
2001-08-16 14:54         ` Tom Rini
2001-08-16  7:46     ` Olaf Hering
2001-08-15 14:59 Scott Carroll

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=15227.4822.809371.11593@cargo.ozlabs.ibm.com \
    --to=paulus@samba.org \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=scottcar@us.ibm.com \
    --cc=trini@kernel.crashing.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).