Jesse Hall 851cfe8342 Isolate knowledge that fb target == output buffer ... HWComposer didn't allow the virtual display output buffer to be set directly, instead it always used the framebuffer target buffer. DisplayDevice was only providing the framebuffer release fence to DisplaySurfaces after a commit. This change fixes both of these, so both HWComposer and DisplayDevice should continue to work if VirtualDisplaySurface changes to use separate framebuffer and output buffers. It's also more correct since VirtualDisplaySurface uses the correct release fence when queueing the buffer to the sink. Bug: 8384764 Change-Id: I95c71e8d4f67705e23f122259ec8dd5dbce70dcf		2013-03-22 15:27:57 -07:00
..
BufferQueueInterposer.cpp	Release virtual display buffer immediately after HWC set	2013-03-20 11:16:55 -07:00
BufferQueueInterposer.h	Release virtual display buffer immediately after HWC set	2013-03-20 11:16:55 -07:00
DisplaySurface.h	Isolate knowledge that fb target == output buffer	2013-03-22 15:27:57 -07:00
FramebufferSurface.cpp	Isolate knowledge that fb target == output buffer	2013-03-22 15:27:57 -07:00
FramebufferSurface.h	Isolate knowledge that fb target == output buffer	2013-03-22 15:27:57 -07:00
HWComposer.cpp	Isolate knowledge that fb target == output buffer	2013-03-22 15:27:57 -07:00
HWComposer.h	Isolate knowledge that fb target == output buffer	2013-03-22 15:27:57 -07:00
PowerHAL.cpp	don't actuate vsync hint when not needed	2012-04-27 13:55:05 -07:00
PowerHAL.h	don't actuate vsync hint when not needed	2012-04-27 13:55:05 -07:00
VirtualDisplaySurface.cpp	Isolate knowledge that fb target == output buffer	2013-03-22 15:27:57 -07:00
VirtualDisplaySurface.h	Isolate knowledge that fb target == output buffer	2013-03-22 15:27:57 -07:00