On 28.08.14 14:23, Alexander Graf wrote:
On 28.08.14 13:59, Alexander Graf wrote:
On 15.08.14 07:29, Peter Crosthwaite wrote:
Hi All,
So phase one was the QOMification of qemu_irq. This is the next step.
We start to setup GPIOs as proper QOM objects. Inputs are child objects
of
On 15.08.14 07:29, Peter Crosthwaite wrote:
Hi All,
So phase one was the QOMification of qemu_irq. This is the next step.
We start to setup GPIOs as proper QOM objects. Inputs are child objects
of their device. Outputs are settable Links and connection is made
via proper setting of a QOM
On 28.08.14 13:59, Alexander Graf wrote:
On 15.08.14 07:29, Peter Crosthwaite wrote:
Hi All,
So phase one was the QOMification of qemu_irq. This is the next step.
We start to setup GPIOs as proper QOM objects. Inputs are child objects
of their device. Outputs are settable Links and
Ping!
Andreas, are you able to take this?
Regards,
Peter
On Thu, Aug 21, 2014 at 7:23 PM, Alexander Graf ag...@suse.de wrote:
On 15.08.14 07:29, Peter Crosthwaite wrote:
Hi All,
So phase one was the QOMification of qemu_irq. This is the next step.
We start to setup GPIOs as proper QOM
On 15.08.14 07:29, Peter Crosthwaite wrote:
Hi All,
So phase one was the QOMification of qemu_irq. This is the next step.
We start to setup GPIOs as proper QOM objects. Inputs are child objects
of their device. Outputs are settable Links and connection is made
via proper setting of a QOM
Hi All,
So phase one was the QOMification of qemu_irq. This is the next step.
We start to setup GPIOs as proper QOM objects. Inputs are child objects
of their device. Outputs are settable Links and connection is made
via proper setting of a QOM link.
We then cleanup Sysbus to simply re-use
