On 17/11/2015 17:25, Tim Sander wrote:
> I can instantiate my i2c-tiny-usb with the following command line option:
> -device usb-i2c-tiny,id=i2c-0
>
> Now i would like to add child devices to this device instance. Unfortunatly i
> could not find out how to add e.g. the tmp105 sensor to this i2c
Hi
I am no so far that i can successfully read and write from linux usermode to
my virtual i2c-tiny-usb device. Unfortunatly i was not able to plug any i2c-
device into this device to go on with implementing the backend bus accesses.
I can instantiate my i2c-tiny-usb with the following command l
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
Hi Paolo
Thanks for your reply.
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
Hi
I had been missing a i2c-bus configurable from the command line.
By searching i have seen the discussion:
https://lists.gnu.org/archive/html/qemu-devel/2014-02/msg03146.html
I just gave it a try and now i have a device which is detected by linux and
allows simple reads (without i2c backend t
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 t
