* Tony Lindgren <tony@xxxxxxxxxxx> [120510 11:06]: > * Tony Lindgren <tony@xxxxxxxxxxx> [120509 11:58]: > > * Vaibhav Hiremath <hvaibhav@xxxxxx> [120509 04:28]: > > > Initially, we decided to make am33xx family of device to fall > > > under omap3 class (cpu_is_omap34xx() = true), since it carries > > > Cortex-A8 core. But while adding complete baseport support > > > (like, clock, power and hwmod) support, it is observed that, > > > we are creating more and more problems by treating am33xx device > > > as omap3 family, as nothing matches between them > > > (except cortex-A8 mpu). > > > > Thanks applying into devel-soc after updating for soc_is change > > and fixing typo in the description that stil said OMAPAM. Updated > > patch below. > > Turns out we still need to add defined(CONFIG_SOC_AM33XX) around > __omap2_set_globals() to keep compile working when omap4 + am33xx > are selected without omap2 or 3. Also removed the "default y" > for am33xx as that's where we're heading to anyways. > > Updated patch below. Argh, now it breaks with: arch/arm/mach-omap2/built-in.o: In function `omap2_set_globals_am33xx': twl-common.c:(.init.text+0x1dd8): undefined reference to `omap2_set_globals_sdrc' There are clearly some dependencies to the clean up patches being discussed.. So I'll drop this for now until the clean up is sorted out. Regards, 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
