Mirrors/u-boot
2
0
Fork 0
mirror of https://github.com/AsahiLinux/u-boot synced 2025-03-16 23:07:00 +00:00
Code Issues Projects Releases Packages Wiki Activity

binman: Use a reference for binman symbols docs

Browse source 
Several etypes have this reference in their documentation. Now that we are
using rST, link to the section directly.

Signed-off-by: Simon Glass <sjg@chromium.org>
Suggested-by: Quentin Schulz <quentin.schulz@theobroma-systems.com>
This commit is contained in:
Simon Glass 2023-01-07 14:07:11 -07:00
parent 237ac96a70
commit 23ab4e0054
9 changed files with 15 additions and 50 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

1
tools/binman/binman.rst
View file

@ -487,6 +487,7 @@ For x86 devices (with the end-at-4gb property) this base address is not added
since it is assumed that images are XIP and the offsets already include the
address.
.. _binman_fdt:
Access to binman entry offsets at run time (fdt)
------------------------------------------------

32
tools/binman/entries.rst
View file

@ -1578,11 +1578,7 @@ This is the U-Boot binary, containing relocation information to allow it
to relocate itself at runtime. The binary typically includes a device tree
blob at the end of it.
U-Boot can access binman symbols at runtime. See:
'Access to binman entry offsets at run time (fdt)'
in the binman README for more information.
U-Boot can access binman symbols at runtime. See :ref:`binman_fdt`.
Note that this entry is automatically replaced with u-boot-expanded unless
--no-expanded is used or the node has a 'no-expanded' property.
@ -1712,9 +1708,7 @@ not relocatable so must be loaded to the correct address in SRAM, or written
to run from the correct address if direct flash execution is possible (e.g.
on x86 devices).
SPL can access binman symbols at runtime. See:
'Access to binman entry offsets at run time (symbols)'
SPL can access binman symbols at runtime. See :ref:`binman_fdt`.
in the binman README for more information.
@ -1817,9 +1811,7 @@ entry after this one, or use a u-boot-spl entry instead' which normally
expands to a section containing u-boot-spl-dtb, u-boot-spl-bss-pad and
u-boot-spl-dtb
SPL can access binman symbols at runtime. See:
'Access to binman entry offsets at run time (symbols)'
SPL can access binman symbols at runtime. See :ref:`binman_fdt`.
in the binman README for more information.
@ -1855,9 +1847,7 @@ loader. Note that SPL is not relocatable so must be loaded to the correct
address in SRAM, or written to run from the correct address if direct
flash execution is possible (e.g. on x86 devices).
SPL can access binman symbols at runtime. See:
'Access to binman entry offsets at run time (symbols)'
SPL can access binman symbols at runtime. See :ref:`binman_fdt`.
in the binman README for more information.
@ -1972,9 +1962,7 @@ entry after this one, or use a u-boot-tpl entry instead, which normally
expands to a section containing u-boot-tpl-dtb, u-boot-tpl-bss-pad and
u-boot-tpl-dtb
TPL can access binman symbols at runtime. See:
'Access to binman entry offsets at run time (symbols)'
TPL can access binman symbols at runtime. See :ref:`binman_fdt`.
in the binman README for more information.
@ -2060,9 +2048,7 @@ loader. Note that VPL is not relocatable so must be loaded to the correct
address in SRAM, or written to run from the correct address if direct
flash execution is possible (e.g. on x86 devices).
SPL can access binman symbols at runtime. See:
'Access to binman entry offsets at run time (symbols)'
SPL can access binman symbols at runtime. See :ref:`binman_fdt`.
in the binman README for more information.
@ -2162,11 +2148,7 @@ entry after this one, or use a u_boot_vpl entry instead, which normally
expands to a section containing u-boot-vpl-dtb, u-boot-vpl-bss-pad and
u-boot-vpl-dtb
VPL can access binman symbols at runtime. See:
'Access to binman entry offsets at run time (symbols)'
in the binman README for more information.
VPL can access binman symbols at runtime. See :ref:`binman_fdt`.
The ELF file 'vpl/u-boot-vpl' must also be available for this to work, since
binman uses that to look up symbols to write into the VPL binary.

6
tools/binman/etype/u_boot.py
View file

@ -18,11 +18,7 @@ class Entry_u_boot(Entry_blob):
to relocate itself at runtime. The binary typically includes a device tree
blob at the end of it.
U-Boot can access binman symbols at runtime. See:
'Access to binman entry offsets at run time (fdt)'
in the binman README for more information.
U-Boot can access binman symbols at runtime. See :ref:`binman_fdt`.
Note that this entry is automatically replaced with u-boot-expanded unless
--no-expanded is used or the node has a 'no-expanded' property.

4
tools/binman/etype/u_boot_spl.py
View file

@ -21,9 +21,7 @@ class Entry_u_boot_spl(Entry_blob):
to run from the correct address if direct flash execution is possible (e.g.
on x86 devices).
SPL can access binman symbols at runtime. See:
'Access to binman entry offsets at run time (symbols)'
SPL can access binman symbols at runtime. See :ref:`binman_fdt`.
in the binman README for more information.

4
tools/binman/etype/u_boot_spl_nodtb.py
View file

@ -21,9 +21,7 @@ class Entry_u_boot_spl_nodtb(Entry_blob):
expands to a section containing u-boot-spl-dtb, u-boot-spl-bss-pad and
u-boot-spl-dtb
SPL can access binman symbols at runtime. See:
'Access to binman entry offsets at run time (symbols)'
SPL can access binman symbols at runtime. See :ref:`binman_fdt`.
in the binman README for more information.

4
tools/binman/etype/u_boot_tpl.py
View file

@ -21,9 +21,7 @@ class Entry_u_boot_tpl(Entry_blob):
address in SRAM, or written to run from the correct address if direct
flash execution is possible (e.g. on x86 devices).
SPL can access binman symbols at runtime. See:
'Access to binman entry offsets at run time (symbols)'
SPL can access binman symbols at runtime. See :ref:`binman_fdt`.
in the binman README for more information.

4
tools/binman/etype/u_boot_tpl_nodtb.py
View file

@ -21,9 +21,7 @@ class Entry_u_boot_tpl_nodtb(Entry_blob):
expands to a section containing u-boot-tpl-dtb, u-boot-tpl-bss-pad and
u-boot-tpl-dtb
TPL can access binman symbols at runtime. See:
'Access to binman entry offsets at run time (symbols)'
TPL can access binman symbols at runtime. See :ref:`binman_fdt`.
in the binman README for more information.

4
tools/binman/etype/u_boot_vpl.py
View file

@ -21,9 +21,7 @@ class Entry_u_boot_vpl(Entry_blob):
address in SRAM, or written to run from the correct address if direct
flash execution is possible (e.g. on x86 devices).
SPL can access binman symbols at runtime. See:
'Access to binman entry offsets at run time (symbols)'
SPL can access binman symbols at runtime. See :ref:`binman_fdt`.
in the binman README for more information.

6
tools/binman/etype/u_boot_vpl_nodtb.py
View file

@ -21,11 +21,7 @@ class Entry_u_boot_vpl_nodtb(Entry_blob):
expands to a section containing u-boot-vpl-dtb, u-boot-vpl-bss-pad and
u-boot-vpl-dtb
VPL can access binman symbols at runtime. See:
'Access to binman entry offsets at run time (symbols)'
in the binman README for more information.
VPL can access binman symbols at runtime. See :ref:`binman_fdt`.
The ELF file 'vpl/u-boot-vpl' must also be available for this to work, since
binman uses that to look up symbols to write into the VPL binary.