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 poin
Ok fine.
I always think there should be basic doc for QOM model for the QEMU beginners
as this point. Or if we already have some in-mails explanations or any blogs
can any one point out here.
Thanks.Sai Pavan
On Tuesday, February 10, 2015 7:57 PM, Paolo Bonzini
wrote:
On 10/02/2015
On 10/02/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
yup, thanks Paolo.
But i have another basic question. I hope we have some docs on this. QOM
model.I always really confuse with this series
obj->DeviceState->SysBusDevice->hw_perip state.
I simple assume that all the hw_emulations will be connected to SysBus(mostly).
The device state is different
On 10/02/2015 14:34, boddu pavan wrote:
> Yes its hardware block, and yes they are of same SOC. status is 16bit.
For simplicity you can make them the same DeviceState.
In order of increasing accuracy:
- save the AES module's address in a global variable, and add a qemu_irq
raised by the AES mo
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 updated in register
[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 updated in register of
> another block, which is said to be public register. The one in which its
> updating is a private register.
> How to get the data passed and
