u-boot.git/doc/usage/fit, branch v2024.10

doc: add missing table of content links

2024-07-19T09:55:56Z

add missing table of content links, make alphabetical Signed-off-by: Sam Povilus Reviewed-by: Simon Glass

doc: Remove FIT documentation that is elsewhere

2024-07-19T09:55:56Z

Before 9d0750064e (doc: Move external FIT docs into the main body), the FIT property data-size was not a mandatory property and still it is not expected to be set alongside the data property. Move the data-size property to the "Conditionally mandatory property" section, where it actually belongs. Signed-off-by: Sam Povilus Reviewed-by: Simon Glass

Merge branch 'next'

2024-07-01T21:00:56Z

doc: fit: Make data-size a conditionally mandatory property

2024-06-30T11:58:31Z

Drop the special am335x_boneblack_vboot target

2024-06-28T19:54:52Z

Now that am335x_evm boots OK on the Beaglebone black, drop the latter and update the docs to cover the change. Also add a few updates about 'make fit' and drop the note about the security review, as U-Boot's verified boot has had quite extensive review now. Signed-off-by: Simon Glass Reviewed-by: Tom Rini

doc: Fix link reference to general verified boot docs

2024-06-16T08:37:10Z

Fixes: ad29e08b79fd ("doc: Bring in FIT signature files") Signed-off-by: Alexander Dahl Reviewed-by: Simon Glass

doc: add clarity to what a "fpga" image is

2024-06-06T07:24:10Z

Update fit documentation to clarify that FPGA images are vendor specific and opaque bitstreams. Signed-off-by: Sam Povilus

doc: Remove extraneous curly braces

2024-06-06T07:24:10Z

Update documentation to remove un-needed curly braces. Signed-off-by: Sam Povilus

rsa: use pkcs11 uri as defined in rfc7512

2023-12-20T14:48:17Z

pkcs11 : change engine uri to use full pk11-URI as defined in: https://www.rfc-editor.org/rfc/rfc7512.html Signed-off-by: Ayoub Zaki

doc: Replace examples of MD5 and SHA1 with SHA256

2023-12-17T12:06:48Z

Both SHA1 and (especially) MD5 are no longer as safe as they once were for cryptographic use. Replaces examples which use them with examples using SHA256 instead. This will provide more-secure defaults for users who use documentation examples as a base for their own use. This is not too necessary for non-verified-boot scenarios (since someone could just replace the checksum), but I wanted to be complete. Signed-off-by: Sean Anderson Reviewed-by: Peter Robinson Reviewed-by: Simon Glass Reviewed-by: Tom Rini