All of lore.kernel.org
 help / color / mirror / Atom feed
From: Roger Pau Monne <roger.pau@citrix.com>
To: grub-devel@gnu.org
Cc: xen-devel@lists.xenproject.org,
	Daniel Kiper <daniel.kiper@oracle.com>,
	Roger Pau Monne <roger.pau@citrix.com>
Subject: [PATCH v2] multiboot2: clarify usage of the address tag
Date: Thu, 7 Jun 2018 17:59:06 +0200	[thread overview]
Message-ID: <20180607155906.14304-1-roger.pau@citrix.com> (raw)

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é <roger.pau@citrix.com>
---
Cc: Daniel Kiper <daniel.kiper@oracle.com>
Cc: xen-devel@lists.xenproject.org
---
Changes since v1:
 - s/elf/@sc{elf}/
 - s/Multiboot/Multiboot2/
---
 doc/multiboot.texi | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/doc/multiboot.texi b/doc/multiboot.texi
index 2e2d7e74a..3c797787c 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 @sc{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 @sc{elf} format or contain the address
+tag embedded in the Multiboot2 header.
+
 @subsection The entry address tag of Multiboot2 header
 
 @example
-- 
2.17.1


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

WARNING: multiple messages have this Message-ID (diff)
From: Roger Pau Monne <roger.pau@citrix.com>
To: <grub-devel@gnu.org>
Cc: Roger Pau Monne <roger.pau@citrix.com>,
	Daniel Kiper <daniel.kiper@oracle.com>,
	<xen-devel@lists.xenproject.org>
Subject: [PATCH v2] multiboot2: clarify usage of the address tag
Date: Thu, 7 Jun 2018 17:59:06 +0200	[thread overview]
Message-ID: <20180607155906.14304-1-roger.pau@citrix.com> (raw)

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é <roger.pau@citrix.com>
---
Cc: Daniel Kiper <daniel.kiper@oracle.com>
Cc: xen-devel@lists.xenproject.org
---
Changes since v1:
 - s/elf/@sc{elf}/
 - s/Multiboot/Multiboot2/
---
 doc/multiboot.texi | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/doc/multiboot.texi b/doc/multiboot.texi
index 2e2d7e74a..3c797787c 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 @sc{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 @sc{elf} format or contain the address
+tag embedded in the Multiboot2 header.
+
 @subsection The entry address tag of Multiboot2 header
 
 @example
-- 
2.17.1



             reply	other threads:[~2018-06-07 15:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-07 15:59 Roger Pau Monne [this message]
2018-06-07 15:59 ` [PATCH v2] multiboot2: clarify usage of the address tag Roger Pau Monne
2018-06-08  9:35 ` Daniel Kiper
2018-06-08  9:35 ` Daniel Kiper
2018-06-08 10:08   ` Roger Pau Monné
2018-06-08 10:08   ` Roger Pau Monné
2018-06-08 10:39     ` Daniel Kiper
2018-06-11  9:30       ` Roger Pau Monné
2018-06-11  9:30       ` Roger Pau Monné
2018-06-11 11:16         ` Daniel Kiper
2018-06-11 11:16         ` Daniel Kiper
2018-06-08 10:39     ` Daniel Kiper

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180607155906.14304-1-roger.pau@citrix.com \
    --to=roger.pau@citrix.com \
    --cc=daniel.kiper@oracle.com \
    --cc=grub-devel@gnu.org \
    --cc=xen-devel@lists.xenproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.