All of lore.kernel.org
 help / color / mirror / Atom feed
From: "jeff" <jeff_lee@coventive.com>
To: "Thiemo Seufer" <ica2_ts@csv.ica.uni-stuttgart.de>
Cc: <linux-mips@linux-mips.org>
Subject: RE: Kernel 2.4.20
Date: Tue, 25 Feb 2003 16:46:55 +0800	[thread overview]
Message-ID: <LPECIADMAHLPOFOIEEFNCEMBCNAA.jeff_lee@coventive.com> (raw)
In-Reply-To: <20030225083321.GD25303@rembrandt.csv.ica.uni-stuttgart.de>

Dear Thiemo,
    We modified the head.S and the kernel_entry change to 0x80000798
(check from System.map) and we download this kernel to RAM address
0x80000000 and jump to 0x8000798 to execute. It show EXCEPTION...
And our bootloader will not handle ELF file format. But after build the kernel
image, we got two image, vmlinux and vmlinux.binary. vmlinux is FLE file
format and vmlinux.binary is only data (check by file). We download 
vmlinux.binary to test.

Regards,

Jeff

-----Original Message-----
From: Thiemo Seufer [mailto:ica2_ts@csv.ica.uni-stuttgart.de]
Sent: Tuesday, February 25, 2003 4:33 PM
To: jeff
Cc: linux-mips@linux-mips.org
Subject: Re: Kernel 2.4.20


jeff wrote:
> Dear Thiemo,
>     Thanks for your quickly response.
> I try to modify the /arch/mips/ld.script.in or /arch/mips/kernel/head.S

This won't help. The entry address is where the linker happens to
place the entry function. It may vary even for slight differences
in Kernel compilation.

> but still can't work (entry is changed but kernel can't work).

What does "can't work" mean? What happens exactly?

What sort of bootloader are you using? Normally it is able to
handle ELF properly, which makes this thing work automatically.

> Do I make any mistake?

Sounds so.


Thiemo

WARNING: multiple messages have this Message-ID (diff)
From: "jeff" <jeff_lee@coventive.com>
To: Thiemo Seufer <ica2_ts@csv.ica.uni-stuttgart.de>
Cc: linux-mips@linux-mips.org
Subject: RE: Kernel 2.4.20
Date: Tue, 25 Feb 2003 16:46:55 +0800	[thread overview]
Message-ID: <LPECIADMAHLPOFOIEEFNCEMBCNAA.jeff_lee@coventive.com> (raw)
Message-ID: <20030225084655.5Boqvr2wJ_L99logmnDtFlYNrSH2vWKwWOlu_wiZb48@z> (raw)
In-Reply-To: <20030225083321.GD25303@rembrandt.csv.ica.uni-stuttgart.de>

Dear Thiemo,
    We modified the head.S and the kernel_entry change to 0x80000798
(check from System.map) and we download this kernel to RAM address
0x80000000 and jump to 0x8000798 to execute. It show EXCEPTION...
And our bootloader will not handle ELF file format. But after build the kernel
image, we got two image, vmlinux and vmlinux.binary. vmlinux is FLE file
format and vmlinux.binary is only data (check by file). We download 
vmlinux.binary to test.

Regards,

Jeff

-----Original Message-----
From: Thiemo Seufer [mailto:ica2_ts@csv.ica.uni-stuttgart.de]
Sent: Tuesday, February 25, 2003 4:33 PM
To: jeff
Cc: linux-mips@linux-mips.org
Subject: Re: Kernel 2.4.20


jeff wrote:
> Dear Thiemo,
>     Thanks for your quickly response.
> I try to modify the /arch/mips/ld.script.in or /arch/mips/kernel/head.S

This won't help. The entry address is where the linker happens to
place the entry function. It may vary even for slight differences
in Kernel compilation.

> but still can't work (entry is changed but kernel can't work).

What does "can't work" mean? What happens exactly?

What sort of bootloader are you using? Normally it is able to
handle ELF properly, which makes this thing work automatically.

> Do I make any mistake?

Sounds so.


Thiemo

  reply	other threads:[~2003-02-25  8:41 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-24 12:07 Change -mcpu option for VR41xx Yoichi Yuasa
2003-02-24 20:21 ` Ralf Baechle
2003-02-25  3:48   ` Yoichi Yuasa
2003-02-25  7:58     ` Kernel 2.4.20 jeff
2003-02-25  7:58       ` jeff
2003-02-25  8:03       ` Thiemo Seufer
2003-02-25  8:17         ` jeff
2003-02-25  8:17           ` jeff
2003-02-25  8:33           ` Thiemo Seufer
2003-02-25  8:46             ` jeff [this message]
2003-02-25  8:46               ` jeff
2003-02-25  9:42               ` Thiemo Seufer
2003-02-25 17:47       ` Jun Sun
2003-02-25 13:18     ` Change -mcpu option for VR41xx Maciej W. Rozycki
2003-02-26  2:54       ` Yoichi Yuasa
2003-02-26 12:18         ` Maciej W. Rozycki
2003-02-27  1:41           ` Yoichi Yuasa
2003-02-27 12:05             ` Maciej W. Rozycki
2003-02-27 12:37               ` Yoichi Yuasa
2003-02-27 13:07                 ` Maciej W. Rozycki
2003-02-28  3:50                   ` Yoichi Yuasa
2003-05-23  6:19 kernel 2.4.20 Gurpreet Singh (SCM)
2003-05-23 18:51 ` Jan Knutar
2003-07-24  3:19 Kernel 2.4.20 David Munn
2003-07-24  4:57 ` Jeremy Utley
2003-07-24  8:01 ` Riley Williams
2004-01-13 11:10 kernel 2.4.20 gojyo
2004-01-13 15:51 ` Ducrot Bruno

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=LPECIADMAHLPOFOIEEFNCEMBCNAA.jeff_lee@coventive.com \
    --to=jeff_lee@coventive.com \
    --cc=ica2_ts@csv.ica.uni-stuttgart.de \
    --cc=linux-mips@linux-mips.org \
    /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.