Date: Fri, 14 May 2010 08:31:13 +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: <4BECEE31.3060004@gmail.com> In-Reply-To: <20100514020055.GB89230@duncan.reilly.home> References: <4BE98FB5.3060906@gmail.com> <20100514020055.GB89230@duncan.reilly.home>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig167EF57E5A1AF8B901523CAB Andrew Reilly wrote: > 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 Yes and No. multiboot2 describes some aspects of the host system hardware but I've never heard of device trees outside of IEEE1275 or xnu, where it's probably a historical leftover. If this specification is clear and share some of our goals we can think of collaboration. Our goals in this direction: 1) Allow the same kernel load on all machines implementing the same ISA. This will require supplying info about machine. 2) Keep the things as advanced as they need to but not more advanced. E.g. when you supply an info about serial port you tell: it's at I/O port N rather than: it's in PCI bar X of device Y offset F. Since if OS doesn't support PCI this info is useless and if it does it will find out that this address is actually a part of PCI bar. This can be discussed though. 3) Firmware independency. Ideally OS shouldn't care at all which firmware it's running on. In some cases we may add pointers to firmware interfaces if there are good reasons for it but it's not the goal So if it's something clean and nice we should try integrating it. If it's however yet another firmware-dependant overkill interface it should be avoided. --=20 Regards Vladimir '=CF=86-coder/phcoder' Serbinenko --------------enig167EF57E5A1AF8B901523CAB 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 iF4EAREKAAYFAkvs7kEACgkQNak7dOguQgnDjwD/aZSHgDD4gj3k3ZnlE69boV2o YLdM2mZckB7juyGmVbUA/Rra3VpsJInbJxFUGOxRg5Creh1g3ythHLB9YJkg0TsK =ayn6 -----END PGP SIGNATURE----- --------------enig167EF57E5A1AF8B901523CAB--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4BECEE31.3060004>