commit 851cfe834295224cd64bdd499872b95b19c4de8c
author Jesse Hall <jessehall@google.com> Wed Mar 20 13:44:00 2013 -0700
committer Jesse Hall <jessehall@google.com> Fri Mar 22 15:27:57 2013 -0700
tree be3c3711c47337d41401385e56f6d3aafb427d27
parent afaf14b9fbfe8943d845e2f01e8a401ad7a4d854

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