| Message ID | 1378303802.3485.36.camel@deneb.redhat.com (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
On Wed, Sep 04, 2013 at 03:10:02PM +0100, Mark Salter wrote: > 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 <msalter@redhat.com> > --- > Documentation/arm64/booting.txt | 6 +++--- > 1 file changed, 3 insertions(+), 3 deletions(-) > > diff --git a/Documentation/arm64/booting.txt b/Documentation/arm64/booting.txt > index 5273c4d..98df4a0 100644 > --- a/Documentation/arm64/booting.txt > +++ b/Documentation/arm64/booting.txt > @@ -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 <will.deacon@arm.com> Will
diff --git a/Documentation/arm64/booting.txt b/Documentation/arm64/booting.txt index 5273c4d..98df4a0 100644 --- a/Documentation/arm64/booting.txt +++ b/Documentation/arm64/booting.txt @@ -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.
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 <msalter@redhat.com> --- Documentation/arm64/booting.txt | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)