Subject: RE: NetBSD/ofppc on Pegasos asking for boot partition
To: Jorge Acereda <firstname.lastname@example.org>
From: Matt Sealey <email@example.com>
Date: 12/16/2004 15:56:04
You already mailed us about the source code. I don't think it's
a matter for this public mailing list. We are discussing it :)
As for the deviation from the standard, why don't you collate
these and mail them to me off-list and I'll forward them to the
engineers and poke them until they are fixed.
It's all well and good to find bugs but if nobody knows about
them but you.. :)
Matt Sealey <firstname.lastname@example.org>
Genesi, Manager, Developer Relations
> -----Original Message-----
> From: Jorge Acereda [mailto:email@example.com]
> Sent: 16 December 2004 15:47
> To: Matt Sealey
> Cc: firstname.lastname@example.org; email@example.com
> Subject: Re: NetBSD/ofppc on Pegasos asking for boot partition
> On Thu, 16 Dec 2004 13:26:37 -0000, Matt Sealey <firstname.lastname@example.org> wrote:
> > A few small clarifications for Pegasos (someone asked some
> > questions yesterday).
> > The Pegasos uses a Marvell Discovery II northbridge. It's not
> > OpenPIC, it's just like an ordinary i8529-style interrupt
> > controller as found on any ordinary PC.
> > As it stands however, the OpenFirmware and hardware is all
> > CHRP-compliant so you can treat it as that besides.
> Is it? From the OpenFirmware standard:
> "Memory that cannot be allocated for general purpose use, for example
> physical memory on PowerPC systems used for interrupt vectors and
> implementation specific areas, shall not appear in the "available"
> property of the memory node. A Client Program that needs to use such
> memory for its architected purpose must not claim that area prior to
> Go to the OF console and list the memory properties. It reports memory
> from 0x0 upwards as available. Is that fixed in newer firmware
> As for the SmartFirmware sources, is there any way to get those? I
> don't mind signing NDAs if that is required.
> Jorge Acereda