From: Paolo Bonzini <pbonzini@redhat.com>
To: Alexander Graf <graf@campus.tu-berlin.de>, qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org
Subject: Re: [Qemu-devel] hw/arm: add Lego NXT board
Date: Mon, 14 Jul 2014 22:37:47 +0200 [thread overview]
Message-ID: <53C43F9B.6090907@redhat.com> (raw)
In-Reply-To: <53C41CEC.5030705@campus.tu-berlin.de>
Il 14/07/2014 20:09, Alexander Graf ha scritto:
> So the protocol basically allows to forward read and write accesses on
> IO memory to processes outside of Qemu.
>
> Get and set transactions are triggered by Qemu on an IO memory read
> operation or write operation respectively. The pipe communication blocks
> Qemu until a value is available/the value was published.
The obvious thing to consider is whether this could be used to
circumvent the GPL.
I think a generic memory-mapped I/O device interface is not a good idea
in this respect, also because it's hard to get it right. But i2c is
simple enough, and there are so many devices with a 4-page datasheet,
that I think it would be acceptable. You could also write an i2c
passthrough chardev backend that connects to /dev/i2c* and lets the
guest access slaves in the host.
Paolo
> I like the *-over-chardev idea. This could be a benefit for people who
> want to couple simulators or test oracles for embedded system tests or
> in general to other software in a simple way.
next prev parent reply other threads:[~2014-07-14 20:38 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 [this message]
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
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=53C43F9B.6090907@redhat.com \
--to=pbonzini@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.