[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190318094412.GA18161@codeblueprint.co.uk>
Date: Mon, 18 Mar 2019 09:44:12 +0000
From: Matt Fleming <matt@...eblueprint.co.uk>
To: Juergen Gross <jgross@...e.com>
Cc: linux-kernel@...r.kernel.org, linux-doc@...r.kernel.org,
x86@...nel.org, corbet@....net, hpa@...or.com, bp@...en8.de,
mingo@...hat.com, tglx@...utronix.de, konrad.wilk@...cle.com,
mfleming@...e.com, ross.philipson@...cle.com,
daniel.kiper@...cle.com
Subject: Re: [PATCH] doc: add boot protocol 2.13 description to
Documentation/x86/boot.txt
On Fri, 08 Mar, at 12:43:10PM, Juergen Gross wrote:
> Documentation/x86/boot.txt is missing protocol 2.13 description.
>
> Signed-off-by: Juergen Gross <jgross@...e.com>
> ---
> Documentation/x86/boot.txt | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/Documentation/x86/boot.txt b/Documentation/x86/boot.txt
> index f4c2a97bfdbd..223e484a1304 100644
> --- a/Documentation/x86/boot.txt
> +++ b/Documentation/x86/boot.txt
> @@ -61,6 +61,10 @@ Protocol 2.12: (Kernel 3.8) Added the xloadflags field and extension fields
> to struct boot_params for loading bzImage and ramdisk
> above 4G in 64bit.
>
> +Protocol 2.13: (Kernel 3.14) Support 32- and 64-bit flags being set in
> + xloadflags to support booting a 64-bit kernel from 32-bit
> + EFI
> +
> **** MEMORY LAYOUT
>
> The traditional memory map for the kernel loader, used for Image or
> --
> 2.16.4
Not sure if this has already been picked up but...
Reviewed-by: Matt Fleming <matt@...eblueprint.co.uk>
Powered by blists - more mailing lists