Documentation/arm64: clarify requirements for DTB placement
PATCH 1/1 Documentation/arm64: clarify requirements for DTB placement
The current description of DTB placement requirements does not quite match the kernel code in head.S: __vet_fdt and __create_page_tables. This patch tweaks the text to match the actual requirements placed on it by the code.
Signed-off-by Mark Salter <[email protected]>
--- Documentation/arm64/booting.txt | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
Documentation/arm64/booting.txt +3 -3
@@ -45,9 +45,9 @@ sees fit.) Requirement: MANDATORY -The device tree blob (dtb) must be no bigger than 2 megabytes in size -and placed at a 2-megabyte boundary within the first 512 megabytes from -the start of the kernel image. This is to allow the kernel to map the +The device tree blob (dtb) must be placed on an 8-byte boundary within +the first 512 megabytes from the start of the kernel image and must not +cross a 2-megabyte boundary. This is to allow the kernel to map the blob using a single section mapping in the initial page tables.
Signature · 1 line
1.8.3.1
PATCH 1/1 Documentation/arm64: clarify requirements for DTB placement
Quoted 15 lines · Mark Salter
The current description of DTB placement requirements does not quite match the kernel code in
head.S:__vet_fdtand__create_page_tables. This patch tweaks the text to match the actual requirements placed on it by the code.Signed-off-by Mark Salter <[email protected]>--- Documentation/arm64/booting.txt | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)Documentation/arm64/booting.txt +0
-0
Documentation/arm64/booting.txt sees fit.) · line 51
Quoted 10 lines
Documentation/arm64/booting.txt +3
-3@@ -45,9 +45,9 @@ sees fit.) Requirement: MANDATORY -The device tree blob (dtb) must be no bigger than 2 megabytes in size -and placed at a 2-megabyte boundary within the first 512 megabytes from -the start of the kernel image. This is to allow the kernel to map the +The device tree blob (dtb) must be placed on an 8-byte boundary within +the first 512 megabytes from the start of the kernel image and must not +cross a 2-megabyte boundary. This is to allow the kernel to map the blob using a single section mapping in the initial page tables.
Yes, that's a better way of wording the requirements. Thanks!
Acked-by Will Deacon <[email protected]>
Will