All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 2/2] ARM: shmobile: bockw: enable boot from shmobile_defconfig
Date: Tue, 09 Apr 2013 12:19:51 +0000	[thread overview]
Message-ID: <20130409121950.GC15412@verge.net.au> (raw)
In-Reply-To: <1365131070-13142-3-git-send-email-horms+renesas@verge.net.au>

On Tue, Apr 09, 2013 at 02:37:27AM -0700, Kuninori Morimoto wrote:
> To enable boot from shmobile_defconfig on Bock-W,
> it needs
>  - memory started from 0x40000000
>  - enable R8A7778
>  - enable Bock-W board
>  - enable TMU

I was expecting that the bockw needed to be started at 0x600000000.
Are there any side-effects of using 0x400000000?

If not, then I guess I am happy with this.
But could you split it into two patches?


> 
> Signed-off-by: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
> ---
>  arch/arm/boot/dts/r8a7778-bockw.dts |    2 +-
>  arch/arm/configs/shmobile_defconfig |    3 ++-
>  2 files changed, 3 insertions(+), 2 deletions(-)
> 
> diff --git a/arch/arm/boot/dts/r8a7778-bockw.dts b/arch/arm/boot/dts/r8a7778-bockw.dts
> index 0076b1e..1242940 100644
> --- a/arch/arm/boot/dts/r8a7778-bockw.dts
> +++ b/arch/arm/boot/dts/r8a7778-bockw.dts
> @@ -27,6 +27,6 @@
>  
>  	memory {
>  		device_type = "memory";
> -		reg = <0x60000000 0x10000000>;
> +		reg = <0x40000000 0x10000000>;
>  	};
>  };
> diff --git a/arch/arm/configs/shmobile_defconfig b/arch/arm/configs/shmobile_defconfig
> index 7dba53f..c1fdff9 100644
> --- a/arch/arm/configs/shmobile_defconfig
> +++ b/arch/arm/configs/shmobile_defconfig
> @@ -14,13 +14,14 @@ CONFIG_SLAB=y
>  CONFIG_ARCH_SHMOBILE=y
>  CONFIG_ARCH_SH7372=y
>  CONFIG_ARCH_R8A7740=y
> +CONFIG_ARCH_R8A7778=y
>  CONFIG_ARCH_R8A7790=y
>  CONFIG_ARCH_EMEV2=y
>  CONFIG_MACH_MACKEREL=y
>  CONFIG_MACH_ARMADILLO800EVA=y
> +CONFIG_MACH_BOCKW=y
>  CONFIG_MACH_LAGER=y
>  CONFIG_MACH_KZM9D=y
> -# CONFIG_SH_TIMER_TMU is not set
>  # CONFIG_SWP_EMULATE is not set
>  CONFIG_ARM_ERRATA_430973=y
>  CONFIG_ARM_ERRATA_458693=y
> -- 
> 1.7.9.5
> 

  parent reply	other threads:[~2013-04-09 12:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-05  3:04 [GIT PULL] Renesas ARM-based SoC bockw board updates for v3.10 Simon Horman
2013-04-05  3:04 ` Simon Horman
2013-04-05  3:04 ` [PATCH 1/2] ARM: shmobile: bockw: add SMSC ethernet support Simon Horman
2013-04-05  3:04   ` Simon Horman
2013-04-05  3:04 ` [PATCH 2/2] ARM: shmobile: bockw: enable network settings on bootargs Simon Horman
2013-04-05  3:04   ` Simon Horman
2013-04-09  9:37   ` [PATCH 2/2] ARM: shmobile: bockw: enable boot from shmobile_defconfig Kuninori Morimoto
2013-04-09 12:19   ` Simon Horman [this message]
2013-04-10  1:57   ` Kuninori Morimoto
2013-04-10  2:15   ` Simon Horman
2013-04-10  5:27   ` Kuninori Morimoto
2013-04-09 12:53 ` [GIT PULL] Renesas ARM-based SoC bockw board updates for v3.10 Arnd Bergmann
2013-04-09 12:53   ` Arnd Bergmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130409121950.GC15412@verge.net.au \
    --to=horms@verge.net.au \
    --cc=linux-sh@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.