diff options
author | Masahiro Yamada <yamada.masahiro@socionext.com> | 2017-03-09 16:28:25 +0900 |
---|---|---|
committer | Tom Rini <trini@konsulko.com> | 2017-03-14 20:40:23 -0400 |
commit | 2808576491ae36b6ea96743005058f370d936beb (patch) | |
tree | dbde878c68a528f04cc709ea5f918379531bb503 /doc/device-tree-bindings/firmware | |
parent | 3b0825296aeba69c2cbfd3e179db2e9cbe5e70d7 (diff) |
arm64: booti: allow to place kernel image anywhere in physical memory
At first, the ARM64 Linux booting requirement recommended that the
kernel image be placed text_offset bytes from 2MB aligned base near
the start of usable system RAM because memory below that base address
was unusable at that time.
This requirement was relaxed by Linux commit a7f8de168ace ("arm64:
allow kernel Image to be loaded anywhere in physical memory").
Since then, the bit 3 of the flags field indicates the tolerance
of the kernel physical placement. If this bit is set, the 2MB
aligned base may be anywhere in physical memory. For details, see
Documentation/arm64/booting.txt of Linux.
The booti command should be also relaxed. If the bit 3 is set,
images->ep is respected, and the image is placed at the nearest
bootable location. Otherwise, it is relocated to the start of the
system RAM to keep the original behavior.
Another wrinkle we need to take care of is the unknown endianness of
text_offset for a kernel older than commit a2c1d73b94ed (i.e. v3.16).
We can detect this based on the image_size field. If the field is
zero, just use a fixed offset 0x80000.
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
Diffstat (limited to 'doc/device-tree-bindings/firmware')
0 files changed, 0 insertions, 0 deletions