mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Smirnov Alexander <alllecs@yandex.ru>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: Re: [RFC] Introduce MIPS disassembler library for barebox
Date: Fri, 31 Jul 2015 20:26:15 +0300	[thread overview]
Message-ID: <1419861438363575@web21o.yandex.ru> (raw)
In-Reply-To: <20150724080634.GQ18700@pengutronix.de>

Hi Sascha,

24.07.2015, 11:06, "Sascha Hauer" <s.hauer@pengutronix.de>:
>  Hi Alexander,
>
>  On Thu, Jul 23, 2015 at 06:53:08PM +0300, Alexander Smirnov wrote:
>>   This commit imports disassembler for mips from qemu/binutils.
>>
>>   Here is a sample disassembler output:
>>
>>   barebox:/ disasm 0xbfc00018+0x20
>>   bfc00018: 401a6000 mfc0 k0,$12
>>   bfc0001c: 241bfffe li k1,-2
>>   bfc00020: 035bd024 and k0,k0,k1
>>   bfc00024: 409a6000 mtc0 k0,$12
>>   bfc00028: 3c09b400 lui t1,0xb400
>>   bfc0002c: 3c08df00 lui t0,0xdf00
>>   bfc00030: ad280068 sw t0,104(t1)
>>   bfc00034: 3c09bbe0 lui t1,0xbbe0
>>
>>   TODOs:
>>
>>     * -a option (select cpu architecture) does not work properly;
>>     * -s option (select binary file for disassembly) does not work properly .
>>
>>   This commit demonstrate simple way for importing disassembler from qemu/binutils:
>>   disassemblers for other architectures (e.g. ARM) can be easely imported.
>
>  This is nice and somehow cool to be able to just disassemble some code
>  under barebox. However, it's quite a bunch of code imported from another
>  project and we'll need even more code for other architectures. This code
>  needs maintenance to stay useful, so I am not very fond of merging it.
>  What is your usecase for this? Normally I would transfer the area I'd
>  like to disassemble via tftp or whatever to a host and disassemble it
>  there, but that it something that I need very seldomly.
>
I carry out this work for educational purposes.
I study programming for embedded systems.
I run barebox for mips as an exercise.
Work on the disassembler will allow me to get better acquainted with the MIPS instruction set.
I'm on vacation now.
I plan to finish disassembler after the vacation ends.
Options -s and -a are not working in the current version, I plan to fix it.
If you think the disassembler pulls too much code from other projects, I'll keep the finished version in my separate branch on github.

-- 
Smirnov Alexander

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

      reply	other threads:[~2015-07-31 17:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-23 15:53 Alexander Smirnov
2015-07-24  8:06 ` Sascha Hauer
2015-07-31 17:26   ` Smirnov Alexander [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=1419861438363575@web21o.yandex.ru \
    --to=alllecs@yandex.ru \
    --cc=barebox@lists.infradead.org \
    --cc=s.hauer@pengutronix.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