| 7a5ee57895822a769f48ab40e590711a2459e2d1 |
|
02-Feb-2011 |
David 'Digit' Turner <digit@android.com> |
Simplify core framebuffer management.
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
/external/qemu/android/display-core.c
|
| 94a2fba98924c6684650d66409934358cb0c9d09 |
|
31-Jan-2011 |
Vladimir Chtchetkine <vchtchetkine@google.com> |
Refactor the framebuffer service
Change-Id: I8ac4580af65b8d58976c97b77b309dd202e75003
/external/qemu/android/display-core.c
|
| ac389ae4513263597dc02e4099867d5123faaa04 |
|
20-Jan-2011 |
Vladimir Chtchetkine <vchtchetkine@google.com> |
Force core to send entire framebuffer on UI attachment
Change-Id: I2feb813314163b94781ffe765eb23527b6c4a0f1
/external/qemu/android/display-core.c
|
| 97d795c955f8d261a0a5294d49ea06d5a473ed03 |
|
16-Jan-2011 |
David 'Digit' Turner <digit@android.com> |
Add support for 32-bit framebuffers.
This modifies the emulator so support 32-bit framebuffers.
You can create such a frame-buffer using one of these methods:
- Add a "bpp 32" line to the "display" element of your skin
- Use the new 'magic' skin option format: e.g. -skin 320x480x32
Note that the result will be hideous since the kernel driver still
thinks the hardware is only 16-bits. This will be addressed in a
later patch to hw/goldfish_fb.c and to the kernel driver
($KERNEL/drivers/video/goldfishfb.c)
Change-Id: I0fc700c4a4cb8521076605324e15ed34e5d01136
/external/qemu/android/display-core.c
|
| 8acf4e2237c2969647f47008344e44918bb30acb |
|
21-Dec-2010 |
Vladimir Chtchetkine <vchtchetkine@google.com> |
Pass bits per pixel tu UI when it gets attached to core framebuffer
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
/external/qemu/android/display-core.c
|
| e95660aadc669784406d5f5a867988b8ecc2ed0d |
|
20-Dec-2010 |
Vladimir Chtchetkine <vchtchetkine@google.com> |
Resubmit framebuffer service implementation
Change-Id: I184e27a1e8d88835bc9f0502eccfa3f64a7aaf9e
/external/qemu/android/display-core.c
|
| 72d83df9865cf8f5393a41fc3f6e283ab6aaa81b |
|
14-Dec-2010 |
Vladimir Chtchetkine <vchtchetkine@google.com> |
Implement core display deriving it from android display
Core display is a framebuffer client that receives framebuffer updates and dispatches
them to the UI attached to the core.
Change-Id: Iff1e0609cbe66240031e3670934a6796a9ae3b15
/external/qemu/android/display-core.c
|