Jesse Hall ef19414bd8 Transfer HWC release fences to BufferQueue ... After a HWC set, each SurfaceFlinger Layer retrieves the release fence HWC returned and gives it to the layer's SurfaceTexture. The SurfaceTexture accumulates the fences into a merged fence until the next updateTexImage, then passes the merged fence to the BufferQueue in releaseBuffer. In a follow-on change, BufferQueue will return the fence along with the buffer slot in dequeueBuffer. For now, dequeueBuffer waits for the fence to signal before returning. The releaseFence default value for BufferQueue::releaseBuffer() is temporary to avoid transient build breaks with a multi-project checkin. It'll disappear in the next change. Change-Id: Iaa9a0d5775235585d9cbf453d3a64623d08013d9		2012-06-21 22:21:12 -07:00
build	I am having second thoughts about 512m for the large heap size.	2012-06-08 13:02:09 -07:00
cmds	am 4f0dfaa7: am 9be7caf3: Merge "Include stack traces for certain native processes in bugreport." into jb-dev	2012-06-08 15:33:30 -07:00
data/etc	Move com.nxp.mifare to frameworks/native.	2012-04-12 21:24:08 -07:00
include	Transfer HWC release fences to BufferQueue	2012-06-21 22:21:12 -07:00
libs	Transfer HWC release fences to BufferQueue	2012-06-21 22:21:12 -07:00
opengl	Update ANativeWindow clients for sync	2012-06-20 15:48:30 -07:00
services	Transfer HWC release fences to BufferQueue	2012-06-21 22:21:12 -07:00
MODULE_LICENSE_APACHE2
NOTICE