| wdenk | a8c7c70 | 2003-12-06 19:49:23 +0000 | [diff] [blame] | 1 | Subject: Re: [PATCH][CFT] bring ARM memory layout in line with the documented behaviour |
| 2 | From: "Anders Larsen" <alarsen@rea.de> |
| 3 | Date: Thu, 18 Sep 2003 14:15:21 +0200 |
| 4 | To: 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 Denk | 14d0a02 | 2010-10-07 21:51:12 +0200 | [diff] [blame] | 12 | _armboot_start contains the value of CONFIG_SYS_TEXT_BASE (0xA07E0000); it seems |
| 13 | CONFIG_SYS_TEXT_BASE and _armboot_start are both used for the same purpose in |
| wdenk | a8c7c70 | 2003-12-06 19:49:23 +0000 | [diff] [blame] | 14 | different parts of the (ARM) code. |
| 15 | Furthermore, the startup code (cpu/<arm>/start.S) internally uses |
| 16 | another variable (_TEXT_BASE) with the same content as _armboot_start. |
| 17 | I agree that this mess should be cleaned up. |