[Top][All Lists]

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

Re: [RFC] Multiboot2 drafting

From: Vladimir 'φ-coder/phcoder' Serbinenko
Subject: Re: [RFC] Multiboot2 drafting
Date: Mon, 24 May 2010 20:22:01 +0200
User-agent: Mozilla-Thunderbird (X11/20091109)

M. Warner Losh wrote:
> In message: <address@hidden>
>             Vladimir 'φ-coder/phcoder' Serbinenko <address@hidden> 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...
Could we come up with a standard of passing this information in multiboot2?
> In addition, Rafal Jawarski has ported this technology to FreeBSD.
> He's presenting a paper on it today at BSDcan:
> 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

Vladimir 'φ-coder/phcoder' Serbinenko

Attachment: signature.asc
Description: OpenPGP digital signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]