[roll] Roll fuchsia [intel-i915] Migrate the driver and driver test to DFv2.

This change migrates the intel-i915 driver and the driver test
intel-display-driver-test.cc to DFv2.

This migration also changes the device node topology: it removes
the "intel_i915" root node created by the DFv1 driver; now the
"intel-gpu-core" and "intel-display-controller" are created directly
under the PCI device.

Tests using DFv1 and DFv2 cannot coexist in the same executable, so
we move the DFv2 tests to a separate target "intel-i915-dfv2-tests"
which is only linked against DFv2 libraries and runtime.

Test: intel-i915-test
Test: intel-i915-dfv2-test

Test: "display-tool squares" on core.x64 on NUC11 worked.
Test: "vkcube-on-fb" on core.x64 on NUC11 worked.
Test: "ffx driver list -v" on NUC11
      display-coordinator binds to "intel-display-controller" node
      libmsd_intel binds to "intel-gpu-core" node.
Original-Bug: 339114729
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1077013
Original-Revision: 136facb65fd76caa0067f36b812ad2dec3c49f76
GitOrigin-RevId: 6f934b267416166c910230899e2ecdcafed9ffc4
Change-Id: I993e809aed639031451e26710b39d65adf8fb31e
1 file changed
tree: 0bc9898e3a6a90df2d7cf9061a228493b06aacab
  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 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.