* Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx> [100603 07:25]: > > > On Thu, 3 Jun 2010, Michael Ellerman wrote: > > > > You can sort of do that today, by just storing a delta, but oldconfig > > will silently turn off things you have enabled if prereqs change, so > > that doesn't really work I think. > > I think you can do it today with various hacks. Up to and including > basically doing something that just selects the options you want. > > IOW, you could likely have a human-written Kconfig.<platform> file that > just does > > define_bool MYPLATFORM y > select .. everything I need .. > > include Kconfig.main > > or a number of other tricks. I agree all the defconfigs are a pain just for the omaps alone. If this is of any help we could now just keep omap3_defconfig for arch/arm/mach-omap2 and get rid of 23 config files: $ egrep "CONFIG_ARCH_OMAP[2|3|4]=y" arch/arm/configs/* | grep -v omap3_defconfig | wc -l 23 It needs some more work for omap2 though to boot to userspace as there are still some known issues with ARMv6 vs ARMv7 support and VFP2 vs 3 support. Will try to look at fixing those again when I have a chance. Then making the multi-omap thing work on all omap1 boards would cut down another 15 defconfigs, that should be also doable. To be able to compile in multiple arm architectures we would have to get rid of the Makefile.boot files and NR_IRQS and then have some kind of common clock framework at least. I did some experiments compiling in both mach-omap1 and mach-omap2 a few years back using ARMv5 flags, there were probably other issues too like some conflicting defines. Cheers, Tony -- To unsubscribe from this list: send the line "unsubscribe linux-arm-msm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
