linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Mikrotik RouterBoard 333
Date: Tue, 15 Jul 2008 11:41:49 +1000	[thread overview]
Message-ID: <20080715014149.GH26640@yookeroo.seuss> (raw)
In-Reply-To: <4ca5bd814ebc5d76508d40503f4884db@kernel.crashing.org>

On Tue, Jul 15, 2008 at 02:17:36AM +0200, Segher Boessenkool wrote:
>> Its firmware apparently provides a flattened device tree to the OS.
>> And while this step towards world domination is flattering, it's an
>> example of what I feared when people first got enthusiastic about the
>> idea of including flattened device trees in firmwares.  The tree has
>> not, AFAIK, been past this list, and has apparently not been reviewed
>> by someone knowledgeable about device trees.  In short, it's crap, and
>> now that it's embedded in the firware we can't really fix it.
>
> Can't you build a kernel with a blob that overrides the
> firmware-provided blob?

Sorry, my phrasing was slightly unclear.  Certainly we can work around
a firmware with a crap device tree by replacing it, if necessary.
Basically that's just treating the firmware as though it's one of
these old-style jobs which provides its tiny handful of necessary bits
of information (memory size, maybe a few others) in a format that
happens to resemble a device tree.

But it seems kind of silly for firmware to go to the trouble of
providing a device tree just for us to ignore it and substitute our
own.

-- 
David Gibson			| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you.  NOT _the_ _other_
				| _way_ _around_!
http://www.ozlabs.org/~dgibson

      reply	other threads:[~2008-07-15  1:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-08  4:26 Mikrotik RouterBoard 333 David Gibson
2008-07-09  4:09 ` Grant Likely
2008-07-14  0:44   ` Jerry Van Baren
2008-07-21 21:13     ` Scott Wood
2008-07-21 22:13       ` Segher Boessenkool
2008-07-22  2:54       ` Jerry Van Baren
2008-07-22  3:48         ` David Gibson
2008-07-22 14:56         ` Scott Wood
2008-07-15  0:17 ` Segher Boessenkool
2008-07-15  1:41   ` David Gibson [this message]

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=20080715014149.GH26640@yookeroo.seuss \
    --to=david@gibson.dropbear.id.au \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=segher@kernel.crashing.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).