From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:55634) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZyheV-00076l-CS for qemu-devel@nongnu.org; Tue, 17 Nov 2015 09:54:36 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZyheR-0001JO-Bv for qemu-devel@nongnu.org; Tue, 17 Nov 2015 09:54:35 -0500 Received: from lvps176-28-13-145.dedicated.hosteurope.de ([176.28.13.145]:49284) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZyheR-0001JE-58 for qemu-devel@nongnu.org; Tue, 17 Nov 2015 09:54:31 -0500 From: Tim Sander Date: Tue, 17 Nov 2015 15:54 +0100 Message-ID: <2474896.NqoA36AmNt@dabox> In-Reply-To: <564B35CD.9080905@redhat.com> References: <1691671.NeDo6VeWzF@dabox> <564B35CD.9080905@redhat.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [Qemu-devel] i2c-tiny-usb noob question List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paolo Bonzini Cc: qemu-devel@nongnu.org Hi Paolo Am Dienstag, 17. November 2015, 15:12:29 schrieb Paolo Bonzini: > On 17/11/2015 14:45, Tim Sander wrote: > > I just gave it a try and now i have a device which is detected by linux > > and > > allows simple reads (without i2c backend though). But unfortunatly i am > > currently stuck as i don't know how the address is transmitted to the > > device? > Do you mean how it is transmitted to the i2c-tiny-usb device by the > driver? The only way to find out is to read a datasheet or the driver > code. Or do you mean something else? Just after hitting send of my previous mail i found out that i overlooked "index", which is the argument used in this case to transmit the address. So the next step would be to use this value and do accesses to any i2c devices associated: any pointers where s.th. like this has been done? Best regards Tim