From: Benjamin Herrenschmidt <bh40@calva.net>
To: linuxppc-dev@lists.linuxppc.org
Subject: miBoot 1.0d3
Date: Sun, 19 Sep 1999 01:45:57 +0200 [thread overview]
Message-ID: <19990919014557.023075@smtp.calvacom.fr> (raw)
HI !
miBoot 1.0d3 is online at http://calvaweb.calvacom.fr/bh40/test.html
I booted successfully Paul's latest 2.2.12 with a normal xcoff zImage, it
should also work with plain images (vmlinux, usually too large for a
floppy), zImage with initrd, and plain vmlinux compressed with -vf9
option. I didn't test zImage with initrd. (Note that the image is
decompressed by miBoot, the decompression "header" is bypassed.
The kernel file name is currently stored in resource STR# 128.
next on my list:
- get rid of the Apple boot blocs (write my own). Note that in theory,
using the 68k bootblocs, it may be possible to boot from an ext2
partition (using a first stage loader with a "map" like we do with OF)
- add some kind of gui to choose the root volume, options, and to be
able to change the video resolution when using video=ofonly (by calling
the ROM video driver).
Another issue is that I have currently no way to exit from miBoot. If I
fail to boot Linux, I exit to the caller, the disk is ejected, but the
machine doesn't try another disk to boot from. It may ne possible, it may
not, I'll have to disassemble more of MacOS ROM in order to figure this
out. I'd like to have a choice to boot MacOS, especially when miBoot is
on a hard disk partition. (I can still change the PRAM value and reboot).
--
E-Mail: <mailto:bh40@calva.net>
BenH. Web : <http://calvaweb.calvacom.fr/bh40/>
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~1999-09-18 23:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-18 23:45 Benjamin Herrenschmidt [this message]
1999-09-20 7:26 ` miBoot 1.0d3 Geert Uytterhoeven
-- strict thread matches above, loose matches on Subject: below --
1999-09-20 8:50 Benjamin Herrenschmidt
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=19990919014557.023075@smtp.calvacom.fr \
--to=bh40@calva.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).