linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Matt Porter <mporter@kernel.crashing.org>
To: Tom Rini <trini@kernel.crashing.org>
Cc: jonathan@jonmasters.org, linuxppc-embedded@ozlabs.org
Subject: Re: bi_recs
Date: Mon, 4 Oct 2004 07:41:05 -0700	[thread overview]
Message-ID: <20041004074105.A11487@home.com> (raw)
In-Reply-To: <20041004142909.GA27376@smtp.west.cox.net>; from trini@kernel.crashing.org on Mon, Oct 04, 2004 at 07:29:09AM -0700

On Mon, Oct 04, 2004 at 07:29:09AM -0700, Tom Rini wrote:
> On Mon, Oct 04, 2004 at 09:07:20AM +0300, Pantelis Antoniou wrote:
> > Tom Rini wrote:
> [snip]
> > >I've been thinking about it, and I do believe that Ben's flattened OF
> > >tree wins the "show me the code" race, so lets go that way.  I'll add in
> > >that for most platforms we'll want to build up the tree at compile time,
> > >but U-Boot, and anything else smart enough can pass one in for real.
> > >
> > >Jon, I look forward to your patch. :)
> > >
> > >
> > Allow me, to cut in and plug my own thing.
> [snip]
> > I just create an argv of all the environment variables of the firmware
> > and I pass the psysical address of that NULL terminated argv array
> > to the kernel command line like so... "u-boot-env=0x0f000f00".
> 
> The 'problem' I forsee with this is that we still have two methods for
> getting stuff in, an OF tree or env array.  If we got with a fake OF
> tree, we have just one method and we can always use it.
> 
> [snip]
> > I know this is the Nth time this discussion is taking place bu IMO something
> > must be finally decided. I don't really care if my solution will be selected
> > as long as something is at last selected.
> 
> As far as I'm concerned, unless some horrible problem springs up that
> we can't resolve, this is it.

Same here, I see that no one has raised a technical issue with the
flattened device tree method. Since it is a working mechanism AND it
unifies the arch, it's the clear choice over reinventing the wheel.
All we need is an implementation.

-Matt

  reply	other threads:[~2004-10-04 14:41 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-30 23:02 bi_recs Jon Masters
2004-09-30 23:21 ` bi_recs Benjamin Herrenschmidt
2004-09-30 23:53   ` bi_recs Jon Masters
2004-10-01  3:11     ` bi_recs Kumar Gala
2004-10-01  3:40       ` bi_recs Benjamin Herrenschmidt
2004-10-01 11:14         ` bi_recs Jon Masters
2004-10-01 14:53           ` [PATCH] for linuxppc-2.4 tree: adds Memec 2VP7 / 2VP4 board support Andrei Konovalov
2004-10-01 21:54           ` bi_recs Jon Masters
2004-10-02  4:35             ` bi_recs Benjamin Herrenschmidt
2004-10-02 12:59               ` bi_recs Jon Masters
2004-10-01 22:06       ` bi_recs Tom Rini
2004-10-04  6:07         ` bi_recs Pantelis Antoniou
2004-10-04 12:09           ` bi_recs Mark Chambers
2004-10-04 12:45           ` bi_recs Jon Masters
2004-10-04 16:43             ` bi_recs Dan Malek
2004-10-04 21:53               ` bi_recs Tom Rini
2004-10-04 20:20             ` bi_recs Wolfgang Denk
2004-10-04 14:29           ` bi_recs Tom Rini
2004-10-04 14:41             ` Matt Porter [this message]
2004-10-04 15:00               ` bi_recs Kumar Gala
2004-10-04 15:06               ` bi_recs Jon Masters
2004-10-04 15:47                 ` bi_recs Kumar Gala
2004-10-04 20:18           ` bi_recs Wolfgang Denk

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=20041004074105.A11487@home.com \
    --to=mporter@kernel.crashing.org \
    --cc=jonathan@jonmasters.org \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=trini@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).