| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Remove one layer of indirection between the core's DisplayState
and a ProxyFramebuffer object. The main ideas behind this patch
are that:
- We don't need a QFrameBuffer object when in the core process,
each proxy can receive display updates directly from QEMU.
- The DisplayChangeListener is really lame: its can't dissociate
between several listeners that use the same callback pointers,
so introduce DisplayUpdateListener in console.h to work around
this. This is preferably to modifying DisplayChangeListener
which is going to introduce conflicts with upstream.
- Simplify a lot the console code and display-core. Note that
we can have several framebuffer clients at the same time now.
Note that QFrameBuffer is still used by both the UI program and
the standalone emulator.
Change-Id: I6d5ad6ecd9b34b9d9d1a30ea5000e875c285e84e
|
|
|
|
|
|
|
| |
The QFrameBuffer is no used by QEMU-specific code anymore so it's
more logical to move it here.
Change-Id: Id49ff53dd49648000e7543652d66f7c03881a8cb
|
|
|
|
| |
Change-Id: I8ac4580af65b8d58976c97b77b309dd202e75003
|
|
|
|
|
|
|
| |
Instead of passing bits per pixel property in each and every framebuffer notification
message, do it once when UI attaches to the core's framebuffer service.
Change-Id: Ic1f6d9796b64d40518f09f5a5341f8359ff817b7
|
|
|
|
| |
Change-Id: I184e27a1e8d88835bc9f0502eccfa3f64a7aaf9e
|
|
Core display is a framebuffer client that receives framebuffer updates and dispatches
them to the UI attached to the core.
Change-Id: Iff1e0609cbe66240031e3670934a6796a9ae3b15
|