blob: 1b120ac3e1a372c92e7ef6b73fb00f710dc7dfcd [file] [log] [blame]
wdenkc0aa5c52003-12-06 19:49:23 +00001Subject: Re: [PATCH][CFT] bring ARM memory layout in line with the documented behaviour
2From: "Anders Larsen" <alarsen@rea.de>
3Date: Thu, 18 Sep 2003 14:15:21 +0200
4To: Wolfgang Denk <wd@denx.de>
5
6...
7>I still see references to _armboot_start, _armboot_end_data, and
8>_armboot_end - which role do these play now? Can we get rid of them?
9>
10>How are they (should they be) set in your memory map above?
11
Wolfgang Denk0708bc62010-10-07 21:51:12 +020012_armboot_start contains the value of CONFIG_SYS_TEXT_BASE (0xA07E0000); it seems
13CONFIG_SYS_TEXT_BASE and _armboot_start are both used for the same purpose in
wdenkc0aa5c52003-12-06 19:49:23 +000014different parts of the (ARM) code.
15Furthermore, the startup code (cpu/<arm>/start.S) internally uses
16another variable (_TEXT_BASE) with the same content as _armboot_start.
17I agree that this mess should be cleaned up.