Hi,
So, the big qemu console data structure overhauls is done, patches just
posted to the list.
I think the next logical step ahead is to QOM-ify the QemuConsoles, so
we can link the QemuConsole to the thing actually backing it. For a
graphical console that would be the emlated graphic
Hi Gerd,
Am 20.03.2013 10:55, schrieb Gerd Hoffmann:
I think the next logical step ahead is to QOM-ify the QemuConsoles, so
we can link the QemuConsole to the thing actually backing it. For a
graphical console that would be the emlated graphic device. For a text
console it would be the
Andreas Färber afaer...@suse.de writes:
Hi Gerd,
Am 20.03.2013 10:55, schrieb Gerd Hoffmann:
I think the next logical step ahead is to QOM-ify the QemuConsoles, so
we can link the QemuConsole to the thing actually backing it. For a
graphical console that would be the emlated graphic
Hi,
I think the first step is to figure out what the relationships are. I
was looking through the changes and vaguely, it appears that its:
- Each UI has one or more DisplayChangeListeners
Yes.
- Each DisplayChangeListener can be mapped to 1 or more QemuConsoles
Each
On 03/20/2013 09:39 AM, Andreas Färber wrote:
Hi Gerd,
Am 20.03.2013 10:55, schrieb Gerd Hoffmann:
I think the next logical step ahead is to QOM-ify the QemuConsoles, so
we can link the QemuConsole to the thing actually backing it. For a
graphical console that would be the emlated graphic
