external_qemu.git - external/qemu

	Commit message (Collapse)	Author	Age	Files	Lines
*	Simplify core framebuffer management.	David 'Digit' Turner	2011-02-02	1	-95/+29
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	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
*	Refactor the framebuffer service	Vladimir Chtchetkine	2011-01-31	1	-5/+5
\| \| \| \|	Change-Id: I8ac4580af65b8d58976c97b77b309dd202e75003
*	Force core to send entire framebuffer on UI attachment	Vladimir Chtchetkine	2011-01-20	1	-1/+1
\| \| \| \|	Change-Id: I2feb813314163b94781ffe765eb23527b6c4a0f1
*	Add support for 32-bit framebuffers.	David 'Digit' Turner	2011-01-18	1	-1/+11
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	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
*	Pass bits per pixel tu UI when it gets attached to core framebuffer	Vladimir Chtchetkine	2010-12-21	1	-0/+5
\| \| \| \| \| \| \|	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
*	Resubmit framebuffer service implementation	Vladimir Chtchetkine	2010-12-20	1	-10/+38
\| \| \| \|	Change-Id: I184e27a1e8d88835bc9f0502eccfa3f64a7aaf9e
*	Implement core display deriving it from android display	Vladimir Chtchetkine	2010-12-14	1	-0/+91
	Core display is a framebuffer client that receives framebuffer updates and dispatches them to the UI attached to the core. Change-Id: Iff1e0609cbe66240031e3670934a6796a9ae3b15