[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH] multiboot2: clarify usage of the address tag

From: Daniel Kiper
Subject: Re: [PATCH] multiboot2: clarify usage of the address tag
Date: Wed, 6 Jun 2018 19:28:20 +0200
User-agent: Mutt/1.5.21 (2010-09-15)

On Tue, Jun 05, 2018 at 11:55:36AM +0200, Roger Pau Monne wrote:
> 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é <address@hidden>
> ---
> Cc: Daniel Kiper <address@hidden>
> Cc: address@hidden
> ---
>  doc/multiboot.texi | 6 ++++++
>  1 file changed, 6 insertions(+)
> diff --git a/doc/multiboot.texi b/doc/multiboot.texi
> index 2e2d7e74a..196f9c17a 100644
> --- a/doc/multiboot.texi
> +++ b/doc/multiboot.texi
> @@ -509,6 +509,12 @@ assumes that no bss segment is present.
>  @end table
> +Note: This information does not need to be provided if the kernel
> +image is in elf format, but it must be provided if the image is in


> +a.out format or in some other format. Compliant boot loaders must be
> +able to load images that are either in elf format or contain the


> +address tag embedded in the Multiboot header.


I think that it is also worth mentioning that the address tag has
preference over relevant data provided in ELF header.

Additionally, may I ask you to provide similar patch for Multiboot spec?
You can find it in multiboot branch. Please look for "The address fields
of Multiboot header" paragraph.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]