* Russell King - ARM Linux <linux@xxxxxxxxxxxxxxxx> [120208 14:39]: > On Wed, Feb 08, 2012 at 11:55:30AM -0800, Tony Lindgren wrote: > > * Russell King - ARM Linux <linux@xxxxxxxxxxxxxxxx> [120208 01:15]: > > > On Tue, Feb 07, 2012 at 04:08:23PM -0800, Kevin Hilman wrote: > > > > Víctor M. Jáquez L. <vjaquez@xxxxxxxxxx> writes: > > > > > If it helps, I observed the same issue in a beagleboard rev B6, with > > > > > v3.3-rc2 > > > > > > > > Great, thanks. Can you share your ~/.config? > > > > > > If it helps, ARM Kautobuild V2 is up and running (assuming I don't break > > > the scripts again) at: > > > > > > http://www.arm.linux.org.uk/developer/build/ > > > > > > from where the build configs I use (and the exact ones used in those > > > compiles) are available. These aren't configs in arch/arm/configs. > > > > Great. How do you generate the allnoconfig there? > > > > I tried: > > > > ARCH=arm make KCONFIG_ALLCONFIG=my_config allnoconfig > > > > But it really does a total ARM noconfig that currently has no chance > > in building currently? > > Each of the builds have a seed configuration, even allnoconfig. > > The seed configuration for the oldconfig's are a 'make savedefconfig' > version of the build config I've been using. > > For the allnoconfig, there's a minimal set of configuration symbols > to set - mainly to set the target platform but with CONFIG_MMU=y. > > So, for the LDP, it's: > > CONFIG_MMU=y > CONFIG_ARCH_OMAP=y > CONFIG_ARCH_OMAP2PLUS=y > CONFIG_ARCH_OMAP3=y > CONFIG_SOC_OMAP3430=y > CONFIG_MACH_OMAP_LDP=y > > and 4430SDP: > > CONFIG_MMU=y > CONFIG_ARCH_OMAP=y > CONFIG_ARCH_OMAP2PLUS=y > CONFIG_ARCH_OMAP4=y > CONFIG_MACH_OMAP_4430SDP=y OK thanks, so no KCONFIG_ALLCONFIG type magic there. 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
