linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: Jerry Van Baren <gvb.linuxppc.dev@gmail.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Mikrotik RouterBoard 333
Date: Mon, 21 Jul 2008 16:13:44 -0500	[thread overview]
Message-ID: <20080721211344.GA13268@loki.buserror.net> (raw)
In-Reply-To: <487AA17E.6000808@gmail.com>

On Sun, Jul 13, 2008 at 08:44:46PM -0400, Jerry Van Baren wrote:
> I'm a half-ack.  ;-)  I'm partial to u-boot's implementation rather than  
> using a bootwrapper for obvious reasons.  The u-boot implementation  
> takes the blob as a boot parameter and passes it along to the kernel  
> after doing appropriate (optional) fixups.

And if those fixups expect a malformed device tree?

> Other than that quibble, I agree that burning the blob into the firmware  
> so that the firmware must be recompiled and reburned to change the blob  
> is very undesirable.

I thought the device tree was *supposed* to be an interface between the
firmware and the kernel?  What if the firmware produces the tree
dynamically?  What if the firmware itself depends on having the device tree
in order to operate?

-Scott

  reply	other threads:[~2008-07-21 21:15 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 [this message]
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

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=20080721211344.GA13268@loki.buserror.net \
    --to=scottwood@freescale.com \
    --cc=gvb.linuxppc.dev@gmail.com \
    --cc=linuxppc-dev@ozlabs.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).