qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Fabien Chouteau <chouteau@adacore.com>
To: "Andreas Färber" <afaerber@suse.de>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	Paul Brook <paul@codesourcery.com>
Subject: Re: [Qemu-devel] [ARM] Cortex-R4F and VFP3-D16
Date: Mon, 04 Mar 2013 10:58:49 +0100	[thread overview]
Message-ID: <51347059.4090407@adacore.com> (raw)
In-Reply-To: <5130F958.3010108@suse.de>

On 03/01/2013 07:54 PM, Andreas Färber wrote:
> Am 27.02.2013 18:25, schrieb Fabien Chouteau:
>> On 02/27/2013 05:58 PM, Peter Maydell wrote:
>>> On 27 February 2013 16:37, Fabien Chouteau <chouteau@adacore.com> wrote:
>>>> I'm making my first steps in the ARM world by looking at R4F
>>>> implementation. More specifically I'm trying to add VFP3-D16 support
>>>> which is, as far as I understand, a regular VFP3 with only 16 D
>>>> registers instead of 32.
>>>
>>> Andreas was looking at Cortex-R4(F) support a while back; you should
>>> talk to him about how far he got with that (and google for the mailing
>>> list archives for my comments on his patches, probably).
>>>
>>
>> I already found these patches, and I base my work on them. I also
>> contacted Andreas to know if he made progress on this support, but
>> didn't get the answer yet.
> 
> I've sent one in the meantime, you can't expect me to be available 24/7.
> 

It's OK, I wasn't complaining :)

> In short:
> http://repo.or.cz/w/qemu/afaerber.git/shortlog/refs/heads/cortex-r4f is
> about what I've got. Feel free to reuse and extend/change as you see fit.
>

Thanks, I already started to use it.

Regards,

-- 
Fabien Chouteau

      reply	other threads:[~2013-03-04  9:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <512E3637.6070609@adacore.com>
     [not found] ` <CAFEAcA8gyz=b4xFW9NfqnLJx=azJwUovCDg_j3m5Gq-tyjze0Q@mail.gmail.com>
     [not found]   ` <512E4170.4070003@adacore.com>
     [not found]     ` <201302272049.59409.paul@codesourcery.com>
     [not found]       ` <512F6336.6090206@adacore.com>
     [not found]         ` <CAFEAcA8Ah2JQSA3XxWA=qbzecrcKXgNx-=gtaC9bfoFTuusq5g@mail.gmail.com>
     [not found]           ` <512F965B.1000007@adacore.com>
     [not found]             ` <CAFEAcA8fzFnDb-MDh5Wo3X77qwc-TnU-M4yvzBejNu2394LAmg@mail.gmail.com>
2013-03-01 10:13               ` [Qemu-devel] [ARM] Cortex-R4F and VFP3-D16 Fabien Chouteau
2013-03-01 10:40                 ` Peter Maydell
2013-03-01 11:21                   ` Fabien Chouteau
2013-03-01 11:32                     ` Peter Maydell
2013-03-01 12:07                       ` Fabien Chouteau
2013-03-01 12:16                         ` Peter Maydell
2013-03-01 13:43                           ` Fabien Chouteau
2013-03-01 15:10                             ` Fabien Chouteau
2013-03-01 15:22                               ` Peter Maydell
2013-03-01 18:54     ` Andreas Färber
2013-03-04  9:58       ` Fabien Chouteau [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=51347059.4090407@adacore.com \
    --to=chouteau@adacore.com \
    --cc=afaerber@suse.de \
    --cc=paul@codesourcery.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).