[roll] Roll fuchsia [flatland] Allow YUV buffer constraints in Intel display path

We currently do not have YUV images supported in intel displays.
Additionally, we dont have a way of handling sysmem negotiation
without failure, i.e. prunable tokens.

This CL adds a short term workaround by allowing YUV constraints in
intel code and marking all YUV images as not supported in Display
Compositor. This enables us to turn on direct-to-display without
breaking YUV buffers.

Original-Fixed: 93944
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/652843
Original-Revision: 654675f125288e45d553cff1c986a87730ea144d
GitOrigin-RevId: ecdaa0eb5a21dd175bb0f42ca213e06f7a4a1c33
Change-Id: I848e3ccf7b4f39ff3a785589079e191152da60f4
1 file changed
tree: df1d9a8b34c1e685593523ca78040a62763b5d6f
  1. infra/
  2. third_party/
  3. cts
  4. firmware
  5. flower
  6. jiri.lock
  7. minimal
  8. prebuilts
  9. README.md
  10. stem
  11. test_durations
  12. 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 via the IRC channel #fuchsia on Freenode.

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.