From: "Keith Packard" via <qemu-devel@nongnu.org>
To: Max Filippov <jcmvbkbc@gmail.com>,
Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-arm <qemu-arm@nongnu.org>, QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [PATCH] hw/arm: Add 'virtm' hardware
Date: Fri, 26 Jun 2020 13:14:30 -0700 [thread overview]
Message-ID: <877dvtinyx.fsf@keithp.com> (raw)
In-Reply-To: <CAMo8Bf+57b=u12nMp4EWaza3WdOQpx_L_O=HvdouM99wW-Xe=A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 315 bytes --]
Max Filippov <jcmvbkbc@gmail.com> writes:
> Most of them are due to unsupported/differently implemented
> syscalls.
Yeah, I think that was the basis of my confusion -- qemu-arm is not a
bare metal environment, and my work is focused on enabling application
development in that environment.
--
-keith
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2020-06-26 20:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-25 23:07 [PATCH] hw/arm: Add 'virtm' hardware Keith Packard via
2020-06-26 8:38 ` Peter Maydell
2020-06-26 16:40 ` Keith Packard via
2020-06-26 17:31 ` Peter Maydell
2020-06-26 18:02 ` Max Filippov
2020-06-26 20:14 ` Keith Packard via [this message]
2020-06-26 21:40 ` Peter Maydell
2020-06-26 20:12 ` Keith Packard via
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=877dvtinyx.fsf@keithp.com \
--to=qemu-devel@nongnu.org \
--cc=jcmvbkbc@gmail.com \
--cc=keithp@keithp.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@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).