template <>class WireWeakSyncClientImpl
Defined at line 10903 of file fidling/gen/sdk/fidl/fuchsia.paver/fuchsia.paver/cpp/fidl/fuchsia.paver/cpp/wire_messaging.h
Public Methods
::fidl::WireResult< ::fuchsia_paver::DynamicDataSink::ReadAsset> ReadAsset (::fuchsia_paver::wire::Configuration configuration, ::fuchsia_paver::wire::Asset asset)Reads the partition corresponding to `configuration` and `asset` into a vmo and returns it.
The size field of the returned `Buffer` will be the size of just the asset, if it can be
determined. Otherwise, it will be the size of the entire partition.
The size and stream size of the vmo in the returned `Buffer` will always be the size of the
entire partition.
Allocates 72 bytes of message buffer on the stack. No heap allocation necessary.
::fidl::WireResult< ::fuchsia_paver::DynamicDataSink::WriteAsset> WriteAsset (::fuchsia_paver::wire::Configuration configuration, ::fuchsia_paver::wire::Asset asset, ::fuchsia_mem::wire::Buffer && payload)Writes partition corresponding to `configuration` and `asset` with data from `payload`.
`payload` may need to be resized to the partition size, so the provided vmo must have
been created with `ZX_VMO_RESIZABLE` or must be a child VMO that was created with
`ZX_VMO_CHILD_RESIZABLE`. Will zero out rest of the partition if `payload` is smaller
than the size of the partition being written.
Returns `ZX_ERR_INVALID_ARGS` if `configuration` specifies active configuration.
Allocates 64 bytes of message buffer on the stack. No heap allocation necessary.
::fidl::WireResult< ::fuchsia_paver::DynamicDataSink::WriteFirmware> WriteFirmware (::fuchsia_paver::wire::Configuration configuration, ::fidl::StringView type, ::fuchsia_mem::wire::Buffer && payload)Writes firmware data from `payload`.
`configuration` represents the A/B/R configuration. For platforms that do not support
firmware A/B/R, the parameter will be ignored by the underlying device-specific logic .
`type` is a device-specific string identifying the payload contents,
used to select the proper paving logic. For example, a device with
multiple bootloader stages might send them as separate calls to
`WriteFirmware()`, differentiated by `type`. An empty string
indicates the default type.
`payload` may need to be resized to the partition size, so the provided
vmo must have been created with `ZX_VMO_RESIZABLE` or must be a child
VMO that was created with `ZX_VMO_CHILD_RESIZABLE`.
Allocates 344 bytes of message buffer on the stack. No heap allocation necessary.
::fidl::WireResult< ::fuchsia_paver::DynamicDataSink::ReadFirmware> ReadFirmware (::fuchsia_paver::wire::Configuration configuration, ::fidl::StringView type)Read firmware corresponding to `configuration` and `type`.
Parameter `configuration` and `type` are the same as WriteFirmware.
If ReadFirmware returns error, caller should assume that firmware image does not exist
or is in a bad state, or firmware read is not defined for the product.
Allocates 344 bytes of message buffer on the stack. No heap allocation necessary.
::fidl::WireResult< ::fuchsia_paver::DynamicDataSink::WriteVolumes> WriteVolumes (::fidl::ClientEnd< ::fuchsia_paver::PayloadStream> && payload)Writes FVM with data from streamed via `payload`. This potentially affects all
configurations.
Allocates 48 bytes of message buffer on the stack. No heap allocation necessary.
::fidl::WireResult< ::fuchsia_paver::DynamicDataSink::WriteOpaqueVolume> WriteOpaqueVolume (::fuchsia_mem::wire::Buffer && payload)Write a raw volume image to the device. The image will be passed as it is to the device
partitioner backend to write. Therefore the format and write logic for the image is up to
the product to define. It differs from WriteVolume(), which is specifically for writing the
FVM sparse image, in that the paver will not perform any FVM related parsing or other
operation of the image. Thus it is not dependent on the volume driver version and less
susceptible to an outdated paver.
Returns ZX_ERR_NOT_SUPPORTED if the backend does not support opaque volume blobs.
Allocates 64 bytes of message buffer on the stack. No heap allocation necessary.
::fidl::WireResult< ::fuchsia_paver::DynamicDataSink::WriteSparseVolume> WriteSparseVolume (::fuchsia_mem::wire::Buffer && payload)Writes an image in the Android Sparse format. Identical in behaviour to
`WriteOpaqueVolume`, except the contents of `payload` are parsed as a sparse image and
unpacked before being written to disk.
Allocates 64 bytes of message buffer on the stack. No heap allocation necessary.
::fidl::WireResult< ::fuchsia_paver::DynamicDataSink::Flush> Flush ()Flush all previously buffered writes to persistent storage.
Allocates 40 bytes of message buffer on the stack. No heap allocation necessary.
::fidl::WireResult< ::fuchsia_paver::DynamicDataSink::InitializePartitionTables> InitializePartitionTables ()Initializes partitions on given block device.
Currently only supported on devices which don't support fastboot (which is the preferred
mechanism for device setup).
*WARNING*: This API will wipe the existing partitions and data loss may occur. Non-Fuchsia
partitions *may* be preserved, although this is behaviour is board-specific.
Allocates 40 bytes of message buffer on the stack. No heap allocation necessary.
::fidl::WireResult< ::fuchsia_paver::DynamicDataSink::WipePartitionTables> WipePartitionTables ()Wipes all entries from the partition table of the specified block device.
Currently only supported on devices with a GPT.
*WARNING*: This API may destructively remove non-fuchsia maintained partitions from
the block device.
Allocates 40 bytes of message buffer on the stack. No heap allocation necessary.