From: Sean Chen <sean.chen1234@gmail.com>
To: paawan oza <paawan1982@yahoo.com>
Cc: Michael Snyder <msnyder@vmware.com>, Hui Zhu <teawater@gmail.com>,
"gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: porting reversible on arm/mips
Date: Mon, 22 Mar 2010 04:30:00 -0000 [thread overview]
Message-ID: <5e81cb501003212130v7af4e563xe5c108a33db308cc@mail.gmail.com> (raw)
In-Reply-To: <465493.20375.qm@web112516.mail.gq1.yahoo.com>
> 1) which Arm family/data sheet need to be refereed ?
DDI0100I_ARM_Architecture_Reference_Manual and
DDI0308C_thumb2_supplement are the latest basic documents. To
implement coprocessor instructions which is a plus such as VPF, NEON
and WMMX, you might need the coresponding specs.
> 2) I am planning to use 'target simulator' command, and cross compiling test programs for arm.
> so with that simulator I can finish everything except Linux ABI
Arm-elf is a choice. However, I am not sure whether it supports the
latest ARMv7 and Thumb2 instructions. I think a real ARM target or
QEMU is necessary, otherwise, it's very inconvenient for you to test
and implement the Linux function call handler.
> 3) and at the last step I will be trying to get arm kernel and finish linux ABI part.
You will need real ARM target or QEMU absolutely.
> PS : some way it is getting difficult to use qemu or other virtual emulation and fit it on to x86 emulating ARM.
QEMU is a good choice if you don't have any ARM target. You might need
to contact QEMU guys.
--
Best Regards,
Sean Chen
next prev parent reply other threads:[~2010-03-22 4:30 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-20 9:28 paawan oza
2010-03-22 4:30 ` Sean Chen [this message]
2010-03-22 12:31 ` Joseph S. Myers
2010-03-22 14:08 ` paawan oza
-- strict thread matches above, loose matches on Subject: below --
2009-12-10 2:42 About the link to wiki in reversible.html Hui Zhu
2009-12-10 8:14 ` porting reversible on arm/mips paawan oza
2009-12-10 23:59 ` Michael Snyder
2009-12-11 2:10 ` paawan oza
2009-12-11 2:15 ` Hui Zhu
2009-12-11 13:03 ` paawan oza
2009-12-11 16:38 ` Sean Chen
2009-12-11 3:12 ` Michael Snyder
2009-12-11 3:48 ` Sean Chen
2009-12-11 8:16 ` Jakob Engblom
2009-12-11 13:24 ` paawan oza
2009-12-11 16:42 ` Sean Chen
2009-12-11 16:35 ` Sean Chen
2009-12-11 13:07 ` paawan oza
2009-12-11 18:50 ` Michael Snyder
2009-12-11 19:04 ` Ramana Radhakrishnan
2009-12-11 19:14 ` Michael Snyder
2009-12-11 19:37 ` Ramana Radhakrishnan
2009-12-12 3:28 ` paawan oza
2009-12-14 15:42 ` paawan oza
2009-12-14 18:27 ` Michael Snyder
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=5e81cb501003212130v7af4e563xe5c108a33db308cc@mail.gmail.com \
--to=sean.chen1234@gmail.com \
--cc=gdb@sourceware.org \
--cc=msnyder@vmware.com \
--cc=paawan1982@yahoo.com \
--cc=teawater@gmail.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