All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philipp Rumpf <prumpf@suse.de>
To: Alex deVries <adevries@redhat.com>
Cc: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] Creating a bootable image.
Date: Tue, 1 Jun 1999 09:16:01 +0200	[thread overview]
Message-ID: <19990601091601.A6399@suse.de> (raw)
In-Reply-To: <Pine.LNX.3.96.990601002832.8814F-100000@devserv.devel.redhat.com>; from Alex deVries on Tue, Jun 01, 1999 at 12:33:05AM -0400

> I'm mailing this because I'm not entirely sure what I'm doing is correct.

Neither am I, but arch/parisc/hp/boot/README seems to say something different.

> The way I understand it, the kernel we cross compile on Linux is in fact
> a broken ELF32 file, which doesn't really matter, because at this point we
> don't need the kernel to have any loader information itself. 

I think we should build a binary image of the kernel (that is not ELF) like
we do for x86.

> However, to actually boot you need IPL, which requires SOM linking, so
> that much must be done on HPUX.

This I do not understand. According to arch/parisc/hp/boot/README, the IPL is
stored in a special binary format which we could generate from ELF like we
do for the kernel image.

> and it'll create a kernel and boot header that should just boot right
> away.  That way to do kernel work (and not bootstrap work), you don't need
> HPUX at all.

I think the vast majority of parisc boxes runs HP-UX at the moment so it
probably would not be a big win.

	Philipp Rumpf

  reply	other threads:[~1999-06-01  7:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-06-01  4:33 [parisc-linux] Creating a bootable image Alex deVries
1999-06-01  7:16 ` Philipp Rumpf [this message]
1999-06-01 13:27   ` Alex deVries
1999-06-01 14:06   ` Mike Shaver

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=19990601091601.A6399@suse.de \
    --to=prumpf@suse.de \
    --cc=adevries@redhat.com \
    --cc=parisc-linux@thepuffingroup.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.