On Monday 08 July 2013, Jonas Jensen wrote:
> Arnd suggested removing one (or many) of the options:
>
> CPU_ABRT_EV4T
> CPU_CACHE_V4WT
> CPU_COPY_V4WB
> CPU_TLB_V4WBI
>
> However boot is still broken after removing all including CPU_32v4T.
>
> Selecting CPU_SA1100 instead, it boots normally and init works.
>
> The idea is, If you can help figure out what exactly breaks boot, the
> patch can be dropped.
>
> From these tests, I have created two branches ( arch/arm/mm have
> replacements for calls to no longer compiled in ):
>
> http://code.google.com/p/linux-next-20130703-moxart/source/detail?r=a88f33ad22d3f9a31fe126f1c95568e5b2e8f32d&name=multi_V4_test_arm920t
> http://code.google.com/p/linux-next-20130703-moxart/source/detail?r=9f4c21f1123a122c51792cd374217ce6e426e74a&name=multi_V4_test_sa1100
It looks like you select CPU_ARM926T but change the entry for CPU_ARM920T
instead, which would have no effect then.
Arnd
_______________________________________________
devicetree-discuss mailing list
devicetree-discuss@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/devicetree-discuss
