From: Gary Jennejohn <gljennjohn@googlemail.com>
To: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
Cc: The development of GRUB 2 <grub-devel@gnu.org>,
Andrew Reilly <areilly@bigpond.net.au>,
freebsd-arch@freebsd.org
Subject: Re: [RFC] Multiboot2 drafting
Date: Fri, 14 May 2010 13:21:42 +0200 [thread overview]
Message-ID: <20100514132142.252b092d@ernst.jennejohn.org> (raw)
In-Reply-To: <4BECEE31.3060004@gmail.com>
On Fri, 14 May 2010 08:31:13 +0200
Vladimir '__-coder/phcoder' Serbinenko <phcoder@gmail.com> 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...
> >
> >
> 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.
>
As an example of what I think Andrew was addressing, U-Boot can pass a
Flattened Device Tree to the Linux kernel. This basically allows a
Linux kernel to handle variants of a board without having to custom
compile Linux for each board. At the moment I think only powerpc-based
boards can be handled in this way.
--
Gary Jennejohn
next prev parent reply other threads:[~2010-05-14 11:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-11 17:11 [RFC] Multiboot2 drafting Vladimir 'φ-coder/phcoder' Serbinenko
2010-05-14 2:00 ` Andrew Reilly
2010-05-14 6:31 ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-05-14 11:21 ` Gary Jennejohn [this message]
2010-05-14 12:45 ` M. Warner Losh
2010-05-14 12:44 ` M. Warner Losh
2010-05-14 12:57 ` Rafal Jaworowski
2010-05-24 18:22 ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-05-14 12:50 ` M. Warner Losh
2010-05-24 18:19 ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-05-24 21:07 ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-06-02 19:02 ` Nathan Whitehorn
2010-05-25 4:53 ` Andrew Reilly
-- strict thread matches above, loose matches on Subject: below --
2010-04-03 17:01 Vladimir 'φ-coder/phcoder' Serbinenko
2010-04-03 17:01 ` Vladimir 'φ-coder/phcoder' Serbinenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100514132142.252b092d@ernst.jennejohn.org \
--to=gljennjohn@googlemail.com \
--cc=areilly@bigpond.net.au \
--cc=freebsd-arch@freebsd.org \
--cc=grub-devel@gnu.org \
--cc=phcoder@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.