From: Scott A McConnell <samcconn@cotw.com>
To: linux-mips@oss.sgi.com
Subject: Link problems with 2.4.3 kernel
Date: Mon, 16 Apr 2001 13:09:37 -0700 [thread overview]
Message-ID: <3ADB5181.BCE02A9@cotw.com> (raw)
Using Hardhat linux targeting a NEC VR5432 and a 2.4.0-test 5 kernel I
get an image that looks like the following:
vmlinux: file format elf32-littlemips
Disassembly of section .text:
0000000080001000 <_ftext>:
...
80002000: 6e 01 00 10 00 00 00 00 00 00 00 00 00 00 00 00
n...............
...
0000000080002288 <except_vec0_r4000>:
....
00000000800025bc <kernel_entry>:
--------------------------------------
using the cvs 2.4.3 kernel (about a week old) and the same tool chain I
get an image that looks like:
Using a loadaddr of 8000000
vmlinux: file format elf32-littlemips
Disassembly of section .text:
0000000080000000 <_ftext>:
80000000: 6b 01 00 10 00 00 00 00 00 00 00 00 00 00 00 00
k...............
...
0000000080000288 <except_vec0_r4000>:
....
00000000800005b0 <kernel_entry>:
...
--------------------------------------
If I change the loadaddr to 80001000 I get:
vmlinux: file format elf32-littlemips
Disassembly of section .text:
0000000080002000 <_ftext>:
80002000: 6b 01 00 10 00 00 00 00 00 00 00 00 00 00 00 00
k...............
...
0000000080002288 <except_vec0_r4000>:
....
00000000800025b0 <kernel_entry>:
-------------------------------------
No matter what I do I can not get _ftext to appear at 80001000. I use
identical ld.scripts for bother kernels.
At first I thought it was my binutils so I switched to the same tools
that I used with my 2.4.0-test5 kernel.
Addresses appear to be off by 0x1000. Which is why my 2.4.3 kernel dies
on the jump to init_arch out of kernel_entry.
Any thoughts about what I might be doing wrong?
Thanks,
Scott
next reply other threads:[~2001-04-16 19:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-16 20:09 Scott A McConnell [this message]
2001-04-17 16:32 ` Link problems with 2.4.3 kernel Ralf Baechle
2001-04-17 17:48 ` Scott A McConnell
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=3ADB5181.BCE02A9@cotw.com \
--to=samcconn@cotw.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