From: Kumar Gala <kumar.gala@freescale•com>
To: "Matt Porter" <mporter@kernel•crashing.org>
Cc: jonathan@jonmasters•org, linuxppc-embedded@ozlabs•org
Subject: Re: bi_recs
Date: Mon, 4 Oct 2004 10:00:27 -0500 [thread overview]
Message-ID: <20608413-1616-11D9-9774-000393DBC2E8@freescale.com> (raw)
In-Reply-To: <20041004074105.A11487@home.com>
On Oct 4, 2004, at 9:41 AM, Matt Porter wrote:
> 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=20
> flattened OF
> > > >tree wins the "show me the code" race, so lets go that way.=A0=20=
> I'll add in
> > > >that for most platforms we'll want to build up the tree at=20
> compile time,
> > > >but U-Boot, and anything else smart enough can pass one in for=20=
> 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=20
> firmware
> > > and I pass the psysical address of that NULL terminated argv =
array
> > > to the kernel command line like so... "u-boot-env=3D0x0f000f00".
> >
> > The 'problem' I forsee with this is that we still have two methods=20=
> for
> > getting stuff in, an OF tree or env array.=A0 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=20
> IMO something
> > > must be finally decided. I don't really care if my solution will=20=
> 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.
I'm in agreement with Matt and Tom. We should only have one solution=20
to this problem.
- kumar
next prev parent reply other threads:[~2004-10-04 15:02 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 ` bi_recs Matt Porter
2004-10-04 15:00 ` Kumar Gala [this message]
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=20608413-1616-11D9-9774-000393DBC2E8@freescale.com \
--to=kumar.gala@freescale$(echo .)com \
--cc=jonathan@jonmasters$(echo .)org \
--cc=linuxppc-embedded@ozlabs$(echo .)org \
--cc=mporter@kernel$(echo .)crashing.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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