From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:34162) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WFKMR-00072e-7T for qemu-devel@nongnu.org; Mon, 17 Feb 2014 04:19:41 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WFKMK-0006cx-Dn for qemu-devel@nongnu.org; Mon, 17 Feb 2014 04:19:35 -0500 Received: from mx1.redhat.com ([209.132.183.28]:33560) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WFKMK-0006ae-5U for qemu-devel@nongnu.org; Mon, 17 Feb 2014 04:19:28 -0500 Message-ID: <5301D40F.2010506@redhat.com> Date: Mon, 17 Feb 2014 10:19:11 +0100 From: Paolo Bonzini MIME-Version: 1.0 References: <52FE3D0E.8070904@redhat.com> <52FE44DB.8030408@suse.de> <52FE4820.8050009@redhat.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] Trying to write a new device / virtio-i2c ? List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Alex David Cc: =?ISO-8859-1?Q?Andreas_F=E4rber?= , qemu-devel@nongnu.org Il 17/02/2014 09:35, Alex David ha scritto: > - Are there solutions that seems more adapted to my case ? Like using > USB-I2C bridge ? From an upstream point of view, a host passthrough device pair (one object talking to /dev/i2c-N on the host, and one device per sensor talking to the other object) would be the best. But if you can make I2C-over-parallel work, that would also be interesting. And not much new code to write: all you need to parse the bitbanging I2C protocol is already in hw/i2c/bitbang_i2c.c. Paolo