qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: aurelio remonda <aurelioremonda@gmail.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Liviu Ionescu <ilg@livius.net>,
	Daniel Gutson <daniel.gutson@tallertechnologies.com>,
	QEMU Developers <qemu-devel@nongnu.org>,
	Martin Galvan <martin.galvan@tallertechnologies.com>
Subject: Re: [Qemu-devel] [PATCH V4] Target-arm: Add the Cortex-M4 CPU
Date: Tue, 16 Jun 2015 11:35:44 -0300	[thread overview]
Message-ID: <CAE_j2psVATMjShBREAAgn5_Z+Cnqn66PPD2PbbhfxSK8s-2Syw@mail.gmail.com> (raw)
In-Reply-To: <CAFEAcA9S61Aa8v=-HRd_J9ERYj+Rt-n2CZFYAhfJAgMcCkSRAA@mail.gmail.com>

Thank you!

2015-06-16 11:20 GMT-03:00 Peter Maydell <peter.maydell@linaro.org>:
> On 16 June 2015 at 14:37, Aurelio C. Remonda <aurelioremonda@gmail.com> wrote:
>> This patch adds the Cortex-M4 CPU. The M4 is basically the
>> same as the M3, the main differences being the DSP instructions and an
>> optional FPU. Created an ARM_FEATURE_THUMB_DSP to be added to any non-M
>> thumb2-compatible CPU that uses DSP instructions, and manually added it to
>> the M4 in its initfn. The THUMB_DSP feature was created in a different patch
>> along with the bit checking on each DSP instruction. Only no-FPU cortex-M4 is
>> implemented here, cortex-M4F is not because the core target-arm code doesn't
>> support the M-profile FPU model yet.
>>
>> Signed-off-by: Aurelio C. Remonda <aurelioremonda@gmail.com>
>
> Applied to target-arm.next, thanks.
>
> -- PMM

      reply	other threads:[~2015-06-16 14:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-16 13:37 [Qemu-devel] [PATCH V4] Target-arm: Add the Cortex-M4 CPU Aurelio C. Remonda
2015-06-16 14:20 ` Peter Maydell
2015-06-16 14:35   ` aurelio remonda [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=CAE_j2psVATMjShBREAAgn5_Z+Cnqn66PPD2PbbhfxSK8s-2Syw@mail.gmail.com \
    --to=aurelioremonda@gmail.com \
    --cc=daniel.gutson@tallertechnologies.com \
    --cc=ilg@livius.net \
    --cc=martin.galvan@tallertechnologies.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).