* Jan Luebbe <jlu@xxxxxxxxxxxxxx> [120807 09:30]: > When only ARCH_OMAP3 (or -2,-4,...) and SOC_AM33XX are selected, multi.h > doesn't set MULTI_OMAP2. In this case, cpu.h will simply define > cpu_is_omap24xx() as 1. > > This causes problems for example for omap_hwmod.c:omap_hwmod_init which > checks for cpu_is_omap24xx() first, using the wrong soc_ops for AM33xx. > > Fix this by defining MULTI_OMAP2 when using SOC_AM33XX together with > something else. Thanks applying into fixes. Tony -- 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
