From: Paolo Bonzini <pbonzini@redhat.com>
To: BALATON Zoltan <balaton@eik.bme.hu>,
Stefan Hajnoczi <stefanha@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
Jim Mussared <jim@groklearning.com>,
Joel Stanley <joel@jms.id.au>,
Jonathan Austin <jonny@microbit.org>
Subject: Re: [Qemu-devel] Internship idea: I2C passthrough
Date: Wed, 9 Jan 2019 22:16:01 +0100 [thread overview]
Message-ID: <3f4f974a-2bd9-bf08-eef1-d89d2cf6cfa5@redhat.com> (raw)
In-Reply-To: <alpine.BSF.2.21.9999.1901091919140.41593@zero.eik.bme.hu>
On 09/01/19 19:23, BALATON Zoltan wrote:
>> '''Summary:''' Implement I2C bus passthrough on Linux hosts so that
>> emulated Raspberry Pi or micro:bit boards can talk to real I2C
>> devices.
>
> How about implementing USB for raspi boards instead? Or is there a
> project proposal (or even some code somewhere out of tree) for that
> already? Seems more useful to allow having emulated keyboard and mouse
> to use Raspbian for example or pass through USB devices. (I don't know
> anything about this was just reminded to a recent discussion by this
> message. If it's not relevant just disregard my comment and sorry for
> the noise.)
That's also a valid idea. However, Stefan has misinterpreted the
reference to the raspi that I quickly made on IRC. The idea of I2C
passthrough is that a single board computer like a Raspberry Pi can be
used to develop application for a microcontroller such as micro:bit,
without having to flash the firmware again and again, etc.
Real I2C devices---for example a GPIO extender, a temperature sensor or
a real-time clock---would be attached to the I2C bus on the single board
computer's GPIO headers, exposed as an I2C device through /dev/i2c, and
then driven by the emulated micro:bit through its own I2C controller (or
bitbanged).
(I've now updated the project idea).
Paolo
prev parent reply other threads:[~2019-01-09 21:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-09 17:09 [Qemu-devel] Internship idea: I2C passthrough Stefan Hajnoczi
2019-01-09 18:23 ` BALATON Zoltan
2019-01-09 21:16 ` 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=3f4f974a-2bd9-bf08-eef1-d89d2cf6cfa5@redhat.com \
--to=pbonzini@redhat.com \
--cc=balaton@eik.bme.hu \
--cc=jim@groklearning.com \
--cc=joel@jms.id.au \
--cc=jonny@microbit.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
/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).