[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140416104453.571c8d10@skate>
Date: Wed, 16 Apr 2014 10:44:53 +0200
From: Thomas Petazzoni <thomas.petazzoni@...e-electrons.com>
To: Sebastian Hesselbarth <sebastian.hesselbarth@...il.com>
Cc: Andrew Lunn <andrew@...n.ch>, Kevin Hilman <khilman@...aro.org>,
Russell King <linux@....linux.org.uk>,
Jason Cooper <jason@...edaemon.net>,
Arnd Bergmann <arnd@...db.de>,
Chao Xie <xiechao.mail@...il.com>,
linux-kernel@...r.kernel.org,
Haojian Zhuang <haojian.zhuang@...il.com>,
Gregory Clement <gregory.clement@...e-electrons.com>,
Olof Johansson <olof@...om.net>,
Eric Miao <eric.y.miao@...il.com>,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH 0/5] fixing regressions caused by Dove in MULTI_V7
Dear Sebastian Hesselbarth,
On Tue, 15 Apr 2014 20:15:58 +0200, Sebastian Hesselbarth wrote:
> Sebastian Hesselbarth (5):
> ARM: iwmmxt: explicitly check for supported architectures
> ARM: pj4: enable iWMMXt only if CONFIG_IWMMXT is set
> ARM: pj4: properly detect existence of iWMMXt coprocessor
> ARM: pj4: fix cpu_is_pj4 check
> ARM: iwmmxt: allow to build iWMMXt on Marvell PJ4B
Tested-by: Thomas Petazzoni <thomas.petazzoni@...e-electrons.com>.
It does fix the boot on PJ4B-MP based processors that don't have iWMMXt
extensions such as the Armada XP. I've tested the following cases:
* Armada XP (PJ4B-MP), with CONFIG_MACH_DOVE disabled and enabled
* Armada 370 (PJ4B), with CONFIG_MACH_DOVE disabled and enabled
and all of them boot, while before your patch series, 3.15-rc1 fails to
boot on Armada XP with CONFIG_MACH_DOVE enabled.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists