diff options
Diffstat (limited to 'doc/usage')
-rw-r--r-- | doc/usage/cmd/bootflow.rst | 4 | ||||
-rw-r--r-- | doc/usage/cmd/load.rst | 2 | ||||
-rw-r--r-- | doc/usage/fit/howto.rst | 4 |
3 files changed, 5 insertions, 5 deletions
diff --git a/doc/usage/cmd/bootflow.rst b/doc/usage/cmd/bootflow.rst index ead493d0aaf..9c5ea9c5d84 100644 --- a/doc/usage/cmd/bootflow.rst +++ b/doc/usage/cmd/bootflow.rst @@ -514,8 +514,8 @@ the cmdline is word-wrapped here and some parts of the command line are elided:: root_hexdigest=78cc462cd45aecbcd49ca476587b4dee59aa1b00ba5ece58e2c29ec9acd914ab salt=8dec4dc80a75dd834a9b3175c674405e15b16a253fdfe05c79394ae5fd76f66a" noinitrd vt.global_cursor_default=0 - kern_guid=799c935b-ae62-d143-8493-816fa936eef7 add_efi_memmap boot=local - noresume noswap i915.modeset=1 ramoops.ecc=1 tpm_tis.force=0 + kern_guid=799c935b-ae62-d143-8493-816fa936eef7 add_efi_memmap + noresume i915.modeset=1 ramoops.ecc=1 tpm_tis.force=0 intel_pmc_core.warn_on_s0ix_failures=1 i915.enable_guc=3 i915.enable_dc=4 xdomain=0 swiotlb=65536 intel_iommu=on i915.enable_psr=1 usb-storage.quirks=13fe:6500:u diff --git a/doc/usage/cmd/load.rst b/doc/usage/cmd/load.rst index 1efee773179..2c892ee1cb7 100644 --- a/doc/usage/cmd/load.rst +++ b/doc/usage/cmd/load.rst @@ -40,7 +40,7 @@ bytes pos number of bytes to skip -addr, bytes, pos are hexadecimal numbers. +part, addr, bytes, pos are hexadecimal numbers. Example ------- diff --git a/doc/usage/fit/howto.rst b/doc/usage/fit/howto.rst index c933703d1d0..def12a70f7b 100644 --- a/doc/usage/fit/howto.rst +++ b/doc/usage/fit/howto.rst @@ -21,8 +21,8 @@ important that the dtc used has support for binary includes -- refer to:: for its latest version. mkimage (together with dtc) takes as input an image source file, which describes the contents of the image and defines its various properties used during booting. By convention, image source file -has the ".its" extension, also, the details of its format are given in -doc/uImage.FIT/source_file_format.txt. The actual data that is to be included in +has the ".its" extension, also, the details of its format are provided in +:doc:`source_file_format`. The actual data that is to be included in the uImage (kernel, ramdisk, etc.) is specified in the image source file in the form of paths to appropriate data files. The outcome of the image creation process is a binary file (by convention with the ".itb" extension) that |