From: Simon Horman <horms@verge.net.au>
To: Laurent Dufour <ldufour@linux.vnet.ibm.com>
Cc: kexec@lists.infradead.org
Subject: Re: [PATCH] kexec/ppc64: move to device tree version 17
Date: Tue, 17 Jun 2014 08:23:53 +0900 [thread overview]
Message-ID: <20140616232353.GA24011@verge.net.au> (raw)
In-Reply-To: <20140616124243.11173.39355.stgit@nimbus>
On Mon, Jun 16, 2014 at 02:42:43PM +0200, Laurent Dufour wrote:
> Kernel commit e6a6928c3ea1d0195ed75a091e345696b916c09b changed the way the
> device tree is processed in the kernel. Now version 2 is no more supported.
>
> This patch move the version of the device tree generated in ppc64
> environment from 2 to 17, allowing to kexec kernel 3.16.
>
> In addition, automates the define of NEED_STRUCTURE_BLOCK_EXTRA_PAD which
> should not be set for DT version 16 and above.
>
> Signed-off-by: Laurent Dufour <ldufour@linux.vnet.ibm.com>
Thanks, applied.
> ---
> kexec/arch/ppc64/kexec-ppc64.h | 8 +++++---
> 1 file changed, 5 insertions(+), 3 deletions(-)
>
> diff --git a/kexec/arch/ppc64/kexec-ppc64.h b/kexec/arch/ppc64/kexec-ppc64.h
> index 9a0aecf..89ee942 100644
> --- a/kexec/arch/ppc64/kexec-ppc64.h
> +++ b/kexec/arch/ppc64/kexec-ppc64.h
> @@ -6,9 +6,11 @@
> #define CORE_TYPE_ELF32 1
> #define CORE_TYPE_ELF64 2
>
> -#define BOOT_BLOCK_VERSION 2
> -#define BOOT_BLOCK_LAST_COMP_VERSION 2
> -#define NEED_STRUCTURE_BLOCK_EXTRA_PAD
> +#define BOOT_BLOCK_VERSION 17
> +#define BOOT_BLOCK_LAST_COMP_VERSION 17
> +#if (BOOT_BLOCK_VERSION < 16)
> +# define NEED_STRUCTURE_BLOCK_EXTRA_PAD
> +#endif
> #define HAVE_DYNAMIC_MEMORY
> #define NEED_RESERVE_DTB
>
>
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
prev parent reply other threads:[~2014-06-16 23:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-16 12:42 [PATCH] kexec/ppc64: move to device tree version 17 Laurent Dufour
2014-06-16 23:23 ` Simon Horman [this message]
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=20140616232353.GA24011@verge.net.au \
--to=horms@verge.net.au \
--cc=kexec@lists.infradead.org \
--cc=ldufour@linux.vnet.ibm.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox