All of lore.kernel.org
 help / color / mirror / Atom feed
From: cov@codeaurora.org (Christopher Covington)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 0/4] Big Endian support for ARM64 kernel
Date: Tue, 15 Oct 2013 14:09:21 -0400	[thread overview]
Message-ID: <525D84D1.2000609@codeaurora.org> (raw)
In-Reply-To: <1381494135-15085-1-git-send-email-ankit.jindal@linaro.org>

Hi Ankit,

On 10/11/2013 08:22 AM, Ankit Jindal wrote:
> This patchset adds support for using Big Endian mode of AArch64 CPUs
> 
> All patches have been tested on APM X-Gene Storm SOC.
> 
> The Big Endian toolchain used for development can be found at:
> http://cbuild.validation.linaro.org/snapshots/big_endian

At this URL I see:

404 Not Found

Thanks,
Christopher

-- 
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by the Linux Foundation.

  parent reply	other threads:[~2013-10-15 18:09 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-11 12:22 [RFC PATCH 0/4] Big Endian support for ARM64 kernel Ankit Jindal
2013-10-11 12:22 ` [RFC PATCH 1/4] ARM64: Add Kconfig option to enable Big Endian kernel Ankit Jindal
2013-10-15 18:09   ` Christopher Covington
2013-10-16  6:49     ` Tushar Jagad
2013-10-16 14:30       ` Christopher Covington
2013-10-11 12:22 ` [RFC PATCH 2/4] ARM64: Include appropriate byteorder for Big Endian Ankit Jindal
2013-10-11 12:22 ` [RFC PATCH 3/4] ARM64: Big Endian fixes for kernel booting Ankit Jindal
2013-10-11 12:52   ` Ankit Jindal
2013-10-15 18:24   ` Christopher Covington
2013-10-16  7:04     ` Tushar Jagad
2013-10-11 12:22 ` [RFC PATCH 4/4] ARM64: Support for 32-bit big endian userspace Ankit Jindal
2013-10-15 18:09 ` Christopher Covington [this message]
2013-10-16  8:05   ` [RFC PATCH 0/4] Big Endian support for ARM64 kernel Tushar Jagad
2013-10-16 14:40     ` Christopher Covington

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=525D84D1.2000609@codeaurora.org \
    --to=cov@codeaurora.org \
    --cc=linux-arm-kernel@lists.infradead.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.