public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Kumar Gala <kumar.gala@freescale•com>
To: <jonathan@jonmasters•org>
Cc: linuxppc-embedded@ozlabs•org
Subject: Re: bi_recs
Date: Thu, 30 Sep 2004 22:11:03 -0500	[thread overview]
Message-ID: <87127382-1357-11D9-8EFC-000393DBC2E8@freescale.com> (raw)
In-Reply-To: <35fb2e59040930165327f2dd59@mail.gmail.com>

> > 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.

- kumar

  reply	other threads:[~2004-10-01  3:11 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     ` Kumar Gala [this message]
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               ` 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=87127382-1357-11D9-8EFC-000393DBC2E8@freescale.com \
    --to=kumar.gala@freescale$(echo .)com \
    --cc=jonathan@jonmasters$(echo .)org \
    --cc=linuxppc-embedded@ozlabs$(echo .)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