Hi, Sorry for the delay in replying.. * Michael Jones <michael.jones@xxxxxxxxxxxxxxxx> [110811 07:34]: > > I still stumbled upon these linker errors when building for my OMAP3 > board, using the current linux-omap master branch. I inadvertently had > CONFIG_ARCH_OMAP4=y (leftover from my starting point, > omap2plus_defconfig), but didn't have any of the boards with > omap_phy_internal.o selected (OMAP_4430SDP, OMAP4_PANDA, PCM049, PCM049, > OMAP3517EVM). Maybe this isn't a concern anyway, since anybody building > with CONFIG_ARCH_OMAP4 will presumably also be building one of those > boards? I don't know if it is our goal to build successfully with every > wacky CONFIG_ combination, but I thought I would report it here just in > case. Probably the best way is to get omap specific randconfigs going based on something what Arnd posted few days ago. Even with the old defconfig files we'll still be missing many corner cases. 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
