| To: | Gerald Champagne <gerald.champagne@esstech.com> |
|---|---|
| Subject: | Re: Moving kernel_entry to LOADADDR |
| From: | Geoffrey Espin <espin@idiom.com> |
| Date: | Thu, 18 Oct 2001 18:13:22 -0700 |
| Cc: | "linux-mips@oss.sgi.com" <linux-mips@oss.sgi.com> |
| In-reply-to: | <3BCF7AD2.2000000@esstech.com>; from Gerald Champagne on Thu, Oct 18, 2001 at 07:58:58PM -0500 |
| References: | <3BCF7AD2.2000000@esstech.com> |
| Sender: | owner-linux-mips@oss.sgi.com |
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
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Moving kernel_entry to LOADADDR, Gerald Champagne |
|---|---|
| Next by Date: | Strange behavior of serial console under 2.4.9, H . J . Lu |
| Previous by Thread: | Moving kernel_entry to LOADADDR, Gerald Champagne |
| Next by Thread: | Re: Moving kernel_entry to LOADADDR, Gleb O. Raiko |
| Indexes: | [Date] [Thread] [Top] [All Lists] |