From e29a99ac3bbf2481be9a5c7d985539b60900fcac Mon Sep 17 00:00:00 2001 From: =?utf8?q?Roger=20Pau=20Monn=C3=A9?= Date: Sat, 23 Jun 2018 21:32:03 +0200 Subject: [PATCH] multiboot2: Clarify usage of the address tag MIME-Version: 1.0 Content-Type: text/plain; charset=utf8 Content-Transfer-Encoding: 8bit Add a note to spell out that if the address tag is not present the file should be loaded using the elf header. Signed-off-by: Roger Pau Monné Reviewed-by: Daniel Kiper --- doc/multiboot.texi | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/doc/multiboot.texi b/doc/multiboot.texi index 2e2d7e74a..df8a0d056 100644 --- a/doc/multiboot.texi +++ b/doc/multiboot.texi @@ -509,6 +509,14 @@ assumes that no bss segment is present. @end table +Note: This information does not need to be provided if the kernel image +is in @sc{elf} format, but it must be provided if the image is in a.out +format or in some other format. When the address tag is present it must +be used in order to load the image, regardless of whether an @sc{elf} +header is also present. Compliant boot loaders must be able to load +images that are either in @sc{elf} format or contain the address tag +embedded in the Multiboot2 header. + @subsection The entry address tag of Multiboot2 header @example -- 2.47.2