Re: 3.8 -> 3.9-rc1 upgrade: old configs broken

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



* Aaro Koskinen <aaro.koskinen@xxxxxx> [130304 15:26]:
> Hi,
> 
> How should I upgrade my .config files when upgrading to 3.9-rc1?
> 
> So far I have been doing it like this:
> 
> 	cp <old config from previous kernel release> .config
> 	make ARCH=arm oldnoconfig
> 	<compile>
> 
> But now I see that none of my boards boot up... Except OMAP1 (well, after
> fixing the build issues). I believe this is because ARCH_MULTIPLATFORM
> changes. I can always redo my configs with menuconfig, it's a PITA job...
> 
> So I guess .config files are not supposed to be upwards compatible?

Well in this case you need to update your config files by adding
the following manually to your .config:

CONFIG_ARCH_MULTIPLATFORM=y
CONFIG_ARCH_MULTI_V7=y
CONFIG_ARCH_OMAP2PLUS=y

And maybe also:

CONFIG_ARCH_MULTI_V6=y

That's because after the multiplatform Kconfig changes we cannot
select omap2+ automatically as that would not be nice for the
other arm architectures.

Then if using uImage, you need to define LOADADDR in the
environment when building. Or run mkimage manually.

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


[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux