From: Paolo Bonzini <pbonzini@redhat.com>
To: Alexander Graf <graf@campus.tu-berlin.de>,
Alexander Graf <alexander.graf@ilr.tu-berlin.de>,
Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] hw/arm: add Lego NXT board
Date: Wed, 16 Jul 2014 10:50:17 +0200 [thread overview]
Message-ID: <53C63CC9.3020304@redhat.com> (raw)
In-Reply-To: <53C63A93.5000704@campus.tu-berlin.de>
Il 16/07/2014 10:40, Alexander Graf ha scritto:
>>>
>
>> I think that there are two other ways to do it.
>
> And what about the chardev way? Your silence in this regard is
> misterious ;-)
The main problem with chardevs is that they are completely asynchronous.
So they may not be a good match for your use case.
(In fact, this is a problem for the i2c-over-chardev and especially
spi-over-chardev ideas I shot out yesterday. For i2c-over-chardev one
could add support to clock stretching in QEMU, but SPI is entirely
synchronous).
Note that -qmp and -qtest both use chardevs internally to connect the
external program with QEMU.
Paolo
>>
>> 1) [...]
>> 2) [...]
>
> Thanks a lot for your suggestions. I will play a bit and come back when
> I have some code to show.
prev parent reply other threads:[~2014-07-16 8:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-13 14:20 [Qemu-devel] hw/arm: add Lego NXT board Alexander Graf
2014-07-14 11:23 ` Peter Crosthwaite
2014-07-14 11:46 ` Paolo Bonzini
2014-07-14 18:09 ` Alexander Graf
2014-07-14 20:37 ` Paolo Bonzini
2014-07-14 21:10 ` Alexander Graf
2014-07-14 22:48 ` Peter Maydell
2014-07-15 7:06 ` Paolo Bonzini
2014-07-15 10:26 ` Alexander Graf
2014-07-15 10:53 ` Paolo Bonzini
2014-07-15 18:55 ` Alexander Graf
2014-07-15 20:09 ` Paolo Bonzini
2014-07-16 8:40 ` Alexander Graf
2014-07-16 8:50 ` Paolo Bonzini [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=53C63CC9.3020304@redhat.com \
--to=pbonzini@redhat.com \
--cc=alexander.graf@ilr.tu-berlin.de \
--cc=graf@campus.tu-berlin.de \
--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).