diff options
| author | Tom Rini <[email protected]> | 2023-04-05 18:59:47 -0400 |
|---|---|---|
| committer | Tom Rini <[email protected]> | 2023-04-05 18:59:47 -0400 |
| commit | 487e42f7bc5e685c9337890a38358581bb4f31bc (patch) | |
| tree | 03133e406371e92ce12b03b50c61a82637eea827 /disk | |
| parent | 25eeda170c5e533ca0e3837c8b2d7404cdd749d1 (diff) | |
| parent | 272ec6b453049beaf0de6654dabf9bbd5f617022 (diff) | |
Merge branch '2023-04-05-blkmap-composable-virtual-block-devices'
To quote the author:
Block maps are a way of looking at various sources of data through the
lens of a regular block device. It lets you treat devices that are not
block devices, like RAM, as if they were. It also lets you export a
slice of an existing block device, which does not have to correspond to
a partition boundary, as a new block device.
This is primarily useful because U-Boot's filesystem drivers only
operate on block devices, so a block map lets you access filesystems
wherever they might be located.
The implementation is loosely modeled on Linux's "Device Mapper"
subsystem, see the kernel documentation [1] for more information.
The primary use-cases are to access filesystem images stored in RAM, and
within FIT images stored on disk. See doc/usage/blkmap.rst for more
details.
The architecture is pluggable, so adding other types of mappings should
be quite easy.
[1]: https://docs.kernel.org/admin-guide/device-mapper/index.html
Diffstat (limited to 'disk')
| -rw-r--r-- | disk/part.c | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/disk/part.c b/disk/part.c index d449635254e..35300df5903 100644 --- a/disk/part.c +++ b/disk/part.c @@ -140,6 +140,7 @@ void dev_print(struct blk_desc *dev_desc) case UCLASS_NVME: case UCLASS_PVBLOCK: case UCLASS_HOST: + case UCLASS_BLKMAP: printf ("Vendor: %s Rev: %s Prod: %s\n", dev_desc->vendor, dev_desc->revision, |