> * Aaro Koskinen <aaro.koskinen@iki.fi> [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.
Hi,

I run into same problem, 3.9-rc1 builds fail to boot on mu panda
have all the things mentioned above in my .config

i tried building uImage as
make ... MACHINE=arch/arm/mach-omap2 uImage
as well as maually
mkimage -A arm -O linux -T kernel -C none -a 0x80008000 -e 0x80008000 -n "Linux 3.9-rc1-wl" -d
kernel-source/arch/arm/boot/zImage uImage

but the result is the same - failure to boot
here is output of mkimage -l
Image Name:   Linux 3.9-rc1-wl
Created:      Wed Mar  6 16:57:11 2013
Image Type:   ARM Linux Kernel Image (uncompressed)
Data Size:    4242000 Bytes = 4142.58 kB = 4.05 MB
Load Address: 80008000
Entry Point:  80008000

my .config attached

also found this thread
http://marc.info/?l=linux-omap&m=135959698420416&w=2
and tried forcing CONFIG_ARCH_VEXPRESS=n
by fiddling with arch/arm/Kconfig
but no luck as well

would appreciate any hints
Piotr