From: aurelio remonda <aurelioremonda@gmail.com>
To: Liviu Ionescu <ilg@livius.net>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Daniel Gutson <daniel.gutson@tallertechnologies.com>,
qemu-devel@nongnu.org,
Martin Galvan <martin.galvan@tallertechnologies.com>
Subject: Re: [Qemu-devel] [PATCH] Target-arm: Add the Cortex-M4 CPU
Date: Fri, 29 May 2015 09:55:48 -0300 [thread overview]
Message-ID: <CAE_j2psCPEpmF__QNU-kAH2EVT1HX9MAq7_RPYqvWaT583ifFg@mail.gmail.com> (raw)
In-Reply-To: <CAF3C4AD-953F-4A50-AAF1-52B2136CB5AB@livius.net>
2015-05-28 18:22 GMT-03:00 Liviu Ionescu <ilg@livius.net>:
> > On 29 May 2015, at 00:09, Aurelio C. Remonda <aurelioremonda@gmail.com> wrote:
> > The optional FPU in the M4 could be added in the future as a "Cortex-M4F" CPU.
>
> in my implementation I had a single name ("cortex-m4") and some flags, but a separate name is probably better. can we reserve
>
> { .name = "cortex-m4f", ... }
>
> for this purpose?
Thanks for the feedback! Yes, we could but I think its outside of the
scope of this particular contribution.
> > All we'd have to do is add the ARM_FEATURE_VFP4 to the initfn.
>
> if it is that simple, why don't we add it in for now?
As Peter said, it may not actually be that simple.
Perhaps we could commit this now and add the VFP in the future?
next prev parent reply other threads:[~2015-05-29 12:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-28 21:09 [Qemu-devel] [PATCH] Target-arm: Add the Cortex-M4 CPU Aurelio C. Remonda
2015-05-28 21:22 ` Liviu Ionescu
2015-05-28 22:03 ` Peter Maydell
2015-05-29 12:55 ` aurelio remonda [this message]
2015-05-29 13:21 ` Peter Maydell
2015-05-29 19:15 ` Liviu Ionescu
2015-05-29 19:16 ` Martin Galvan
2015-05-29 19:30 ` Peter Maydell
2015-06-10 9:58 ` Liviu Ionescu
2015-06-10 10:44 ` Peter Maydell
2015-06-10 10:49 ` Daniel Gutson
2015-06-10 10:53 ` Peter Maydell
2015-05-30 10:46 ` Peter Crosthwaite
2015-05-30 22:08 ` aurelio remonda
2015-05-30 23:16 ` Peter Crosthwaite
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_j2psCPEpmF__QNU-kAH2EVT1HX9MAq7_RPYqvWaT583ifFg@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).