| commit | f13468bab4cc5468916fb58391bcf5b683da0207 | [log] [tgz] |
|---|---|---|
| author | James Sullivan <jfsulliv@fuchsia.infra.roller.google.com> | Thu Mar 27 08:28:04 2025 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Mar 27 08:30:30 2025 -0700 |
| tree | 8849c35e6915372951105058e88a9172b70b2d7c | |
| parent | 000fbe63453a033ba4baf329769d4ff76cb60f20 [diff] |
[roll] Roll fuchsia [paver] Support Nelson/Sherlock on storage-host Supports enabling storage-host on Nelson and Sherlock. To accomplish this, I needed to add support for non-GPT block devices being published from fshost to the paver. The way this works is as follows: Define a block device as "managed" by fshost if one of the two applies: - Fshost did not match the block device, OR - The block device was not published from a component that Fshost launched. Adds a directory "/block" exposed by fshost which enumerates only managed block devices, in the same format as "/debug_block". In other words, "/block" is a filtered subset of "/debug_block", which is always exposed (whereas "/debug_block" is only exposed on eng builds). In practice, this means that low-level partitions (e.g. emmc partitions) will be treated as unmanaged by fshost, and the GPT and its contained partitions are managed by fshost. The paver will use /block from fshost (instead of /dev from DF) on storage-host configurations to access non-GPT partitions. The paver will continue to access GPT partitions via the PartitionService interface. Original-Bug: 403647550 Original-Bug: 388533231 Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1233746 Original-Revision: b4f1b88acb7caf3221dc6ad4f5df820c54fb1798 GitOrigin-RevId: 7fe15e46639c7a8a011eede89cb3f1bb14caae0d Change-Id: Ic0a256a72b1c94705b9809a12b3d7aaed416cc58
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.