From: Arnd Bergmann <arnd@arndb.de>
To: Stephen Warren <swarren@nvidia.com>
Cc: "Russell King - ARM Linux" <linux@arm.linux.org.uk>,
Olof Johansson <olof@lixom.net>,
Peter De Schrijver <pdeschrijver@nvidia.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
"Colin Cross (ccross@android.com)" <ccross@android.com>,
Erik Gilling <konkers@android.com>
Subject: Re: [PATCH] arm/tegra: select AUTO_ZRELADDR by default
Date: Fri, 14 Oct 2011 18:27:53 +0200 [thread overview]
Message-ID: <201110141827.53906.arnd@arndb.de> (raw)
In-Reply-To: <74CDBE0F657A3D45AFBB94109FB122FF173BE1A283@HQMAIL01.nvidia.com>
On Friday 14 October 2011, Stephen Warren wrote:
> Arnd Bergmann wrote at Friday, October 14, 2011 9:30 AM:
> ...
> > You mention that tegra30 will require AUTO_ZRELADDR.
>
> Well, just to be clear, here's the situation I think:
>
> Tegra20's SDRAM starts at physical address 0.
>
> Tegra30's SDRAM starts at physical address 2G.
>
> To support that, we could either:
>
> a) Introduce a new Kconfig variable for Tegra30, make T20/T30 mutually
> exclusive, and update arch/arm/mach-tegra/Makefile.boot to set zreladdr
> etc. based on the new Tegra30 config variable too. Then, there's no need
> for AUTO_ZRELADDR anywhere.
>
> b) Have no new config variable, build a unified T20/T30 kernel, leave
> Makefile.boot untouched, and rely on using AUTO_ZRELADDR for Tegra30 to
> account for the different SDRAM physical addresses.
Ok, thanks for the explanation, that makes it much clearer. For
completeness, you could also do both of the above and make T20/T30 mutually
exclusive unless AUTO_ZRELADDR is set. That might be more complex than
necessary, I don't know.
Arnd
next prev parent reply other threads:[~2011-10-14 16:28 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-28 1:07 [PATCH] arm/tegra: select AUTO_ZRELADDR by default Peter De Schrijver
2011-09-28 17:50 ` Stephen Warren
2011-10-13 23:38 ` Olof Johansson
2011-10-14 7:15 ` Russell King - ARM Linux
2011-10-14 14:45 ` Stephen Warren
2011-10-14 15:29 ` Arnd Bergmann
2011-10-14 16:12 ` Stephen Warren
2011-10-14 16:27 ` Arnd Bergmann [this message]
2011-10-14 16:44 ` Olof Johansson
2011-10-14 18:03 ` Nicolas Pitre
2011-10-14 19:20 ` Russell King - ARM Linux
2011-10-14 20:06 ` Nicolas Pitre
2011-10-14 20:12 ` Russell King - ARM Linux
2011-10-14 20:16 ` Stephen Warren
2011-10-14 20:19 ` Russell King - ARM Linux
2011-10-15 15:29 ` Tixy
2011-10-14 20:26 ` Nicolas Pitre
2011-10-14 20:14 ` Stephen Warren
2011-10-14 20:45 ` Nicolas Pitre
2011-10-14 21:01 ` Stephen Warren
2011-10-14 21:28 ` Nicolas Pitre
2011-10-14 22:06 ` Rob Herring
2011-10-14 18:01 ` Nicolas Pitre
2011-10-14 19:20 ` Russell King - ARM Linux
2011-10-14 20:14 ` Nicolas Pitre
2011-10-14 20:17 ` Russell King - ARM Linux
2011-10-14 20:31 ` Nicolas Pitre
2011-10-14 21:13 ` Russell King - ARM Linux
2011-10-14 22:26 ` Nicolas Pitre
2011-10-14 17:53 ` Nicolas Pitre
2011-10-14 17:58 ` Olof Johansson
2011-10-14 18:00 ` Olof Johansson
2011-10-14 15:59 ` [PATCH] ARM: mutually exclude ZBOOT_ROM and AUTO_ZRELADDR Olof Johansson
2011-10-14 16:29 ` Arnd Bergmann
2011-10-14 18:07 ` Nicolas Pitre
2011-10-14 18:04 ` Nicolas Pitre
-- strict thread matches above, loose matches on Subject: below --
2011-10-03 13:06 [PATCH v6 0/3] Add support for tegra2 based ventana board Peter De Schrijver
2011-10-03 13:06 ` [PATCH] arm/tegra: select AUTO_ZRELADDR by default Peter De Schrijver
2011-10-03 13:13 ` Peter De Schrijver
2011-10-03 16:22 ` Stephen Warren
2011-10-04 8:51 ` Peter De Schrijver
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=201110141827.53906.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=ccross@android.com \
--cc=konkers@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=olof@lixom.net \
--cc=pdeschrijver@nvidia.com \
--cc=swarren@nvidia.com \
/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