linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Matt Sealey" <matt@genesi-usa.com>
To: "'Paul Mackerras'" <paulus@samba.org>, <linuxppc-dev@ozlabs.org>
Subject: RE: Who cares about PReP?
Date: Wed, 9 Aug 2006 17:00:50 +0200	[thread overview]
Message-ID: <013401c6bbc4$9d2acd90$99dfdfdf@bakuhatsu.net> (raw)
In-Reply-To: <17622.58559.879330.496619@cargo.ozlabs.ibm.com>


QEMU PPC implements a PReP system too.

Probably a good place to test without needing a real system.

However it's the kind of thing you'd want to throw a CHRP
ROM onto in the end, and forget PReP for emulation (after
all, nobody makes 'em anymore).

-- 
Matt Sealey <matt@genesi-usa.com>
Manager, Genesi, Developer Relations
 

> -----Original Message-----
> From: linuxppc-dev-bounces+matt=genesi-usa.com@ozlabs.org 
> [mailto:linuxppc-dev-bounces+matt=genesi-usa.com@ozlabs.org] 
> On Behalf Of Paul Mackerras
> Sent: Monday, August 07, 2006 8:59 AM
> To: linuxppc-dev@ozlabs.org
> Subject: Who cares about PReP?
> 
> I started looking at moving the PReP code over to 
> arch/powerpc.  I am struck by how many ifdefs there are in 
> there to set things up for particular individual PReP 
> implementations.  We can do better than that, I'm sure, but 
> the issue becomes one of testing.  The only PReP I have here 
> is an RS/6000 43p-140.
> 
> Who else has a PReP system and would be willing to do some 
> testing and debugging?  If so, what sort of PReP is it?
> 
> Paul.
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-dev
> 

  parent reply	other threads:[~2006-08-09 15:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-07  6:59 Who cares about PReP? Paul Mackerras
2006-08-07  7:26 ` Olaf Hering
2006-08-07  9:27 ` Xavier Grave
2006-08-08 14:05 ` Tom Rini
2006-08-09 15:00 ` Matt Sealey [this message]
2006-08-16 10:15 ` Gabriel Paubert
2006-08-16 11:22   ` Paul Mackerras
2006-08-16 11:57     ` Paul Mackerras
2006-08-17 17:16     ` Marc Dietrich
2006-08-17 17:18     ` Marvin
     [not found] <mailman.2127.1155045931.11183.linuxppc-dev@ozlabs.org>
2006-08-09  4:02 ` Ed Goforth
  -- strict thread matches above, loose matches on Subject: below --
2006-08-09  5:08 Robert Brose

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='013401c6bbc4$9d2acd90$99dfdfdf@bakuhatsu.net' \
    --to=matt@genesi-usa.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.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).