From: Jason Eckhardt <jason@equator.com>
To: adevries@redhat.com
Cc: jason@gatekeeper.equator.com, parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] ld problem workaround
Date: Thu, 6 May 1999 11:42:19 -0700 (PDT) [thread overview]
Message-ID: <199905061842.LAA11719@gatekeeper.equator.com> (raw)
> On Thu, 6 May 1999, Philipp Rumpf wrote:
> >
> > Where are the bootloader sources atm ?
> >
>
> Jason's sources are at:
>
> ftp://puffin.external.hp.com/pub/parisc/src/boot_rel_0.2.tar.gz
>
> I'm not quite sure how complete they are. The pain is that because of our
> lack of ELF32 in binutils these really need to be linked on an HPUX box.
>
The source is fairly complete in the sense that the bootstrap can load
a kernel image and transfer control to it. If we had a linux kernel, it could
be booted today.
The source can also be considered less
than complete in that it just reads the kernel from a fixed location on
the media -- for simplicity, to get linux up and running. Alex and
chris have suggested (and this was a thought all along) to have the booter
load the kernel from an ext2 file system. With more time, that can be
done. It's a bit painful since it involves a stand alone extfs (read only)
implementation. Hopefully, we can re-use much of the standard linux code,
but I haven't thought about this in detail yet.
Jason.
next reply other threads:[~1999-05-06 17:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-05-06 18:42 Jason Eckhardt [this message]
1999-05-06 18:47 ` [parisc-linux] ld problem workaround Ulrich Drepper
1999-05-06 19:51 ` Steve Ball
1999-05-06 20:47 ` Martin K. Petersen
1999-05-06 22:17 ` Philipp Rumpf
-- strict thread matches above, loose matches on Subject: below --
1999-05-06 22:14 Jason Eckhardt
1999-05-08 3:59 ` Philipp Rumpf
1999-05-06 5:24 Philipp Rumpf
1999-05-06 5:22 ` Alex deVries
1999-05-06 5:39 ` Philipp Rumpf
1999-05-06 5:38 ` Alex deVries
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=199905061842.LAA11719@gatekeeper.equator.com \
--to=jason@equator.com \
--cc=adevries@redhat.com \
--cc=jason@gatekeeper.equator.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox