[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: ppc64 boot images

On Mon, 2004-07-05 at 07:53 -0400, Paul Nasrat wrote:
> This is what I've been using to generate ppc64 boot images for G5.
> Comments welcome.  I guess we could use a single boot.iso for 32/64
> bit, I think this is what yellowdog use - I think possibly there CHRP
> script detects if it is 32 or 64 bit machine (probably by doing some
> device tree walking

I'm fine with this being two boot.isos for the time being.  We probably
do need a way to do it as one, though, if it's going to be useful (ie,
so that we can have one bootable disc1 :)  

> Index: mk-images.ppc
> ===================================================================
> RCS file: /usr/local/CVS/anaconda/scripts/mk-images.ppc,v
> retrieving revision 1.26
> diff -u -r1.26 mk-images.ppc
> --- mk-images.ppc       4 Jun 2004 16:45:10 -0000       1.26
> +++ mk-images.ppc       5 Jul 2004 11:43:30 -0000
> @@ -80,6 +80,31 @@
> +     elif [ "$KERNELARCH" = "ppc64" ]; then

This isn't ever going to get hit -- see the first stanza which catches
ppc64pseries or ppc64.  Now that the pSeries uses just the standard
ppc64 kernel, this will need to be rolled in with it.

> +       FAKEARCH="ppc"
> +       mkdir -p $TOPDESTPATH/ppc64/mac $TOPDESTPATH/images/mac

Eww, let's just have it under ppc/mac64 (or something like that) instead
of adding another top-level if we can.  Or is ppc64 needed by OF?

> +        echo "Building ppc64 initrd"

Looks the same as the pseries one (which is good), so we should be able
to just have one of these.

Otherwise, looks fine aside from needing to be integrated in.  If we
have to use ppc64 instead of ppc, then we'll want to use hard links
appropriately.  Also interesting to see will be if we can get one boot.
iso for pseries and ppc64 macs.


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]