From: Mike McDonald <mikemac@mikemac.com>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: Gerald Champagne <gerald.champagne@esstech.com>,
"linux-mips@oss.sgi.com" <linux-mips@oss.sgi.com>
Subject: Re: Moving kernel_entry to LOADADDR
Date: Fri, 19 Oct 2001 08:11:40 -0700 [thread overview]
Message-ID: <200110191511.IAA27477@saturn.mikemac.com> (raw)
In-Reply-To: Your message of "Fri, 19 Oct 2001 15:20:33 +0200." <Pine.GSO.3.96.1011019152007.1657E-100000@delta.ds2.pg.gda.pl>
>Date: Fri, 19 Oct 2001 15:20:33 +0200 (MET DST)
>From: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
>To: Gerald Champagne <gerald.champagne@esstech.com>
>Subject: Re: Moving kernel_entry to LOADADDR
>
>On Thu, 18 Oct 2001, Gerald Champagne wrote:
>
>> I also removed the .fill, and now kernel_entry is always exactly LOADADDR,
>> and that makes my bootloader easier to maintain.
>>
>> Is this worth changing in cvs, or did I miss something?
>
> How about just getting it from the ELF header? It's trivial.
Because a bare bones bootloader may not know anything about ELF. The
simplest solution is to just stick a "jmp start_kernel" at LOADADDR
right before the fill. Then the load address and the entry point are
the same. Once the exception vectors get loaded, they'll overwrite the
jmp, so no space is wasted and none of the LOADADDRs have to be
changed.
Mike McDonald
mikemac@mikemac.com
next prev parent reply other threads:[~2001-10-19 15:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-19 0:58 Moving kernel_entry to LOADADDR Gerald Champagne
2001-10-19 1:13 ` Geoffrey Espin
2001-10-19 7:31 ` Gleb O. Raiko
2001-10-19 13:20 ` Maciej W. Rozycki
2001-10-19 15:11 ` Mike McDonald [this message]
2001-10-19 15:18 ` Gerald Champagne
2001-10-19 15:21 ` Justin Carlson
2001-10-19 15:56 ` Mike McDonald
2001-10-24 11:16 ` Florian Lohoff
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=200110191511.IAA27477@saturn.mikemac.com \
--to=mikemac@mikemac.com \
--cc=gerald.champagne@esstech.com \
--cc=linux-mips@oss.sgi.com \
--cc=macro@ds2.pg.gda.pl \
/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.