1*a8c7c708SwdenkSubject: Re: [PATCH][CFT] bring ARM memory layout in line with the documented behaviour 2*a8c7c708SwdenkFrom: "Anders Larsen" <alarsen@rea.de> 3*a8c7c708SwdenkDate: Thu, 18 Sep 2003 14:15:21 +0200 4*a8c7c708SwdenkTo: Wolfgang Denk <wd@denx.de> 5*a8c7c708Swdenk 6*a8c7c708Swdenk... 7*a8c7c708Swdenk>I still see references to _armboot_start, _armboot_end_data, and 8*a8c7c708Swdenk>_armboot_end - which role do these play now? Can we get rid of them? 9*a8c7c708Swdenk> 10*a8c7c708Swdenk>How are they (should they be) set in your memory map above? 11*a8c7c708Swdenk 12*a8c7c708Swdenk_armboot_start contains the value of TEXT_BASE (0xA07E0000); it seems 13*a8c7c708SwdenkTEXT_BASE and _armboot_start are both used for the same purpose in 14*a8c7c708Swdenkdifferent parts of the (ARM) code. 15*a8c7c708SwdenkFurthermore, the startup code (cpu/<arm>/start.S) internally uses 16*a8c7c708Swdenkanother variable (_TEXT_BASE) with the same content as _armboot_start. 17*a8c7c708SwdenkI agree that this mess should be cleaned up. 18*a8c7c708Swdenk 19*a8c7c708Swdenk_armboot_end_data is the end address of the initialized data section, 20*a8c7c708Swdenkand is only used in one place (board/logodl/flash.c - the reference in 21*a8c7c708Swdenklib_arm/board.c is purely informational). 22*a8c7c708Swdenk 23*a8c7c708Swdenk_armboot_end is the end address of the BSS and is used to determine 24*a8c7c708Swdenkthe address of the VFD buffer. 25*a8c7c708Swdenk 26*a8c7c708SwdenkEliminating those should be doable, and at least the patch already 27*a8c7c708Swdenkeliminates _armboot_real_end. 28