Re: [RFC/PATCH 0/7] ARCH: shmobile: defconfig consolidation

[Simon Horman <horms@verge.net.au>]

On Sun, Apr 07, 2013 at 06:07:16PM -0700, Kuninori Morimoto wrote:
> 
> Hi Simon
> 
> > Simon Horman (7):
> >  ARM: shmobile: prune defconfig
> >  ARM: shmobile: make defconfig canonical
> >  ARM: shmobile: Add kzm9d to consolidated defconfig
> >  ARM: shmobile: Add mackerel to consolidated defconfig
> >  ARM: shmobile: defconfig: Remove armadillo800eva defconfig
> >  ARM: shmobile: defconfig: Remove kzm9d defconfig
> >  ARM: shmobile: defconfig: Remove mackerel defconfig
> (snip)
> > Morimoto-san, I suspect it may be possible to add support for the
> > bockw board to the consolidated defconfig if its boot loader supports
> > booting using a zImage. In this case even though the base memory address
> > is not the same as the boards above it should be possible to specify
> > the base address from the boot loader. As I do not have a bockw board
> > I am wondering if you could investigate this.
> 
> I tested shmobile_defconfig on Bock-W board.
> It works with...
> 
>  1) I added R8A7778 SoC on .config
>  2) I added Bock-W on .config
>  3) I fixuped CONFIG_MEMORY_START, CONFIG_MEMORY_SIZE value on .config
> 
> It is correct method ?

Unfortunately not, the idea is not to modify CONFIG_MEMORY_START
or CONFIG_MEMORY_SIZE.

My understanding is that if you load a zImage at the correct
start address (0x60000000 IIRC) and then execute it using bootz
then the kernel should relocate and run from that address.