[roll] Roll fuchsia [carnelian] Use vsync stamps instead of release fences

In direct-display mode (not Scenic/Flatland) stop providing a release
fence to `fuchsia.hardware.display.Coordinator.SetLayerImage()`.
Instead, associate images with the `ConfigStamp` when they were applied,
and free them when a vsync with a *later* stamp is observed.

Tested: ran spinning-square-rs in framebuffer mode, no Scenic/session.
Original-Fixed: 371020991
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1121996
Original-Revision: 238d770091bf47e0ec3984e78e5208a607fb5cd4
GitOrigin-RevId: c430fb7d783a288525c0cb1e75295f6a2b5a29c7
Change-Id: Ia0266d7662f2883aa33180f4605d6aef45cc8fdb
1 file changed
tree: f2d43c11d016292a42c23ebc057735b93b180150
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. cts
  6. firmware
  7. flower
  8. jiri.lock
  9. MILESTONE
  10. minimal
  11. prebuilts
  12. README.md
  13. stem
  14. test_durations
  15. toolchain
README.md

Integration

This repository contains Fuchsia's Global Integration manifest files.

Making changes

All changes should be made to the internal version of this repository. Our infrastructure automatically updates this version when the internal one changes.

Currently all changes must be made by a Google employee. Non-Google employees wishing to make a change can ask for assistance in one of the communication channels documented at get involved.

Obtaining the source

First install Jiri.

Next run:

$ jiri init
$ jiri import minimal https://fuchsia.googlesource.com/integration
$ jiri update

Third party

Third party projects should have their own subdirectory in ./third_party.