All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Malek <dan@embeddededge.com>
To: Ethan Benson <erbenson@alaska.net>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: new bi_rec interface (was Re: [Ppcboot-users] Re: EV-64260 booting)
Date: Mon, 18 Mar 2002 19:29:45 -0500	[thread overview]
Message-ID: <3C968679.7040307@embeddededge.com> (raw)
In-Reply-To: 20020318143326.B26309@plato.local.lan


Ethan Benson wrote:

> from a logistical point of view this really seems to be the best
> approach.

This has been the normal mode of operation for the embedded boards.
Many of us think it is the logical approach, and quite a while ago
some of us started talking about how we can combine these ideas
in an effort to remove a reasonable amount of board specific code
from the kernel setup functions.

There were some challenges while trying to move from one method
to another, with the transition being the 2.4 source tree.  For
2.5 we just "declared" this will be the way.

> of course if someone doesn't want to use the wrapper they can just use
> the vmlinux and write thier own bootloader to handle all this stuff
> and take on the effort of ensuring its up to date with what the kernel
> wants.

There are people that want to do this and see value in doing so.  It
does present a challenge as I was one that broke ppcboot when I changed
the interface between the bootloader and the kernel (thinking everyone
used the bootloader wrapper on embedded boards :-).


	-- Dan


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

      parent reply	other threads:[~2002-03-19  0:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20020312195125.GB25926@cpe-24-221-152-185.az.sprintbbd.net>
     [not found] ` <21274.1015997038@msa.cmst.csiro.au>
     [not found]   ` <20020313155503.GB721@opus.bloom.county>
     [not found]     ` <20020318152329.B324434@brule.borg.umn.edu>
2002-03-18 23:33       ` new bi_rec interface (was Re: [Ppcboot-users] Re: EV-64260 booting) Ethan Benson
2002-03-19  0:24         ` Wolfgang Denk
2002-03-19  9:21           ` Ethan Benson
2002-03-19  0:29         ` Dan Malek [this message]

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=3C968679.7040307@embeddededge.com \
    --to=dan@embeddededge.com \
    --cc=erbenson@alaska.net \
    --cc=linuxppc-dev@lists.linuxppc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.