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
.text
/*
* Reserved space for exception handlers.
On 12/28/05, Dan Malek < dan@xxxxxxxxxxxxxxxxx> wrote:
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
.text
/*
* Reserved space for exception handlers.
On 12/28/05, Dan Malek < dan@xxxxxxxxxxxxxxxxx> 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
loader
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
this.
I've been providing the compressed zImage patches for a long time that
solves
this, as well as the u-boot uImage patches. The process of building
these
images not only locates the proper entry point, but it provides
advantages
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
have
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
happen.
Thanks.
-- Dan
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 .text /* * Reserved space for exception handlers.
