[roll] Roll fuchsia [kernel][coresight] Do not constrain enumerated components

Previously we would error out if the components found in a ROM table
were not of "CoreSight class" or that of a particular legacy timestamp
generator. In this change, we remove that assertion, as such logic is an
overfit and does not leave room for leniency in encountering other
legacy components or vendor-specific wonkiness. A ROM table walker
should just be in the business of reporting its entries; validation of
expected components is more reasonably deferred to users.

Original-Bug: 103310
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/694686
Original-Revision: 1ba67b63e9e38ccebbfde10e584cd2ce80f4f4cc
GitOrigin-RevId: bf99a5314788ddd57a05c9f7b19881f355f68359
Change-Id: I4c71a6e96ce4abf2966da448fe90710f827e42cf
1 file changed
tree: ab33039f1eff145d48084d213a2edf2c32299a8b
  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.