On 2015-04-06 10:54, Russell King - ARM Linux wrote: > On Mon, Apr 06, 2015 at 10:38:10AM +0200, Stefan Agner wrote: >> We already prevent a kernel image which mixes V4/V4T/V5 and V6/V7. And >> so we would do with V7M too. Just because it's in multiplatform doesn't >> mean we need to mix things up. > > I don't think you're getting what I'm saying at all... :( It's not that I don't get it. I'm just arguing against it. IMHO, it's wrong to create a parallel universe for v7M multiplatform... Multiplatform as I understand it is mainly about selecting multiple SoC _platforms_ but not necessarily multiple CPU platforms. It happens to work well for V6/V7, but does not for others, and preventing multiselection for incompatible CPU platforms is the way to prevent creating such images. > Please read the first bit of my replies again, where I say that we do > _not_ want to remove the !MMU dependency from multiplatform. This is > something I feel _very_ strongly about, and something which I've written > about many times on this list. Ok, I don't have such a strong feel for multiplatform, it just feels a bit better to me. I need a top level ARCH which is able to live with !MMU. Will try the ARCH_SINGLE_ARMV7M approach then. -- Stefan -- 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
