All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Eckhardt <jason@equator.com>
To: dave@hiauly1.hia.nrc.ca, prumpf@suse.de
Cc: cjbeard@istar.ca, parisc-linux@thepuffingroup.com
Subject: Re: Building the Bootloader
Date: Tue, 1 Jun 1999 13:44:55 -0700 (PDT)	[thread overview]
Message-ID: <199906012044.NAA19549@gatekeeper.equator.com> (raw)


> > > I think that I may have been able to successfully cross compile ipl to an
> > > elf binary with text starting at offset 0.  Note that this requires that
> > 
> > offset 0 sounds bad as we may not corrupt page 0 (the PDC puts some data we
> > need there).
>
> This is easily changed but seems consistent with the "-R 0" option to
> the hp linker used in Jason Eckhardt's Makefile.  It would appear that
> mkipl builds the actual image.  On the otherhand, no care was taken
> to compile using pic so there may be a relocation problem.
>

  Care was taken -- the ipl is position independent with the chosen 
  combination of flags and code design. The ipl makes no assumption about the
  location it will be loaded into by the ROM (see ipl_s.s). Text offset zero 
  is correct for linking in the scheme I have chosen. The bootloader determines
  where is was loaded at runtime and sets the dp and sp accordingly. All of
  this should be obvious from the code.

  The specific combination of flags allowed me to get something resembling
  a straight binary image (by ignoring the header) and position independence.
  For some reason I can't remember now, -fpic didn't get the job done
  (perhaps a compiler defect).

  In any case, I expect later that we will just link the ipl as a standard
  ELF and then extract the "actual" binary image from it (as chris mentioned
  earlier, and as mentioned in the HILO README). The point was to get a 
  simple bootloader going, which I did (there were no cross tools at that
  time, I therefore just used gcc on HPUX). Any number of tweaks can easily be
  made as needed.

  jason.

             reply	other threads:[~1999-06-01 20:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-06-01 20:44 Jason Eckhardt [this message]
1999-06-01 21:35 ` Building the Bootloader John David Anglin
1999-06-02 14:45   ` John David Anglin
  -- strict thread matches above, loose matches on Subject: below --
1999-06-01 15:58 Christopher Beard
1999-06-01 16:44 ` John David Anglin
1999-06-01 17:18   ` Philipp Rumpf
1999-06-01 18:05     ` John David Anglin
1999-06-01 19:31       ` Philipp Rumpf
1999-06-01 20:03         ` John David Anglin

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=199906012044.NAA19549@gatekeeper.equator.com \
    --to=jason@equator.com \
    --cc=cjbeard@istar.ca \
    --cc=dave@hiauly1.hia.nrc.ca \
    --cc=parisc-linux@thepuffingroup.com \
    --cc=prumpf@suse.de \
    /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.