1a8c7c708SwdenkSubject: Re: [PATCH][CFT] bring ARM memory layout in line with the documented behaviour 2a8c7c708SwdenkFrom: "Anders Larsen" <alarsen@rea.de> 3a8c7c708SwdenkDate: Thu, 18 Sep 2003 14:15:21 +0200 4a8c7c708SwdenkTo: Wolfgang Denk <wd@denx.de> 5a8c7c708Swdenk 6a8c7c708Swdenk... 7a8c7c708Swdenk>I still see references to _armboot_start, _armboot_end_data, and 8a8c7c708Swdenk>_armboot_end - which role do these play now? Can we get rid of them? 9a8c7c708Swdenk> 10a8c7c708Swdenk>How are they (should they be) set in your memory map above? 11a8c7c708Swdenk 12*14d0a02aSWolfgang Denk_armboot_start contains the value of CONFIG_SYS_TEXT_BASE (0xA07E0000); it seems 13*14d0a02aSWolfgang DenkCONFIG_SYS_TEXT_BASE and _armboot_start are both used for the same purpose in 14a8c7c708Swdenkdifferent parts of the (ARM) code. 15a8c7c708SwdenkFurthermore, the startup code (cpu/<arm>/start.S) internally uses 16a8c7c708Swdenkanother variable (_TEXT_BASE) with the same content as _armboot_start. 17a8c7c708SwdenkI agree that this mess should be cleaned up. 18