[roll] Roll fuchsia [display] Refactor framebuffer-intel-display into FramebufferPciBootDisplayDriver

Move PCI BAR mapping and ZBI framebuffer retrieval logic from
framebuffer-intel-display into a new FramebufferPciBootDisplayDriver
class. This allows new framebuffer-based display drivers to easily reuse
logic when there is only a parameterizable difference (such as the BAR
location).

For example, the AMD Strix Halo's framebuffer is at BAR 0 instead of BAR
2 like the Intel driver.

This change is a pure refactor, and should not change the behavior of
framebuffer-intel-display.

Original-Bug: 503064084
Test: Manual virtcon check with keyboard input on Intel NUC11TNHv5

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1574168
Original-Revision: 8bac040b043174bed9b0918b5ee4618338552d75
GitOrigin-RevId: 6e5491b8401097de5ee512e71a1f6f56647407b3
Change-Id: I8355263ef2285d2b42ae3831b5746398f2bda9f0
1 file changed
tree: d63498c46bcbb38fbef2a9388f8532b7f828305e
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. cobalt
  6. flower
  7. jiri.lock
  8. MILESTONE
  9. minimal
  10. prebuilts
  11. README.md
  12. stem
  13. test_durations
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.