Files
u-boot-tk1-som/include/configs
Stephen Warren 48cfca240d ARM: tegra: CONFIG_{SYS_, }LOAD{_, }ADDR rationalization
As best I can tell, CONFIG_SYS_LOAD_ADDR and CONFIG_LOADADDR/$loadaddr
serve essentially the same purpose. Roughly, if a command takes a load
address, then CONFIG_SYS_LOAD_ADDR or $loadaddr (or both) are the default
if the command-line does not specify the address. Different U-Boot
commands are inconsistent re: which of the two default values they use.
As such, set the two to the same value, and move the logic that does this
 into tegra-common-post.h so it's not duplicated. A number of other non-
Tegra boards do this too.

The values chosen for these macros are no longer consistent with anything
in MEM_LAYOUT_ENV_SETTINGS. Regain consistency by setting $kernel_addr_r
to CONFIG_LOADADDR. Older scripts tend to use $loadaddr for the default
kernel load address, whereas newer scripts and features tend to use
$kernel_addr_r, along with other variables for other purposes such as
DTBs and initrds. Hence, it's logical they should share the same value.

I had originally thought to make the $kernel_addr_r and CONFIG_LOADADDR
have different values. This would guarantee no interference if a script
used the two variables for different purposes. However, that scenario is
unlikely given the semantic meaning associated with the two variables.
The lowest available value is 0x90200000; see comments for
MEM_LAYOUT_ENV_SETTINGS in tegra30-common-post.h for details. However,
that value would be problematic for a script that loaded a raw zImage to
$loadaddr, since it's more than 128MB beyond the start of SDRAM, which
would interfere with the kernel's CONFIG_AUTO_ZRELADDR. So, let's not do
that.

The only potential fallout I could foresee from this patch is if someone
has a script that loads the kernel to $loadaddr, but some other file
(DTB, initrd) to a hard-coded address that the new value of $loadaddr
interferes with. This seems unlikely. A user should not do that; they
should either hard-code all load addresses, or use U-Boot-supplied
variables for all load addresses. Equally, any fallout due to this change
is trivial to fix; simply modify the load addresses in that script.

Cc: Paul Walmsley <pwalmsley@nvidia.com>
Signed-off-by: Stephen Warren <swarren@nvidia.com>
Reviewed-by: Paul Walmsley <pwalmsley@nvidia.com>
Reviewed-by: Simon Glass
Signed-off-by: Tom Warren <twarren@nvidia.com>
2015-05-13 09:24:12 -07:00
..
2015-02-25 13:13:38 +09:00
2015-05-10 09:59:38 -04:00
2014-11-20 11:28:25 -05:00
2014-10-27 14:35:54 +01:00
2015-02-17 22:52:39 +01:00
2015-02-17 22:54:41 +01:00
2015-03-05 20:13:21 -05:00
2014-11-20 11:28:24 -05:00
2013-10-17 09:44:20 +02:00
2015-01-05 15:13:47 -05:00
2015-01-13 09:37:26 -05:00
2014-11-20 11:28:25 -05:00
2015-04-23 13:59:19 -04:00
2014-05-13 19:43:01 -04:00
2014-11-20 11:28:25 -05:00
2014-11-20 11:28:25 -05:00
2015-04-23 08:55:53 -07:00
2015-02-25 13:13:46 +09:00
2015-03-05 22:08:59 +01:00
2014-11-19 08:48:42 +01:00
2014-11-20 11:28:24 -05:00
2015-02-25 13:13:49 +09:00
2015-05-10 09:59:38 -04:00
2015-05-10 09:59:38 -04:00
2015-02-17 22:52:39 +01:00
2014-10-10 09:44:44 -04:00
2015-02-24 17:13:36 -05:00
2015-03-13 13:13:48 +01:00
2014-11-20 11:28:25 -05:00
2015-05-10 09:59:38 -04:00
2015-05-13 09:24:12 -07:00
2014-10-27 17:54:13 -04:00
2014-10-27 17:54:13 -04:00
2014-10-27 17:54:13 -04:00
2014-10-27 17:54:13 -04:00
2014-10-27 17:54:13 -04:00
2014-10-27 17:54:13 -04:00
2015-01-05 15:13:45 -05:00
2014-12-05 08:06:10 -08:00
2014-10-10 09:44:44 -04:00
2014-10-10 09:44:44 -04:00
2015-01-13 09:37:27 -05:00
2015-01-13 09:37:27 -05:00
2015-01-13 09:37:27 -05:00
2014-10-27 17:54:13 -04:00
2014-11-20 11:28:25 -05:00
2014-11-20 11:28:25 -05:00
2014-11-17 13:16:20 +09:00
2014-11-17 13:16:20 +09:00
2014-11-17 13:16:20 +09:00
2015-02-25 14:20:10 +09:00
2014-11-07 16:32:02 +01:00
2014-11-20 11:28:25 -05:00
2014-02-06 04:48:15 +01:00
2015-04-29 11:19:04 +02:00
2015-02-24 17:13:57 -05:00