Ping again!
Are there any docs for QOM ?? or the historical parent of QOM , so that it is
easy to relate.
Thanks,Sai Pavan
On Tuesday, February 10, 2015 11:50 PM, boddu pavan
wrote:
Ok fine.
I always think there should be basic doc for QOM model for the QEMU beginners
as this
Hi,
I have some question on using QOM, new to QEMU and will be great if i can put
some answers for below question.
1) If QEMU is considered to be OOP, How is the relation between a Class and
Object. I see in c++ we do not create a classobject there will be a object of a
class. But here i see bot
Hi,
I have some question on using QOM, new to QEMU and will be great if i can put
some answers for below question.
1) If QEMU is considered to be OOP, How is the relation between a Class and
Object. I see in c++ we do not create a classobject there will be a object of a
class. But here i see bot
Hi,
I have some question on using QOM, new to QEMU and will be great if i can put
some answers for below question.
1) If QEMU is considered to be OOP, How is the relation between a Class and
Object. I see in c++ we do not create a classobject there will be a object of a
class. But here i see bot
I am trying to emulate a status reg in qemu, but the value is dependent of the
value of the register in another module. How can I communicate between the two
modules to update the status register.Thanks
Yes its hardware block, and yes they are of same SOC. status is 16bit.
On Tuesday, February 10, 2015 7:00 PM, Paolo Bonzini
wrote:
[no private messages please]
On 10/02/2015 14:27, boddu pavan wrote:
> Hi paolo,
> I have a aes module and its status should also be upda
state is different for each one. and an object.
Does all the hw_peripherals has any root node kind of thing. Which makes all
our nodes connected ?
On Tuesday, February 10, 2015 7:15 PM, Paolo Bonzini
wrote:
On 10/02/2015 14:34, boddu pavan wrote:
> Yes its hardware block, and yes they
/2015 15:02, boddu pavan wrote:
>
> Does all the hw_peripherals has any root node kind of thing. Which makes
> all our nodes connected ?
>
The common superclass of the devices is DeviceState.
The root object that connects the devices is the QEMUMachine.
Paolo
Hi,
I am new to qemu, And i need help in understanding a part of code, Can any one
tell the use of Canonical paths of the Object.
Thanks,Sai Pavan
Thanks Poalo, This was helpful.
Regards,Sai Pavan
On Wednesday, December 10, 2014 6:27 PM, Paolo Bonzini
wrote:
On 09/12/2014 12:28, boddu pavan wrote:
> Hi,
>
> I am new to qemu, And i need help in understanding a part of code, Can
> any one tell the use of Canoni
+qemu-dev
Show original message On Monday, May 22, 2017 6:34 PM, boddu pavan
wrote:
Hi,
I see that ssi_auto_connect_slave helper of ssi.c
(https://github.com/qemu/qemu/blob/master/hw/ssi/ssi.c#L166) is used to connect
SSISlave children of spi controller to its respective spi bus
11 matches
Mail list logo
