kexec.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
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: bring up new ppc64le architecture
Date: Tue, 19 Nov 2013 10:01:40 +0900	[thread overview]
Message-ID: <20131119010140.GA17628@verge.net.au> (raw)
In-Reply-To: <20131115150151.25401.49768.stgit@nimbus>

On Fri, Nov 15, 2013 at 04:01:51PM +0100, Laurent Dufour wrote:
> This patch provides support for the new Power PC litte endian (LE) mode. The
> LE mode only differs in the way the instructions and data are stored in memory
> thus there is no real need to duplicate the ppc64 code.
> 
> However some compilation's options, especially for the purgatory, differ
> between little and big endian mode's support. A new "SUBARCH" build variable
> is introduced which is currently only used for PPC64 to specify the
> endianness.
> 
> Another set of changes in this patch is fixing minor endianess issues in the
> ppc64 code and fix an alignment issue raised on Power7 little endian mode.
> Among these fixes, the check on the kernel binary endianess is removed,
> since we can imagine kexecing a LE kernel from a BE environment, as far as
> the specified root filesystem and initrd file are containing the right
> binaries.
> 
> This patch depends on the patch "kexec/ppc64: use common architecture
> fs2dt.c file" I sent earlier on the kexec mailing list.
> 
> Signed-off-by: Laurent Dufour <ldufour@linux.vnet.ibm.com>

Hi Laurent,

I have applied this. But could you let me know how to (cross) compile it?

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

  reply	other threads:[~2013-11-19  1:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-15 15:01 [PATCH] kexec/ppc64: bring up new ppc64le architecture Laurent Dufour
2013-11-19  1:01 ` Simon Horman [this message]
2013-11-20 10:48   ` Laurent Dufour

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=20131119010140.GA17628@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;
as well as URLs for NNTP newsgroup(s).