From: Jason Eckhardt <jason@equator.com>
To: hppa-linux@puffingroup.com
Cc: jason@gatekeeper.equator.com
Subject: Re: [hppa-linux] Booting issues.
Date: Tue, 16 Feb 1999 08:32:41 -0800 (PST) [thread overview]
Message-ID: <199902161632.IAA00701@gatekeeper.equator.com> (raw)
>
> I was hoping someone could explain how booting works on HPs in the
> following ways:
>
> - booting from disk; is it possible to put our boot image onto an existing
> hpux disk, and boot from that image?
>
By "boot image" do you mean the bootstrap program or the kernel? I think
we could load the (future) kernel from an HPUX disk via HP's ISL, but it
would probably have to be in SOM format. Of course, I don't know for sure.
Over the weekend I got a simple bootstrap program up on a clean, non-HPUX
disk. It doesn't do much:
It simply prints a message "HPPA/Linux bootstrap version 0.00" and then
waits in a spin loop.
It is a small step in that I now understand the
boot process and can actually get the PDC to load and execute a bootstrap
code. There is a small assembly stub which sets up a C-friendly runtime
environment and then invokes a C subroutine to do I/O, etc.
I wrote a simple utility (like lifinit) which takes the bootstrap object,
prepends a LIF header, and then places it on the boot sector.
The next step is to get the simple bootstrap to load a kernel image. Maybe
someone can help me understand what to do next. Issues:
1. Should the bootloader be very simple and just load the kernel image
from a known place on the disk, such as immediately following the
bootstrap code (I believe the i386 version works this
way, correct me if I'm wrong) or should we instead load the kernel from
a Linux filesystem. The later
is a bit of a pain as it means we must have a standalone version
of a filesystem code in the bootloader (at least open, close, read,
seek, stat). The Mklinux works this way -- the boot code is huge...it
seems to me to be unnecessarily large and complex for a bootloader.
The first idea is much easier, since we just read from the already
open boot device (opened by the PDC) from a fixed location and then
branch to the kernel code.
Comments?
2. How are disks "partitioned" on HPs. The bootloader, if it uses the
scheme of loading the kernel from a linux filesystem, will have to
also "understand" the partition of the disk.
Does anyone know how the partitions are setup (i.e. partition table,
or equivalent)? Is the partition scheme imposed by hardware or
is this just a software convention?
Thanks for your help, jason.
----------------------------------------------------------------------
To unsubscribe: send e-mail to hppa-linux-request@puffingroup.com with
`unsubscribe' as the subject.
next reply other threads:[~1999-02-16 16:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-02-16 16:32 Jason Eckhardt [this message]
1999-02-16 18:01 ` [hppa-linux] Booting issues Alex deVries
1999-02-16 19:01 ` Bill Katz
1999-02-16 18:12 ` Richard J. Rauenzahn
1999-02-16 18:47 ` Michael Marxmeier
-- strict thread matches above, loose matches on Subject: below --
1999-02-16 1:48 Alex deVries
1999-02-16 6:06 ` Bill Katz
1999-02-16 17:18 ` Alex deVries
1999-02-16 18:23 ` Bill Katz
1999-02-16 18:35 ` Richard J. Rauenzahn
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=199902161632.IAA00701@gatekeeper.equator.com \
--to=jason@equator.com \
--cc=hppa-linux@puffingroup.com \
--cc=jason@gatekeeper.equator.com \
/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.