On Wed, Feb 06, 2013 at 01:22:31PM +0200, Felipe Balbi wrote: > there's a little more to it. When running allmodconfig, > CONFIG_ARCH_MULTIPLATFORM is set but none of the other ARCHes > (ARCH_OMAP, ARCH_AT91, ARCH_VERSATILE, etc) are set, so it turned out > that the driver wasn't even included on my build test. > > Russell, is this expected (the MULTIPLATFORM thing) ? Just so I fix my > build test scripts to use another defconfig instead of allmod and > allyes. Don't know. Most of that logic is sitting in arm-soc. Nothing obvious stands out as to why that's happening. The first thing to check is which of the CONFIG_ARCH_MULTI_* options are set. It should be ARCH_MULTI_V7 and ARCH_MULTI_V6_V7. This should then allow ARCH_OMAP2PLUS to be set. However, I've said this before, and I'll say it again: if you want to use the all* targets, it's better to seed the configuration so that you end up with the platform you're targetting selected. I've always done this with the build system, and even before it when I've wanted to use the all* targets, because generally I want that behaviour, but I want it for a particular platform. -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
