linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL] Renesas ARM-based SoC defconfig for v3.8
Date: Mon, 22 Oct 2012 14:12:19 +0000	[thread overview]
Message-ID: <201210221412.19486.arnd@arndb.de> (raw)
In-Reply-To: <20121022015126.GA10587@verge.net.au>

(adding Nico, who did a lot of the work to get rid of PLAT_PHYS_OFFSET)

On Monday 22 October 2012, Simon Horman wrote:
> On Mon, Oct 22, 2012 at 09:33:51AM +0900, Simon Horman wrote:
> > On Fri, Oct 19, 2012 at 08:18:50AM +0000, Arnd Bergmann wrote:
> > > On Friday 19 October 2012, Simon Horman wrote:
> > > > * A more significant problem seems to be the use of CONFIG_MEMORY_START
> > > >   to define PLAT_PHYS_OFFSET in arch/arm/mach-shmobile/include/mach/memory.h
> > > > 
> > > >   I'm not sure that I see an easy way to get around this one.
> > > 
> > > ARM_PATCH_PHYS_VIRT should take care of this, have you tried it?
> 
> I believe that this leaves mach-shmobile with three areas
> where CONFIG_MEMORY_START/PLAT_PHYS_OFFSET is used.

Hmm, I just noticed that in fact shmobile is the only remaining
platform that uses CONFIG_MEMORY_START with a per-board or per-soc
setting.

> * arch/arm/mach-shmobile/headsmp.S
> 
>   This uses PLAT_PHYS_OFFSET.
> 
>   I believe this can be replaced with a run-time calculation. Though I
>   haven't thought about the details yet.
> 
> * arch/arm/boot/compressed/head-shmobile.S
> 
>   This makes use of CONFIG_MEMORY_START.
> 
>   This is only used if CONFIG_ZBOOT_ROM is set.
> 
>   I'm unsure if this can be replaced with a run-time calculation or not.
>   But regardless it is only used if CONFIG_ZBOOT_ROM is set, which is not
>   the default at this time.

Right, you can probably make CONFIG_ZBOOT_ROM_MMCIF and
CONFIG_ZBOOT_ROM_SH_MOBILE_SDHI depend on !ARM_PATCH_PHYS_VIRT

> * arch/arm/mach-shmobile/Makefile.boot
> 
>  This makes use of CONFIG_MEMORY_START to set zreladdr.
> 
>  I believe that the solution to this is to make use of CONFIG_AUTO_ZRELADDR.
>  However, it is not yet clear to me how that can be used in conjunction
>  with a uImage.  As I understand it the boot loader on many of our boards,
>  including the Marzen board which is my first target for this work, boot
>  uImage imagess.

If this doesn't work, we probably also need to find a solution to
build multiple uImage files from the same vmlinux when building a
multiplatform kernel.

	Arnd

  reply	other threads:[~2012-10-22 14:12 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-17  4:38 [GIT PULL] Renesas ARM-based SoC defconfig for v3.8 Simon Horman
2012-10-17  4:38 ` [PATCH 1/2] ARM: shmobile: mackerel: defconfig update Simon Horman
2012-10-17  4:38 ` [PATCH 2/2] ARM: shmobile: armadillo800eva: enable L2X0 cache on defconfig Simon Horman
2012-10-17 13:42 ` [GIT PULL] Renesas ARM-based SoC defconfig for v3.8 Arnd Bergmann
2012-10-18  0:58   ` Simon Horman
2012-10-18  7:29     ` Arnd Bergmann
2012-10-18  8:13       ` Simon Horman
2012-10-19  3:09         ` Simon Horman
2012-10-19  8:18           ` Arnd Bergmann
2012-10-22  0:33             ` Simon Horman
2012-10-22  1:51               ` Simon Horman
2012-10-22 14:12                 ` Arnd Bergmann [this message]
2012-10-22 18:20                   ` Nicolas Pitre
2012-10-30  7:45                     ` Simon Horman
2012-10-30 21:41                       ` Arnd Bergmann
2012-11-01  0:46                         ` Simon Horman
2013-01-10  1:23 ` [GIT PULL] Renesas ARM-based SoC defconfig for v3.9 Simon Horman
2013-01-10  1:23   ` [PATCH 1/5] ARM: mach-shmobile: mackerel: update defconfig Simon Horman
2013-01-10 23:11     ` Olof Johansson
2013-01-11  0:36       ` Simon Horman
2013-01-10  1:23   ` [PATCH 2/5] ARM: shmobile: fix memory size for kota2_defconfig Simon Horman
2013-01-10  1:23   ` [PATCH 3/5] ARM: mach-shmobile: kzm9g: use voltage regulators by default Simon Horman
2013-01-10  1:23   ` [PATCH 4/5] ARM: mach-shmobile: armadillo: update defconfig Simon Horman
2013-01-10  1:23   ` [PATCH 5/5] ARM: mach-shmobile: kzm9g: Enable ARM_APPENDED_DTB in defconfig Simon Horman
2013-01-16  6:37   ` [GIT PULL] Renesas ARM-based SoC v3.9 Simon Horman
2013-01-16 23:43     ` Olof Johansson
2013-01-21 15:31       ` Laurent Pinchart
2013-01-22  8:21         ` Olof Johansson
2013-01-22  9:19           ` Paul Mundt
2013-01-24  3:35             ` Olof Johansson
2013-01-21  0:32     ` Simon Horman
2013-01-21  2:17       ` Olof Johansson
2013-01-25  2:02 ` [GIT PULL] Renesas ARM-based SoC defconfig for v3.9 #2 Simon Horman
2013-01-25  2:02   ` [PATCH 1/2] ARM: mach-shmobile: armadillo: defconfig: Enable CEU Simon Horman
2013-01-25  2:02   ` [PATCH 2/2] ARM: mach-shmobile: mackerel: enable VFP in defconfig Simon Horman
2013-01-29 17:01   ` [GIT PULL] Renesas ARM-based SoC defconfig for v3.9 #2 Olof Johansson
2013-03-18 11:53 ` [GIT PULL] Renesas ARM-based SoC defconfig updates for v3.10 Simon Horman
2013-03-18 11:53   ` [PATCH 1/9] ARM: mach-shmobile: mackerel: enable MMCIF and SDHI in defconfig Simon Horman
2013-03-18 11:53   ` [PATCH 2/9] ARM: mach-shmobile: mackerel: enable REGULATOR " Simon Horman
2013-03-18 11:53   ` [PATCH 3/9] ARM: mach-shmobile: armadillo800eva: " Simon Horman
2013-03-18 11:53   ` [PATCH 4/9] ARM: shmobile: kzm9g: defconfig: do not enable PREEMPT Simon Horman
2013-03-18 11:53   ` [PATCH 5/9] ARM: shmobile: armadillo800eva: enable branch prediction on defconfig Simon Horman
2013-03-18 11:53   ` [PATCH 6/9] ARM: shmobile: armadillo800eva: enable NEON " Simon Horman
2013-03-18 11:53   ` [PATCH 7/9] ARM: mach-shmobile: kzm9g: do not enable REGULATOR_DUMMY in defconfig Simon Horman
2013-03-18 11:53   ` [PATCH 8/9] ARM: shmobile: armadillo800eva: enable all errata for cache on defconfig Simon Horman
2013-03-18 11:53   ` [PATCH 9/9] ARM: mach-shmobile: marzen: add SATA support Simon Horman
2013-03-21 16:56   ` [GIT PULL] Renesas ARM-based SoC defconfig updates for v3.10 Arnd Bergmann
2013-03-22  0:46     ` Simon Horman

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=201210221412.19486.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).