From: Peter Maydell <peter.maydell@linaro.org>
To: Randy Yates <yates@digitalsignallabs.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: QEMU Development Questions
Date: Fri, 17 Apr 2020 16:53:17 +0100 [thread overview]
Message-ID: <CAFEAcA8uL3V8aa=0UfYsYTKRPpM+5D62vgTDG6qouLObtzmJTQ@mail.gmail.com> (raw)
In-Reply-To: <87o8rqdsds.fsf@digitalsignallabs.com>
On Fri, 17 Apr 2020 at 16:50, Randy Yates <yates@digitalsignallabs.com> wrote:
>
> Thanks for the answers I've received so far - much appreciated.
>
> Is there a standard way to define your own custom coprocessor CP15 registers?
It can be done but you very likely don't want to do it...
thanks
-- PMM
next prev parent reply other threads:[~2020-04-17 15:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-17 15:49 QEMU Development Questions Randy Yates
2020-04-17 15:53 ` Peter Maydell [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-04-17 1:46 Randy Yates
2020-04-17 8:51 ` Peter Maydell
2020-04-17 11:40 ` BALATON Zoltan
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='CAFEAcA8uL3V8aa=0UfYsYTKRPpM+5D62vgTDG6qouLObtzmJTQ@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=yates@digitalsignallabs.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;
as well as URLs for NNTP newsgroup(s).