Il 18/02/2014 14:44, Alex David ha scritto:
Ok, thank you very much for your help then. I'm gonna spend some time on
this.
If qemu-dev / you are interested in what I've done later, I'll send a
new mail.
Yes, if you get the USB-I2C bridge to work, we'd be interested in
including it in QEMU!
Ok, thank you very much for your help then. I'm gonna spend some time on
this.
If qemu-dev / you are interested in what I've done later, I'll send a new
mail.
2014-02-18 14:05 GMT+01:00 Paolo Bonzini :
> Il 18/02/2014 13:48, Alex David ha scritto:
>
>>
>> 2014-02-17 17:11 GMT+01:00 Paolo Bonzi
Il 18/02/2014 13:48, Alex David ha scritto:
2014-02-17 17:11 GMT+01:00 Paolo Bonzini mailto:pbonz...@redhat.com>>:
Il 17/02/2014 16:33, Alex David ha scritto:
If you need more than one bus, you need a new device
exposing the
I2C bus, besides the new sensor d
2014-02-17 17:11 GMT+01:00 Paolo Bonzini :
> Il 17/02/2014 16:33, Alex David ha scritto:
>
> If you need more than one bus, you need a new device exposing the
>> I2C bus, besides the new sensor devices. USB-I2C could be one such
>> device.
>>
>> So let me see if I understood well. US
Il 17/02/2014 16:33, Alex David ha scritto:
If you need more than one bus, you need a new device exposing the
I2C bus, besides the new sensor devices. USB-I2C could be one such
device.
So let me see if I understood well. USB-I2C (host QEMU device) seems a
good idea, I could normally
2014-02-17 15:30 GMT+01:00 Paolo Bonzini :
> So you cannot configure the three devices on the same bus, with three
> different addresses?
Each sensor is different on the original hardware, they are connected on
different busses. As my guest apps are calling i2c-1, i2c-2, ,i2c-N
(and I can't
Il 17/02/2014 14:32, Alex David ha scritto:
But that leaves me with another problem as I now understand how I2C
works on linux... I, in fact, need at least 3 busses (for my at least 3
devices) - so i2c-0, i2c-1, i2c-2
So you cannot configure the three devices on the same bus, with three
diffe
2014-02-17 14:19 GMT+01:00 Paolo Bonzini :
> Il 17/02/2014 14:11, Alex David ha scritto:
>
> I've tried using tmp105. As my linux isn't 64bits, i'm using
>> qemu-system-i386... It crashes my computer when I use it with my linux
>> image (it's a debian .qcow2..., easy to do some tests...).
>>
>
>
Il 17/02/2014 14:11, Alex David ha scritto:
I've tried using tmp105. As my linux isn't 64bits, i'm using
qemu-system-i386... It crashes my computer when I use it with my linux
image (it's a debian .qcow2..., easy to do some tests...).
You mean crashes your host?
I will most probably need a ch
>
>
>
>>
>> I'm emulating a bunch of sensors/actuators.
>>>
>>> If I virtualize my sensors and attach them to the i2c-dev with -device,
>>> how do I get those data on the host then ?
>>>
>>
>> It depends on your use case.
>>
>> It could be that you can make them return a constant value.
>>
>> Othe
2014-02-17 11:38 GMT+01:00 Paolo Bonzini :
> Il 17/02/2014 11:01, Alex David ha scritto:
>
> I indeed don't use paravirtualization.
>>
>
> Virtio _is_ paravirtualization. :)
>
>
Ok, now that seems much more understandable... I missed that point ha.
>
> I'm emulating a bunch of sensors/actuato
Il 17/02/2014 11:01, Alex David ha scritto:
I indeed don't use paravirtualization.
Virtio _is_ paravirtualization. :)
I'm emulating a bunch of sensors/actuators.
If I virtualize my sensors and attach them to the i2c-dev with -device,
how do I get those data on the host then ?
It depends on
Il 17/02/2014 10:38, Alex David ha scritto:
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.
i2c-N is on the guest, that's why I want to virtualize
2014-02-17 10:19 GMT+01:00 Paolo Bonzini :
> 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 h
14 matches
Mail list logo
