From: Ethan Benson <erbenson@alaska.net>
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: [RFC] A stand-alone boot loader for PReP
Date: Sat, 31 May 2003 13:49:50 -0800 [thread overview]
Message-ID: <20030531214950.GP32642@plato.local.lan> (raw)
In-Reply-To: <62639.213.107.143.228.1054413401.squirrel@www.solinno.co.uk>
On Sat, May 31, 2003 at 09:36:41PM +0100, Leigh Brown wrote:
>
> [If you bore easily: http://www.solinno.co.uk/leigh/pablo/pablo-0.2.tar.gz ]
>
> Ever since I got Linux going on my PReP box I've been unhappy about the
> boot loader. There is no lilo or yaboot equivalent for PReP and it's a
> pain. For the past several months I've been trying to devise a way of
> making a bootloader similar to lilo or yaboot, and this is the best I've
> been able to come up with.
I have been working (slowly due to lack of time) on a complete rewrite
of yaboot, the plan is for it to support any OF based hardware (not
limited to powerpc), and to design it in a general way so it can
accomidate the various ways different architectures boot.
to start with im writing a prom-libc library so all the usual stdc
stuff doesn't have to be reinvented crappilly like every other loader
seems to do, as well as get the prom specific stuff out of bootloaders
and into a common place (it also should allow for a bootloader which
is designed well enough to be more easily portable to different prom
types so long as prom-libc has support). it will also allow the
bootloader to be written much more like ordinary unix C programs,
making them more portable (don't port the loader, port prom-libc).
my goal is to eliminate the need for a different bootloader for every
variation of hardware, i particularly hate how there is a dozen
different loaders all with different user interfaces just for powerpc,
much less other architectures.
I would much appreciate help with the yaboot2.0 project, if anyone is
interested contact me privatly, or on the yaboot-devel list
(http://lists.penguinppc.org/yaboot-devel).
--
Ethan Benson
http://www.alaska.net/~erbenson/
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-05-31 21:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-31 20:36 [RFC] A stand-alone boot loader for PReP Leigh Brown
2003-05-31 21:49 ` Ethan Benson [this message]
2003-06-01 13:57 ` Leigh Brown
2003-06-01 22:12 ` Ethan Benson
2003-06-02 8:26 ` Remco Post
2003-06-02 17:40 ` Tom Rini
2003-06-03 6:43 ` Ethan Benson
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=20030531214950.GP32642@plato.local.lan \
--to=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 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).