From: Paolo Bonzini <pbonzini@redhat.com>
To: Richard Peters <mail@richardpeters.de>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Interconnect two qemu (Stellaris LM3S6965EVB) instances via I2C
Date: Fri, 17 Feb 2017 13:42:15 +0100 [thread overview]
Message-ID: <2f68cce3-8417-79bf-e352-e25a10163e6a@redhat.com> (raw)
In-Reply-To: <b87f8e22-1346-b1fb-90a9-572c56c36c55@richardpeters.de>
On 17/02/2017 13:27, Richard Peters wrote:
> Hi Community,
>
> The Qemu target 'LM3S6965EVB' supports I2C.
> I have two firmware versions for a LM3S6965EVB chip that i want to test
> with qemu. One is the master and the other is slave.
> They use I2C drivers for the LM3S6965EVB chip.
There is no solution for this and, in addition, QEMU's I2C controller
emulation only supports master mode.
I have long been thinking of adding support for I2C-to-chardev bridge,
where a QEMU device would connect to a character device backend
(typically a socket) and the data on the character device would
represent commands to/from an I2C slave. Likewise, adding a character
device backend to an I2C controller, speaking the same protocol, would
make it possible to implement slave mode. However, none of this is
available in QEMU.
The first step would be to implement some kind of asynchronous API in
I2CSlave, to be able to do clock stretching ("no data available on the
socket" would then stretch the clock).
Paolo
> How can i connect these two instances?
> I didn't found a simple solution for that in the docs or in google.
> Is there a simple solution without virtio driver coding, etc?
>
> Hope you can help me with that :-)
>
> Thank you and regards,
> Richard
>
>
prev parent reply other threads:[~2017-02-17 12:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-17 12:27 [Qemu-devel] Interconnect two qemu (Stellaris LM3S6965EVB) instances via I2C Richard Peters
2017-02-17 12:42 ` 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=2f68cce3-8417-79bf-e352-e25a10163e6a@redhat.com \
--to=pbonzini@redhat.com \
--cc=mail@richardpeters.de \
--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).