All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Vladimir 'φ-coder/phcoder' Serbinenko" <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
Date: Mon, 24 May 2010 23:07:05 +0200	[thread overview]
Message-ID: <4BFAEA79.4020901@gmail.com> (raw)
In-Reply-To: <4BFAC322.7070905@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1856 bytes --]

Vladimir 'φ-coder/phcoder' Serbinenko wrote:
> 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...
>>
>>   
>>     
> 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 selectors
> -it uses string identifiers instead of magic numbers. This makes it more
> difficult to parse
> -the most useful information is coming at the leaves and interpretation
> depends on whole path.
>   
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
>   
>> Cheers,
>>
>>   
>>     
>
>
>   


-- 
Regards
Vladimir 'φ-coder/phcoder' Serbinenko



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 293 bytes --]

  reply	other threads:[~2010-05-24 21:37 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
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 [this message]
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=4BFAEA79.4020901@gmail.com \
    --to=phcoder@gmail.com \
    --cc=areilly@bigpond.net.au \
    --cc=freebsd-arch@freebsd.org \
    --cc=grub-devel@gnu.org \
    /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.