Date: Mon, 24 May 2010 23:07:05 +0200 From: =?UTF-8?B?VmxhZGltaXIgJ8+GLWNvZGVyL3BoY29kZXInIFNlcmJpbmVua28=?= <phcoder@gmail.com> To: Andrew Reilly <areilly@bigpond.net.au> Cc: The development of GRUB 2 <grub-devel@gnu.org>, freebsd-arch@freebsd.org Subject: Re: [RFC] Multiboot2 drafting Message-ID: <4BFAEA79.4020901@gmail.com> In-Reply-To: <4BFAC322.7070905@gmail.com> References: <4BE98FB5.3060906@gmail.com> <20100514020055.GB89230@duncan.reilly.home> <4BFAC322.7070905@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigE1F13B1717527337636FC2AD Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Vladimir '=CF=86-coder/phcoder' Serbinenko wrote: > Andrew Reilly wrote: > =20 >> Hi there, >> >> I know next to nothing about GRUB, and have not yet read the >> multiboot spec, but I wonder if you could comment on how or >> whether this is related to either the Open Firmware Device Tree >> or the Flattened Device Tree used in various embedded OS ports. >> It would be cool if there were some convergence going on... >> >> =20 >> =20 > I've looked into it and found good and bad things. > Good: > -represents the info needed to OS. It's something definitely good and > goes in direction we need > Bad: > -it basically has all the history ballast of OpenFirmware. OFW is > supposed to be system-independent but in fact there is a multitude of > implementation with various degrees of compatibility. Same goes for > device trees. The same information is present in different places with > lots of special cases. Many of fields are actually useless variant sele= ctors > -it uses string identifiers instead of magic numbers. This makes it mor= e > difficult to parse > -the most useful information is coming at the leaves and interpretation= > depends on whole path. > =20 And traditional OpenFirmware has too much info which is probably useless. E.g. once you know where PCI controller is and you support PCI you can probe devices which are on it. If you don't support PCI controller the info about devices on it is probably useless too. Only exception is "early" info which is needed to e.g. setup console before normal drivers are up > It lacks aspects of complete boot protocol. I think it needs some > cleanup. I would be interested in converging simplified and cleaned up > version of device tree into multiboot2 > =20 >> Cheers, >> >> =20 >> =20 > > > =20 --=20 Regards Vladimir '=CF=86-coder/phcoder' Serbinenko --------------enigE1F13B1717527337636FC2AD Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iF4EAREKAAYFAkv66n8ACgkQNak7dOguQgl5cgEAl4ky22PaegWMRkA2jnhdJ+5J wzhIP5yl8CuiGUXODeQBALGM/89WvvWjBXYfbBmwzQ7RDcVS5XVy4PO0Yuk+7/ko =LLny -----END PGP SIGNATURE----- --------------enigE1F13B1717527337636FC2AD--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4BFAEA79.4020901>