diff options
| author | Daniel Golle <[email protected]> | 2026-05-16 00:37:52 +0100 |
|---|---|---|
| committer | Tom Rini <[email protected]> | 2026-05-27 13:41:33 -0600 |
| commit | cafe3d6e90e661bd9d42b19f1e2d891da48f3fce (patch) | |
| tree | 85085002dc369ed6eeeda9901983bb8fe898a1f2 /contrib/examples/httpd/https_example | |
| parent | d3eee4d3b120f2fe30932b2f29d935cc9ac9ddb3 (diff) | |
boot: fit: support generating DM verity cmdline parameters
Add fit_verity_build_cmdline(): when a FILESYSTEM loadable carries a
dm-verity subnode, construct the dm-mod.create= kernel cmdline parameter
from the verity metadata (block-size, data-blocks, algo, root-hash,
salt) and append it to bootargs.
Also add dm-mod.waitfor=/dev/fit0[,/dev/fitN] for each dm-verity device
so the kernel waits for the underlying FIT block device to appear before
setting up device-mapper targets. This is needed when the block driver
probes late, e.g. because it depends on NVMEM calibration data.
The dm-verity target references /dev/fitN where N is the loadable's
index in the configuration -- matching the order Linux's FIT block
driver assigns block devices. hash-start-block is read directly from
the FIT dm-verity node; mkimage ensures its value equals num-data-blocks
by invoking veritysetup with --no-superblock.
Signed-off-by: Daniel Golle <[email protected]>
Reviewed-by: Simon Glass <[email protected]>
Diffstat (limited to 'contrib/examples/httpd/https_example')
0 files changed, 0 insertions, 0 deletions
