> -----Original Message----- > From: Tony Lindgren [mailto:tony@xxxxxxxxxxx] > Sent: Wednesday, June 30, 2010 12:55 PM > To: Shilimkar, Santosh > Cc: linux-arm-kernel@xxxxxxxxxxxxxxxxxxx; linux-omap@xxxxxxxxxxxxxxx > Subject: Re: [PATCH 6/6] omap2/3/4: Add Kconfig option to compile in > typical omap features > > * Shilimkar, Santosh <santosh.shilimkar@xxxxxx> [100630 09:41]: > > > -----Original Message----- > > > From: Tony Lindgren [mailto:tony@xxxxxxxxxxx] > > > Sent: Wednesday, June 30, 2010 11:47 AM > > > To: Shilimkar, Santosh > > > Cc: linux-arm-kernel@xxxxxxxxxxxxxxxxxxx; linux-omap@xxxxxxxxxxxxxxx > > > Subject: Re: [PATCH 6/6] omap2/3/4: Add Kconfig option to compile in > > > typical omap features > > > > > > * Shilimkar, Santosh <santosh.shilimkar@xxxxxx> [100629 17:40]: > > > > > > > > > > > With your series OMAP4 build breaks because of PM and SMP > > > dependencies. > > > > > To ensure that build doesn't break on OMAP4, I needed below > change. > > > With > > > > > This change I tried your series and it boots OK on OMAP4430 SDP > > > > > > Hmm the build does not break for me? > > > > > Looks like I am missing something here. How do you build OMAP4 alone > with > > these new changes ?? > > Use your old config file, or just unselect CONFIG_ARCH_OMAP2 > and CONFIG_ARCH_OMAP3. Note that if you now do: > > $ yes "" | ARCH=arm make oldconfig > > with your old omap4 only config file, then by default the > typical features get added by default. So what you probably > want to do is (untested): > > $ echo "# CONFIG_ARCH_OMAP2PLUS_TYPICAL is not set" >> .config > $ yes "" | ARCH=arm make oldconfig > > Then it should not change your old config file. > The above method works Tony. The series boot tested with 4430 SDP Regards, Santosh -- 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
