[roll] Roll fuchsia [boot-shim] Matcher ignore nodes that are not ok

"status" property may be okay/ok, fail, fail-sss or disabled.
We only should look at nodes whose status is okay. When the
status is missing, docs say we should assume its ok.

CPU Topology is slightly more complex, as there are two
parallel data structures, the CPU entries (information about
each cpu, including their status) and then the topology
itself which is linked to the CPU entries through phandles.

In order to generate the correct topology, we must first
generate the topology information, and determine which of
those cpu references is no longer valid AND which of the
container structures (e.g. socket, cluster) are no longer
valid (e.g. they contain no "okay" CPUs).

Original-Fixed: 385360435
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1191094
Original-Revision: eb77d06618814eeb0d6ecabaa3fb58f62f4008c1
GitOrigin-RevId: bbd2ccfaed2b16ee9ce39b6ed4963cc3f10e8a7d
Change-Id: I6a5669225c32bbb3ae075e2a5d3786e616dfb4d5
1 file changed
tree: 239527bfb0b5dcd1d374a3493d90670011b87fa2
  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.