From: Ethan Benson <erbenson@alaska•net>
To: linuxppc-dev@lists•linuxppc.org
Subject: Re: new bi_rec interface (was Re: [Ppcboot-users] Re: EV-64260 booting)
Date: Mon, 18 Mar 2002 14:33:26 -0900 [thread overview]
Message-ID: <20020318143326.B26309@plato.local.lan> (raw)
In-Reply-To: <20020318152329.B324434@brule.borg.umn.edu>; from bergner@brule.borg.umn.edu on Mon, Mar 18, 2002 at 03:23:29PM -0600
On Mon, Mar 18, 2002 at 03:23:29PM -0600, Peter Bergner wrote:
>
> What happened to the idea (paulus' idea?) of creating some wrapper
> code (eg, zimage) that would build the bootinfo and pass it into
> the kernel, so yaboot doesn't need to do much other than pass in
> boot params? This would force us to only boot zimages though
> (or whatever wrapper code we create).
from a logistical point of view this really seems to be the best
approach. keeping all the details in a kernel wrapper of sorts gives
the kernel maintainers much more freedom to make changes in the
future, whereas if its kept in yaboot (rather $bootloader) you have to
deal with backword compatibility and endless luser error due to using
the wrong bootloader versions with wrong kernels.
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.
--
Ethan Benson
http://www.alaska.net/~erbenson/
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next parent reply other threads:[~2002-03-18 23:33 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 ` Ethan Benson [this message]
2002-03-19 0:24 ` new bi_rec interface (was Re: [Ppcboot-users] Re: EV-64260 booting) Wolfgang Denk
2002-03-19 9:21 ` Ethan Benson
2002-03-19 0:29 ` Dan Malek
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=20020318143326.B26309@plato.local.lan \
--to=erbenson@alaska$(echo .)net \
--cc=linuxppc-dev@lists$(echo .)linuxppc.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