Greg Kroah-Hartman
598cf27219
Link: https://lore.kernel.org/r/20260217200002.683975158@linuxfoundation.org Tested-by: Florian Fainelli <florian.fainelli@broadcom.com> Tested-by: Takeshi Ogasawara <takeshi.ogasawara@futuring-girl.com> Tested-by: Peter Schneider <pschneider1968@googlemail.com> Tested-by: Jon Hunter <jonathanh@nvidia.com> Tested-by: Salvatore Bonaccorso <carnil@debian.org> Tested-by: Brett A C Sheffield <bacs@librecast.net> Tested-by: Mark Brown <broonie@kernel.org> Tested-by: Luna Jernberg <droidbittin@gmail.com> Tested-by: Ronald Warsow <rwarsow@gmx.de> Tested-by: Justin M. Forbes <jforbes@fedoraproject.org> Tested-by: Ron Economos <re@w6rz.net> Tested-by: Miguel Ojeda <ojeda@kernel.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
29 lines
1.0 KiB
ReStructuredText
29 lines
1.0 KiB
ReStructuredText
.. SPDX-License-Identifier: GPL-2.0
|
|
|
|
BMIPS DeviceTree Booting
|
|
------------------------
|
|
|
|
Some bootloaders only support a single entry point, at the start of the
|
|
kernel image. Other bootloaders will jump to the ELF start address.
|
|
Both schemes are supported; CONFIG_BOOT_RAW=y and CONFIG_NO_EXCEPT_FILL=y,
|
|
so the first instruction immediately jumps to kernel_entry().
|
|
|
|
Similar to the arch/arm case (b), a DT-aware bootloader is expected to
|
|
set up the following registers:
|
|
|
|
a0 : 0
|
|
|
|
a1 : 0xffffffff
|
|
|
|
a2 : Physical pointer to the device tree block (defined in chapter
|
|
II) in RAM. The device tree can be located anywhere in the first
|
|
512MB of the physical address space (0x00000000 - 0x1fffffff),
|
|
aligned on a 64 bit boundary.
|
|
|
|
Legacy bootloaders do not use this convention, and they do not pass in a
|
|
DT block. In this case, Linux will look for a builtin DTB, selected via
|
|
CONFIG_DT_*.
|
|
|
|
This convention is defined for 32-bit systems only, as there are not
|
|
currently any 64-bit BMIPS implementations.
|