From: Shinya Kuribayashi <skuribay@ruby.dti.ne.jp>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] Allow building mips versions with ELDK 3.1.1
Date: Tue, 06 May 2008 11:37:49 +0900 [thread overview]
Message-ID: <481FC47D.3050505@ruby.dti.ne.jp> (raw)
In-Reply-To: <20080505124655.3870E24764@gemini.denx.de>
Wolfgang Denk wrote:
> In message <481EE9A0.60403@windriver.com> you wrote:
>> .gpword works only with local symbols on certain binutils versions
>>
>> Signed-off-by: Vlad Lungu <vlad.lungu@windrvier.com>
>> ---
>> cpu/mips/start.S | 9 ++++++---
>> 1 files changed, 6 insertions(+), 3 deletions(-)
>
> Applied, thanks a lot.
>
> This fixes the start.S erros/warnings.
This patch works with my two different CPUs. Thanks!
> So the only obvious problem remaining for MIPS are the cache.S
> warnings:
>
> cache.S:243: Warning: Pretending global symbol used as branch target is local.
> cache.S:250: Warning: Pretending global symbol used as branch target is local.
Assembler might be sensitive to global symbol references under PIC code
because they should be processed through GOT in principle.
Therefore, we should have set up function entry point explicitly like:
diff --git a/cpu/mips/cache.S b/cpu/mips/cache.S
index 8024a2e..7966079 100644
--- a/cpu/mips/cache.S
+++ b/cpu/mips/cache.S
@@ -239,14 +239,16 @@ NESTED(mips_cache_reset, 0, ra)
*/
move a1, t2
move a2, t4
- bal mips_init_icache
+ PTR_LA t7, mips_init_icache
+ jalr t7
/*
* then initialize D-cache.
*/
move a1, t3
move a2, t5
- bal mips_init_dcache
+ PTR_LA t7, mips_init_dcache
+ jalr t7
jr RA
END(mips_cache_reset)
I'll post the patch later.
thanks,
Shinya
prev parent reply other threads:[~2008-05-06 2:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-05 11:04 [U-Boot-Users] [PATCH] Allow building mips versions with ELDK 3.1.1 Vlad Lungu
2008-05-05 12:46 ` Wolfgang Denk
2008-05-06 2:37 ` Shinya Kuribayashi [this message]
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=481FC47D.3050505@ruby.dti.ne.jp \
--to=skuribay@ruby.dti.ne.jp \
--cc=u-boot@lists.denx.de \
/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