Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Geoffrey Espin <espin@idiom.com>
To: Gerald Champagne <gerald.champagne@esstech.com>
Cc: "linux-mips@oss.sgi.com" <linux-mips@oss.sgi.com>
Subject: Re: Moving kernel_entry to LOADADDR
Date: Thu, 18 Oct 2001 18:13:22 -0700	[thread overview]
Message-ID: <20011018181322.B56244@idiom.com> (raw)
In-Reply-To: <3BCF7AD2.2000000@esstech.com>; from Gerald Champagne on Thu, Oct 18, 2001 at 07:58:58PM -0500

Gerald,

> to hard-code a jump to kernel_entry in my boot loader.  I got tired
> of having kernel_entry moving around, so I just moved it to the top
> of head.S, just afte the ".fill 0x280".  That places kernel_entry at
> the same place every time.  It's always at LOADADDR+0x280.

Don't know about all .fill & exception vecs... the trick I use in
my (vr)boot loader...

KERNEL_ENTRY=$(shell awk '/kernel_entry/{print "0x" $$1}' $(LINUX_SRC)/System.map)
CFLAGS+=-DKERNEL_ENTRY=$(KERNEL_ENTRY)

And compile boot.S or whatever your bootloader is.

But a fixed, well-known offset can't be a bad thing either.

Geoff
-- 
Geoffrey Espin espin@idiom.com

  reply	other threads:[~2001-10-19  1:13 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 [this message]
2001-10-19  7:31 ` Gleb O. Raiko
2001-10-19 13:20 ` Maciej W. Rozycki
2001-10-19 15:11   ` Mike McDonald
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=20011018181322.B56244@idiom.com \
    --to=espin@idiom.com \
    --cc=gerald.champagne@esstech.com \
    --cc=linux-mips@oss.sgi.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