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