From: ben.dooks@codethink•co.uk (Ben Dooks)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 0/2] additional vexpress-tc2 big endian fixes
Date: Tue, 08 Oct 2013 09:27:49 +0200 [thread overview]
Message-ID: <5253B3F5.1020704@codethink.co.uk> (raw)
In-Reply-To: <1381207040-1623-1-git-send-email-victor.kamensky@linaro.org>
On 08/10/13 06:37, Victor Kamensky wrote:
> Hi Ben,
>
> Here are couple more big endian related fixes. We run into these
> with vexpress TC2 board, when CONFIG_MCPM and CONFIG_ARM_CCI configs
> are enabled. Big endian image fails to boot. With fixes BE TC2
> boots and it sees all 5 cores (2xA15, 3xA7).
>
> These were tested with vexpress TC2 on latest linux-linaro
> branch (include BE patch series) and it was tested on very
> recent rmk/fixes branch along with BE series on top of it.
>
> Thanks,
> Victor
>
> Victor Kamensky (2):
> ARM: mcpm: fix big endian issue in mcpm startup code
> ARM: cci: driver need big endian fixes in asm code
>
> arch/arm/common/mcpm_head.S | 2 ++
> drivers/bus/arm-cci.c | 6 ++++++
> 2 files changed, 8 insertions(+)
Thanks, anyone any objections if these go into my 312-rc4 branch?
--
Ben Dooks http://www.codethink.co.uk/
Senior Engineer Codethink - Providing Genius
prev parent reply other threads:[~2013-10-08 7:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-08 4:37 [PATCH 0/2] additional vexpress-tc2 big endian fixes Victor Kamensky
2013-10-08 4:37 ` [PATCH 1/2] ARM: mcpm: fix big endian issue in mcpm startup code Victor Kamensky
2013-10-08 4:37 ` [PATCH 2/2] ARM: cci: driver need big endian fixes in asm code Victor Kamensky
2013-10-08 17:51 ` Dave Martin
2013-10-08 17:57 ` Nicolas Pitre
2013-10-08 18:03 ` Dave Martin
2013-10-08 18:14 ` Victor Kamensky
2013-10-08 18:26 ` Nicolas Pitre
2013-10-08 7:27 ` Ben Dooks [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=5253B3F5.1020704@codethink.co.uk \
--to=ben.dooks@codethink$(echo .)co.uk \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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