Date: Mon, 24 May 2010 20:22:01 +0200 From: =?UTF-8?B?VmxhZGltaXIgJ8+GLWNvZGVyL3BoY29kZXInIFNlcmJpbmVua28=?= <phcoder@gmail.com> To: "M. Warner Losh" <imp@bsdimp.com> Cc: grub-devel@gnu.org, freebsd-arch@freebsd.org Subject: Re: [RFC] Multiboot2 drafting Message-ID: <4BFAC3C9.1080409@gmail.com> In-Reply-To: <20100514.064409.634347869525783787.imp@bsdimp.com> References: <4BE98FB5.3060906@gmail.com> <20100514020055.GB89230@duncan.reilly.home> <4BECEE31.3060004@gmail.com> <20100514.064409.634347869525783787.imp@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigF203EAB0CFAF9939618CFF30 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable M. Warner Losh wrote: > In message: <4BECEE31.3060004@gmail.com> > Vladimir '=CF=86-coder/phcoder' Serbinenko <phcoder@gmail.c= om> writes: > : 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. > > It is far from a historical left-over. I meant the only xnu on i386. It receives a device tree from bootloader but on most platforms it's either empty or ignored > Linux critically depends on > the boot loader on PowerPC to provide it with a tree of devices that > it cannot otherwise probe. On other architectures, it is becoming an > optional way to specify the device tree as well. There are many > different implementations of this, since primarily it is just data and > boot loaders are good at providing binary blobs to the kernel... > =20 Could we come up with a standard of passing this information in multiboot= 2? > In addition, Rafal Jawarski has ported this technology to FreeBSD. > He's presenting a paper on it today at BSDcan: > http://www.bsdcan.org/2010/schedule/events/171.en.html > I've reviewed the work, and it goes a long way towards making some of > the more stupid and repetitive parts of doing a port to a new embedded > architecture easy. > > Warner > =20 --=20 Regards Vladimir '=CF=86-coder/phcoder' Serbinenko --------------enigF203EAB0CFAF9939618CFF30 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 iF4EAREKAAYFAkv6w8kACgkQNak7dOguQglzJQEAnpQvl5/6IXEUTXfr28Iihl4e qQBLHbOuHbw5L1kRiSQA/0TCDLg8/TnkZGlQq7AqMdg9fXcRBWfoMHe2Lk+Wsi6M =sE7Y -----END PGP SIGNATURE----- --------------enigF203EAB0CFAF9939618CFF30--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4BFAC3C9.1080409>