From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:43459)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <pbonzini@redhat.com>) id 1Zygzt-00077M-HR
	for qemu-devel@nongnu.org; Tue, 17 Nov 2015 09:12:38 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <pbonzini@redhat.com>) id 1Zygzp-0005jW-EY
	for qemu-devel@nongnu.org; Tue, 17 Nov 2015 09:12:37 -0500
Received: from mx1.redhat.com ([209.132.183.28]:46370)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <pbonzini@redhat.com>) id 1Zygzp-0005jJ-9a
	for qemu-devel@nongnu.org; Tue, 17 Nov 2015 09:12:33 -0500
References: <1691671.NeDo6VeWzF@dabox>
From: Paolo Bonzini <pbonzini@redhat.com>
Message-ID: <564B35CD.9080905@redhat.com>
Date: Tue, 17 Nov 2015 15:12:29 +0100
MIME-Version: 1.0
In-Reply-To: <1691671.NeDo6VeWzF@dabox>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] i2c-tiny-usb noob question
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Tim Sander <tim@krieglstein.org>, qemu-devel@nongnu.org



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?

Paolo