From: Tom Rini <trini@kernel.crashing.org>
To: Kumar Gala <kumar.gala@freescale.com>
Cc: jonathan@jonmasters.org, linuxppc-embedded@ozlabs.org
Subject: Re: bi_recs
Date: Fri, 1 Oct 2004 15:06:48 -0700 [thread overview]
Message-ID: <20041001220648.GJ21896@smtp.west.cox.net> (raw)
In-Reply-To: <87127382-1357-11D9-8EFC-000393DBC2E8@freescale.com>
On Thu, Sep 30, 2004 at 10:11:03PM -0500, Kumar Gala wrote:
> >> But on the other hand, I've given up a long time ago trying to
> >enforce any
> > > kind of sane model on ppc32 because the embedded folks only care
> >about having
> > > a quick ugly broken hack to work with their board, thus the
> >explosion of
> > > various incompatible boot_info structures that we have nowadays.
> >
> >Yes indeed. It's ugly and needs fixing so I'll take a look at it - I
> > just don't want to do this if everyone here already knows of a better
> > solution which will work.
> >
> >Then Xilinx et al can generate memory maps and we can head towards
> > having a single kernel binary bootable on multiple different ppc
> > boards.
>
> I would be nice to have an extensive and dynamic way to pass info from
> the bootloader to the kernel. I believe that Wolfgang has stated he
> would be willing to change u-boot to match. I'd be willing to fixup
> and move Freescale boards over to use something as long as we get
> u-boot to support it as well.
>
> I've been told that ARM has a solution, in place, to this problem that
> might always be worth looking at.
I know the ARM folks on the list will yell at me, but to be a bit too
simple, it's a linked list of BI_ bits.
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. :)
--
Tom Rini
http://gate.crashing.org/~trini/
next prev parent reply other threads:[~2004-10-01 22:21 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 ` Tom Rini [this message]
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 ` 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=20041001220648.GJ21896@smtp.west.cox.net \
--to=trini@kernel.crashing.org \
--cc=jonathan@jonmasters.org \
--cc=kumar.gala@freescale.com \
--cc=linuxppc-embedded@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).