[roll] Roll fuchsia [display][fidl][banjo] Add type for driver-side ConfigStamp. This CL creates a compiler-enforced separation between client-side and driver-side config stamps. Each Display Coordinator client manages its ConfigStamp value space, and uses the values in calls to fuchsia.hardware.display/Coordinator.ApplyConfig3(). The Display Coordinator creates a single "timeline" of monotonically increasing DriverConfigStamp values, which are communicated to engine drivers. This CL carries out the following steps. 1. Add the FIDL type fuchsia.hardware.display.engine/ConfigStamp. 2. Add the api-types/cpp type display::DriverConfigStamp. 3. Migrate all in-tree display drivers. 4. Create api-protocols/cpp stubs to facilitate other display driver migration. A future CL will move fuchsia.hardware.display.types/ConfigStamp to fuchsia.hardware.display/ConfigStamp. This change is not done here to keep this CL to a manageable size. Original-Bug: 394148660 Test: fx test //src/graphics/display Test: Booted workbench_eng.x64 on qemu Test: ffx target ssh display-tool squares Multiply: display-api-types-cpp: 1 Multiply: display-api-types-cpp17: 1 Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1198844 Original-Revision: 2d650a948ae3d5781fef7f8774bc2eccaca88d8b GitOrigin-RevId: 0c8d89849cbb77616975c537cbc8a27b9791e611 Change-Id: Icd337d50b62436f6b78522e56270dd11921dbfd6
This repository contains Fuchsia's Global Integration manifest files.
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.
First install Jiri.
Next run:
$ jiri init $ jiri import minimal https://fuchsia.googlesource.com/integration $ jiri update
Third party projects should have their own subdirectory in ./third_party.