linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: swarren@nvidia.com (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ARM: tegra: Add zreladdr etc to Makefile.boot for Tegra30
Date: Tue, 28 Feb 2012 17:03:24 -0700	[thread overview]
Message-ID: <1330473804-23348-2-git-send-email-swarren@nvidia.com> (raw)
In-Reply-To: <1330473804-23348-1-git-send-email-swarren@nvidia.com>

These previously weren't present, because they're different for Tegra20
and Tegra30, which forced one to specify LOADADDR= when building uImages
for kernels with both Tegra20 and Tegra30 support enabled.

My expectation now is that everyone will turn on CONFIG_UIMAGE_NOLOAD and
hence not be inconvenienced by having this information present.

Signed-off-by: Stephen Warren <swarren@nvidia.com>
---
This somewhat depends on the previous patch or it'll be annoying to build
multi-SoC Tegra kernels, so I guess it should get merged through the same
tree.

 arch/arm/mach-tegra/Makefile.boot |    4 ++++
 1 files changed, 4 insertions(+), 0 deletions(-)

diff --git a/arch/arm/mach-tegra/Makefile.boot b/arch/arm/mach-tegra/Makefile.boot
index 9a82094..b6101f8 100644
--- a/arch/arm/mach-tegra/Makefile.boot
+++ b/arch/arm/mach-tegra/Makefile.boot
@@ -2,6 +2,10 @@ zreladdr-$(CONFIG_ARCH_TEGRA_2x_SOC)	+= 0x00008000
 params_phys-$(CONFIG_ARCH_TEGRA_2x_SOC)	:= 0x00000100
 initrd_phys-$(CONFIG_ARCH_TEGRA_2x_SOC)	:= 0x00800000
 
+zreladdr-$(CONFIG_ARCH_TEGRA_3x_SOC)	+= 0x80008000
+params_phys-$(CONFIG_ARCH_TEGRA_3x_SOC)	:= 0x80000100
+initrd_phys-$(CONFIG_ARCH_TEGRA_3x_SOC)	:= 0x80800000
+
 dtb-$(CONFIG_MACH_HARMONY) += tegra-harmony.dtb
 dtb-$(CONFIG_MACH_PAZ00) += tegra-paz00.dtb
 dtb-$(CONFIG_MACH_SEABOARD) += tegra-seaboard.dtb
-- 
1.7.0.4

  reply	other threads:[~2012-02-29  0:03 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-29  0:03 [PATCH 1/2] ARM: Add Kconfig option to use mkimage -T kernel_noload Stephen Warren
2012-02-29  0:03 ` Stephen Warren [this message]
2012-02-29 12:29 ` Jean-Christophe PLAGNIOL-VILLARD
2012-02-29 16:58   ` Stephen Warren
2012-02-29 18:14     ` Jean-Christophe PLAGNIOL-VILLARD
2012-02-29 18:33       ` Tim Bird
2012-02-29 18:50         ` Jean-Christophe PLAGNIOL-VILLARD
2012-03-12 17:40           ` Marek Vasut
2012-03-12 17:44             ` Jean-Christophe PLAGNIOL-VILLARD
2012-02-29 19:12         ` Uwe Kleine-König
2012-02-29 19:17           ` Stephen Warren
2012-02-29 19:44             ` Uwe Kleine-König
2012-02-29 19:59               ` Stephen Warren
2012-02-29 20:12                 ` Andre Renaud
2012-02-29 20:16                   ` Stephen Warren
2012-02-29 20:19                   ` Russell King - ARM Linux
2012-02-29 20:25                     ` Andre Renaud
2012-02-29 20:29                       ` Russell King - ARM Linux
2012-02-29 20:39                       ` Uwe Kleine-König
2012-02-29 20:45                         ` Russell King - ARM Linux
2012-02-29 20:59                           ` Uwe Kleine-König
2012-03-01  4:55                             ` Jean-Christophe PLAGNIOL-VILLARD
2012-03-12 17:42                             ` Marek Vasut
2012-02-29 21:27                           ` Stephen Warren
2012-02-29 22:28                             ` Andre Renaud
2012-02-29 20:30                   ` Uwe Kleine-König
2012-02-29 23:53               ` Ryan Mallon
2012-03-12 17:44                 ` Marek Vasut
2012-03-01 15:34               ` Mark Brown
2012-03-01 17:01 ` Stephen Warren
2012-03-05  4:21   ` Olof Johansson
2012-03-05 20:29   ` Nicolas Pitre

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=1330473804-23348-2-git-send-email-swarren@nvidia.com \
    --to=swarren@nvidia.com \
    --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).