>
> What is important is that the OF client interface is still active and can be
> used from the client program (namely OpenSolaris here). This is the way the
> linux kernel early startup does it, in his prom.c code, and the way both
> yaboot and grub2 access the disk underneath.
>
> grub2 really only provides OF-like capabilities to hardware lacking such, and
> in the OF implementation case, it mostly just passes down his read accesses to
> the lower level.
What makes the GRUB2 so attractive is that it makes us independent from ufsboot.
It fetches the ramdisk image into the memory and runs from there. Which let us
have a working system even without ATA disk driver. the GRUB2 itself, indeed,
uses the OF-client interface to access disk (or network [coming soon]).
So I am not sure we need to invest in making ufsboot work on Peg.
What IS important (IMHO) is to support Solaris disk label natively in
SmartFirmware.
Solaris today groks two (three ?)types of labels - on SPARC it is Sun' VTOC,
on x86 it is FDISK partitions with VTOC encapsulated inside SOLARIS FDISK
partition. And another universally applicable partition type is EFI (aka GPT).
It (EFI) works on both SPARC and x86 and looks like a good choice for future
development. I am not sure who's responsibility it is to support EFI
label - OF or
GRUB2 (or both ?) if one want to stick to it.
Today Pegasos firmware supports Amiga and FDISK types, right ?
--
Regards,
Cyril
