Jesse Hall b716e57048 Set the outbuf acquire fence after we actually have it. ... In GLES-only mode, we don't have the outbuf acquire fence until after GLES composition is done for the frame. We were setting the fence in HWC's state immediately after dequeueing the buffer from the consumer, before GLES had started. This fence got passed through HWC and on to the consumer, so the consumer was reading the buffer before GLES was done writing to it. Now we update HWC's state just before set(), when we know we have the right fence. Bug: 11000763 Change-Id: Iea9db4c69634c352dc2d600f0bdb6bef2a432636		2013-10-01 17:25:20 -07:00
..
DisplaySurface.h	Provide HWC prepare with a valid output buffer	2013-08-20 16:35:32 -07:00
FloatRect.h	fix SF buffer cropping	2013-07-10 15:08:29 -07:00
FramebufferSurface.cpp	Provide HWC prepare with a valid output buffer	2013-08-20 16:35:32 -07:00
FramebufferSurface.h	Provide HWC prepare with a valid output buffer	2013-08-20 16:35:32 -07:00
HWComposer.cpp	fix initialization of framebuffer target crop rect on hwc 1.3	2013-09-25 20:44:34 -07:00
HWComposer.h	handle several vsync signal correctly	2013-08-21 17:45:46 -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	Set the outbuf acquire fence after we actually have it.	2013-10-01 17:25:20 -07:00
VirtualDisplaySurface.h	Make sure do disconnect from a BQ when its client dies.	2013-09-16 16:15:21 -07:00