From: Stefan Hajnoczi <stefanha@gmail.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Steffen Görtz" <contrib@steffen-goertz.de>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Joel Stanley" <joel@jms.id.au>,
"Jim Mussared" <jim@groklearning.com>,
"Julia Suvorova" <jusual@mail.ru>,
"Eric Blake" <eblake@redhat.com>,
"Markus Armbruster" <armbru@redhat.com>,
"open list:ARM" <qemu-arm@nongnu.org>
Subject: Re: [Qemu-devel] [RFC v3] qapi: command category to stimulate high-level machine devices
Date: Fri, 8 Jun 2018 09:01:14 +0100 [thread overview]
Message-ID: <20180608080114.GG29183@stefanha-x1.localdomain> (raw)
In-Reply-To: <20180607125853.5hcd2bhhjedfngre@sirius.home.kraxel.org>
[-- Attachment #1: Type: text/plain, Size: 814 bytes --]
On Thu, Jun 07, 2018 at 02:58:53PM +0200, Gerd Hoffmann wrote:
> > Gerd: What is your preference? Do you want board-specific fake displays
> > inside the QEMU process as the long-term direction for UIs?
>
> Well, it isn't the one or the other, we could actually do both. For the
> deployments you are looking for the websocket approach proably works
> best. Being able to do at least simple stuff (say led display and
> a+b+reset buttons) with a fake display, without requiring setting up
> something separate for the UI can be quite useful too.
>
> Your call.
Okay. There is an existing micro:bit web UI that we're interested in
either reusing or at least closely following as a model
(https://groklearning.com/learn/hoc-virtual-pet/intro/2/), so WebSockets
makes sense for this.
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
next prev parent reply other threads:[~2018-06-08 8:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-03 20:34 [Qemu-devel] [RFC v3] qapi: command category to stimulate high-level machine devices Steffen Görtz
2018-06-03 20:41 ` no-reply
2018-06-03 20:42 ` no-reply
2018-06-04 9:20 ` Stefan Hajnoczi
2018-06-04 9:29 ` Peter Maydell
2018-06-04 10:12 ` Gerd Hoffmann
2018-06-07 10:24 ` Stefan Hajnoczi
2018-06-07 10:33 ` Daniel P. Berrangé
2018-06-08 7:58 ` Stefan Hajnoczi
2018-06-07 12:58 ` Gerd Hoffmann
2018-06-08 8:01 ` Stefan Hajnoczi [this message]
2018-06-04 9:56 ` Gerd Hoffmann
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=20180608080114.GG29183@stefanha-x1.localdomain \
--to=stefanha@gmail.com \
--cc=armbru@redhat.com \
--cc=contrib@steffen-goertz.de \
--cc=eblake@redhat.com \
--cc=jim@groklearning.com \
--cc=joel@jms.id.au \
--cc=jusual@mail.ru \
--cc=kraxel@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.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).