Searched hist:"21 ef45d71221b4577330fe3aacfb06afad91ad46" (Results 1 – 4 of 4) sorted by relevance
| /openbmc/qemu/ui/ |
| H A D | vnc.h | diff 21ef45d71221b4577330fe3aacfb06afad91ad46 Thu Feb 28 04:34:31 CST 2013 Gerd Hoffmann <kraxel@redhat.com> console: kill DisplayState->opaque
It's broken by design. There can be multiple DisplayChangeListener
instances, so they simply can't store state in the (single) DisplayState
struct. Try 'qemu -display gtk -vnc :0', watch it crash & burn.
With DisplayChangeListenerOps having a more sane interface now we can
simply use the DisplayChangeListener pointer to get access to our
private data instead.
Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
|
| H A D | gtk.c | diff 21ef45d71221b4577330fe3aacfb06afad91ad46 Thu Feb 28 04:34:31 CST 2013 Gerd Hoffmann <kraxel@redhat.com> console: kill DisplayState->opaque
It's broken by design. There can be multiple DisplayChangeListener
instances, so they simply can't store state in the (single) DisplayState
struct. Try 'qemu -display gtk -vnc :0', watch it crash & burn.
With DisplayChangeListenerOps having a more sane interface now we can
simply use the DisplayChangeListener pointer to get access to our
private data instead.
Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
|
| H A D | vnc.c | diff 21ef45d71221b4577330fe3aacfb06afad91ad46 Thu Feb 28 04:34:31 CST 2013 Gerd Hoffmann <kraxel@redhat.com> console: kill DisplayState->opaque
It's broken by design. There can be multiple DisplayChangeListener
instances, so they simply can't store state in the (single) DisplayState
struct. Try 'qemu -display gtk -vnc :0', watch it crash & burn.
With DisplayChangeListenerOps having a more sane interface now we can
simply use the DisplayChangeListener pointer to get access to our
private data instead.
Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
|
| /openbmc/qemu/include/ui/ |
| H A D | console.h | diff 21ef45d71221b4577330fe3aacfb06afad91ad46 Thu Feb 28 04:34:31 CST 2013 Gerd Hoffmann <kraxel@redhat.com> console: kill DisplayState->opaque
It's broken by design. There can be multiple DisplayChangeListener
instances, so they simply can't store state in the (single) DisplayState
struct. Try 'qemu -display gtk -vnc :0', watch it crash & burn.
With DisplayChangeListenerOps having a more sane interface now we can
simply use the DisplayChangeListener pointer to get access to our
private data instead.
Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
|