On 10/15/2014 04:42 PM, Jason Cooper wrote:
On Wed, Oct 15, 2014 at 02:53:02AM +0200, Benoit Masson wrote:
Le 6 oct. 2014 à 18:13, Sebastian Hesselbarth <sebastian.hesselbarth@xxxxxxxxx> a écrit :
I prepared more branches with the series
- on top of v3.17 release:
https://github.com/shesselba/linux-dove.git devel/mvebu-ix4_v3.17
- on top of next-20141003 (i.e. what will become v3.18-rc1):
https://github.com/shesselba/linux-dove.git devel/mvebu-ix4_next-20141003
It would be great, if you can test in this order:
- vanilla v3.17
- mvebu-ix4_v3.17
- mvebu-ix4_next-20141003
All the 3 branch works WHEN APPLYING A0 patch (below), with both my custom kernel config and the arch/arm/configs/mvebu_v7_defconfig
The reason why it didn't worked last time was that apparently the A0 patch (copied) below was not merged into 3.17 :(
This means that ix4-300d support is broken on 3.17 because of the A0 stepping patch not merged.
Do you have a link to an email thread or the patch Subject line? I can
confirm it's missing from mvebu/fixes...
http://lists.infradead.org/pipermail/linux-arm-kernel/2014-July/275487.html
But you and Andrew should check what Arnd suggested. IIRC, there
was also an appropriate follow-up patch discussion started by
Andrew.
Sebastian
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
