From: aurelio remonda <aurelioremonda@gmail.com>
To: alistair23@gmail.com, peter.maydell@linaro.org,
peter.crosthwaite@xilinx.com, qemu-devel@nongnu.org
Subject: [Qemu-devel] [ARM]: Adding support for Cortex-M4
Date: Tue, 5 May 2015 09:52:47 -0300 [thread overview]
Message-ID: <CAE_j2puKSpCBMhsS5WvsaozQ0AprS_EFO0eHdWruJPWJW13-xQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 672 bytes --]
Hi, i would like to to add support for cortex-m4 on qemu. Most features of
the Cortex-M3 and M4 are the same with the significant difference that
Cortex-M4 has DSP extensions and optional FPU. Even so, i really need some
pointers for this (im a newbie on qemu devel). I found out that qemu can
manage dsp instructions such as ADD16, ASX, SAX, etc. and all their
combinations with suffixes (u, s, sh, etc.), so half (if not all) of the
work is done.
How should I go about this? What's the standard procedure for adding a new
CPU, even if it's so similar to the existing ones? That is, which are the
relevant functions/files that I should modify, and so on.
Thanks a lot!
[-- Attachment #2: Type: text/html, Size: 751 bytes --]
next reply other threads:[~2015-05-05 12:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-05 12:52 aurelio remonda [this message]
2015-05-05 13:04 ` [Qemu-devel] [ARM]: Adding support for Cortex-M4 Peter Maydell
[not found] ` <CAE_j2pu_S=dDcm9aTh_EoTMpwV-5coPiy6O0Em7H==7h8hWueg@mail.gmail.com>
[not found] ` <CAFEAcA824ioMJq+3WdB3qkj9WR80M_CEeZhXzokpiHgzBjvRjQ@mail.gmail.com>
2015-05-12 12:46 ` aurelio remonda
2015-05-12 12:58 ` Peter Maydell
2015-05-26 15:29 ` aurelio remonda
2015-05-26 15:36 ` Peter Maydell
2015-05-26 17:13 ` aurelio remonda
2015-05-26 17:34 ` Peter Maydell
2015-05-28 15:28 ` aurelio remonda
2015-05-28 16:00 ` Liviu Ionescu
2015-05-30 19:27 ` Liviu Ionescu
2015-05-30 20:10 ` Peter Crosthwaite
2015-05-30 20:54 ` Peter Maydell
2015-05-30 20:58 ` Peter Crosthwaite
2015-05-05 13:12 ` Liviu Ionescu
2015-05-07 18:00 ` aurelio remonda
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=CAE_j2puKSpCBMhsS5WvsaozQ0AprS_EFO0eHdWruJPWJW13-xQ@mail.gmail.com \
--to=aurelioremonda@gmail.com \
--cc=alistair23@gmail.com \
--cc=peter.crosthwaite@xilinx.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
/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;
as well as URLs for NNTP newsgroup(s).