Mathias Agopian ca08833d5e don't use compile-time configuration of libgui as much as possible ... We now detect at runtime which sync features to use, which allows us to remove a lot of the compile-time configuration options. There is still one option though, to disable KHR_fence_sync on some devices (which are more efficient without it). - added a backdoor to get the vendor's EGL strings the new logic is: - use always ANDROID_native_fence_sync if available - fallback to KHR_fence_sync if available and not disabled by the compile-time option - use KHR_wait_sync if available and either of the above is enabled Change-Id: I9c4b49d9ff1151faf902cc93bd53ea5f205aaabf		2013-03-29 15:33:47 -07:00
..
DisplayHardware
tests
Android.mk
Barrier.h
Client.cpp
Client.h
clz.h
DdmConnection.cpp
DdmConnection.h
DisplayDevice.cpp
DisplayDevice.h
EventThread.cpp
EventThread.h
FrameTracker.cpp
FrameTracker.h
GLExtensions.cpp
GLExtensions.h
Layer.cpp
Layer.h
LayerDim.cpp
LayerDim.h
MessageQueue.cpp
MessageQueue.h
MODULE_LICENSE_APACHE2
SurfaceFlinger.cpp
SurfaceFlinger.h
SurfaceFlingerConsumer.cpp
SurfaceFlingerConsumer.h
SurfaceTextureLayer.cpp
SurfaceTextureLayer.h
Transform.cpp
Transform.h