Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "Kevin D. Kissell" <kevink@mips.com>
To: "Dmitriy Tochansky" <toch@dfpost.ru>, <linux-mips@linux-mips.org>
Subject: Re: Strange instruction
Date: Thu, 14 Oct 2004 10:34:18 +0200	[thread overview]
Message-ID: <01d901c4b1c8$996b7b30$10eca8c0@grendel> (raw)
In-Reply-To: 20041014115304.3edbe141.toch@dfpost.ru

That's a 64-bit add, which is actually being used as a 64-bit move
of the "sp" register to k1.  Try "objdump -m mips:isa64" (or whatever
variant gives your version of objdump the right to disassemble the
MIPS III+/MIPS64 instructions.

One might suspect that your board monitor ROM was built for a 64-bit CPU.
This illustrates why, if one want to write portable assembler code for MIPS,
one should implement "move" operations as OR Target,$0,Source rather than
using an ADDU or DADDU...

----- Original Message ----- 
From: "Dmitriy Tochansky" <toch@dfpost.ru>
To: <linux-mips@linux-mips.org>
Sent: Thursday, October 14, 2004 13:53
Subject: Strange instruction


> Hello!
> 
> When starts kernel for my au1500 board reseting board. After disassembling I found instruction
> which reseting board. Here is few strings of "mipsel-linux-objdump -D vmlinux" output:
> 
> ---
> 
> a0000650:       07400003        bltz    k0,a0000660 <nmi_handler+0x1c>          
> a0000654:       03a0d82d        0x3a0d82d                                       
> a0000658:       3c1ba020        lui     k1,0xa020 
> 
> ---
> 
> Base address changed by me.
> 
> What is A0000654? There is board resets.
> 
> 

WARNING: multiple messages have this Message-ID (diff)
From: "Kevin D. Kissell" <kevink@mips.com>
To: Dmitriy Tochansky <toch@dfpost.ru>, linux-mips@linux-mips.org
Subject: Re: Strange instruction
Date: Thu, 14 Oct 2004 10:34:18 +0200	[thread overview]
Message-ID: <01d901c4b1c8$996b7b30$10eca8c0@grendel> (raw)
Message-ID: <20041014083418.aL0hkJHlkbSict3LBqqatAuDCGXq3IhC64HjqG8wMTk@z> (raw)
In-Reply-To: 20041014115304.3edbe141.toch@dfpost.ru

That's a 64-bit add, which is actually being used as a 64-bit move
of the "sp" register to k1.  Try "objdump -m mips:isa64" (or whatever
variant gives your version of objdump the right to disassemble the
MIPS III+/MIPS64 instructions.

One might suspect that your board monitor ROM was built for a 64-bit CPU.
This illustrates why, if one want to write portable assembler code for MIPS,
one should implement "move" operations as OR Target,$0,Source rather than
using an ADDU or DADDU...

----- Original Message ----- 
From: "Dmitriy Tochansky" <toch@dfpost.ru>
To: <linux-mips@linux-mips.org>
Sent: Thursday, October 14, 2004 13:53
Subject: Strange instruction


> Hello!
> 
> When starts kernel for my au1500 board reseting board. After disassembling I found instruction
> which reseting board. Here is few strings of "mipsel-linux-objdump -D vmlinux" output:
> 
> ---
> 
> a0000650:       07400003        bltz    k0,a0000660 <nmi_handler+0x1c>          
> a0000654:       03a0d82d        0x3a0d82d                                       
> a0000658:       3c1ba020        lui     k1,0xa020 
> 
> ---
> 
> Base address changed by me.
> 
> What is A0000654? There is board resets.
> 
> 

  reply	other threads:[~2004-10-14  8:29 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-14 11:53 Strange instruction Dmitriy Tochansky
2004-10-14  8:34 ` Kevin D. Kissell [this message]
2004-10-14  8:34   ` Kevin D. Kissell
2004-10-14 12:12   ` Thiemo Seufer
2004-10-14 12:16     ` Nigel Stephens
2004-10-14 12:36       ` Thiemo Seufer
2004-10-14 13:12         ` Kevin D. Kissell
2004-10-14 13:12           ` Kevin D. Kissell
2004-10-14 13:34           ` Thiemo Seufer
2004-10-14  8:45 ` Fuxin Zhang
     [not found]   ` <000b01c4b1da$6e049f00$10eca8c0@grendel>
     [not found]     ` <416E5B62.8050508@ict.ac.cn>
2004-10-14 11:13       ` Kevin D. Kissell
2004-10-14 11:13         ` Kevin D. Kissell
2004-10-14 13:45 ` Dan Malek
2004-10-14 19:06   ` Dan Malek

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='01d901c4b1c8$996b7b30$10eca8c0@grendel' \
    --to=kevink@mips.com \
    --cc=linux-mips@linux-mips.org \
    --cc=toch@dfpost.ru \
    /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