[Top] [All Lists]

Re: Fixed kernel entry point suggestion

To: Dan Malek <>
Subject: Re: Fixed kernel entry point suggestion
From: Adil Hafeez <>
Date: Fri, 30 Dec 2005 14:36:22 +0500
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta;; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=QTtfqt4IHcNcaZ7bM7I4LIhfjut69o6C6bSNZtWF/dr5kWuUx/BXWbssmk/RYStrf6W2OunNNhqlxDkquNBBYMMymfgmGKkJfY2ZXPC2BS26AvBylqF80o/Jbqfyf2nylvIP0JIc/mFW1BNYhbZVF6n77pyIKD5n1vrQUqgcNjY=
In-reply-to: <>
Original-recipient: rfc822;
References: <> <>
Hi Dan,
Here is the patch.
diff --git a/arch/mips/kernel/head.S b/arch/mips/kernel/head.S
index eebdaa2..a5e6d4e 100644
--- a/arch/mips/kernel/head.S
+++ b/arch/mips/kernel/head.S
@@ -28,6 +28,7 @@
#include <asm/mipsregs.h>
#include <asm/stackframe.h>

+        j kernel_entry
* Reserved space for exception handlers.

On 12/28/05, Dan Malek <> wrote:

On Dec 28, 2005, at 2:36 AM, Adil Hafeez wrote:

> Everytime we add/remove a feature from kernel location of entry_point
> symbol changes.

If you "wrap" the kernel image with a simple header and have a boot
that understands this, or even understands the ELF header, or download
S-records (yuk) as most systems do, I guess it isn't necessary to fix
I've been providing the compressed zImage patches for a long time that
this, as well as the u-boot uImage patches.  The process of building
images not only locates the proper entry point, but it provides
for embedded systems by creating smaller images and faster boot times.

>  .....   Adding a simply jump instruction to kernel_entry point in
> head.S can solve this problem. Why dont we make this change permanent
> in kernel.

:-)  It seems MIPS likes to be different from other architectures that
solved these irritating little details years ago :-)  Submit a patch
and see
what happens, as just complaining on the list isn't likely to make it


       -- Dan

Attachment: kernel_entry-fix.patch
Description: Text document

<Prev in Thread] Current Thread [Next in Thread>