Re: OMAP totally fucked?

[Tony Lindgren <tony@atomide.com>]

* Tony Lindgren <tony@atomide.com> [120303 11:56]:
> * Tony Lindgren <tony@atomide.com> [120303 11:29]:
> > * Russell King - ARM Linux <linux@arm.linux.org.uk> [120303 10:57]:
> > > 
> > > Even with the full config, making oldconfig I get:
> > > 
> > > OMAP2420 support (SOC_OMAP2420) [Y/n] (NEW) 
> > > OMAP2430 support (SOC_OMAP2430) [Y/n] (NEW) 
> > > OMAP3430 support (SOC_OMAP3430) [Y/n] (NEW) 
> > > TI81XX support (SOC_OMAPTI81XX) [Y/n] (NEW) 
> > > AM33XX support (SOC_OMAPAM33XX) [Y/n] (NEW) 
> > > OMAP44XX support (SOC_OMAP44XX) [Y/n] (NEW) 
> > > 
> > > May I remind you of this mail from Linus:
> > > 
> > > 	https://lkml.org/lkml/2012/1/6/354
> > > 
> > > So really this is a rather horrid mess.
> > 
> > Hmm yes. Sounds like we need to remove the defaults and instead
> > add them to omap2plus_defconfig.
> > 
> > I'll do a patch to fix that.
> 
> How about the following patch after we revert commit 72b026a4?
> 
> That still leaves the randconfig not necessarily selecting
> any of ARCH_OMAP2/3/4 issue, but that can be dealt separately
> later on.

Grr, need to look at it more.. Now it leaves out ARCH_OMAP2/3/4
when doing a make oldconfig with some existing .config file.

Regards,

Tony