[ adding linux-kbuild for their input ] On Thu, 21 Jun 2018, Geert Uytterhoeven wrote: > I'm afraid adding (duplicating) machine entries for nommu support is not a > sustainable solutions. Any machine can run a nommu kernel, in theory. > > I'm aware of the objection "but you cannot build a nommu kernel that can > boot on multiple systems". That's true (unless RAM/FLASH addresses are the > same). So don't do that. > > All of the above is true for XIP, too, hence applies with s/nommu/XIP/. > One more reason not to have this duplication. > > The current "ARM multiplatform" has actually two meanings: > 1. It groups platforms that follow the "ARM multiplatform" framework, > 2. It allows to build a single kernel that can be booted on multiple > platforms. > To avoid the duplication, I think 2 should be relaxed when specialized > options like XIP or NOMMU are selected. > > I've just sent a patch to do that. Your patch isn't wrong per se. But it is not enough. The issue here would be easily fixed with some kconfig extension so that: - If XIP or NOMMU is selected then only one target in the multiplatform set can be selected, basically turning it into a choice menu. - If more than one multiplatform targets is selected then XIP and NOMMU can no longere be selected. I don't know how this could be expressed but the implementation might not be that hard. Nicolas -- To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
