upstream u-boot with additional patches for our devices/boards:
https://lists.denx.de/pipermail/u-boot/2017-March/282789.html (AXP crashes) ;
Gbit ethernet patch for some LIME2 revisions ;
with SPI flash support
You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
18 lines
760 B
18 lines
760 B
21 years ago
|
Subject: Re: [PATCH][CFT] bring ARM memory layout in line with the documented behaviour
|
||
|
|
From: "Anders Larsen" <alarsen@rea.de>
|
||
|
|
Date: Thu, 18 Sep 2003 14:15:21 +0200
|
||
|
|
To: Wolfgang Denk <wd@denx.de>
|
||
|
|
|
||
|
|
...
|
||
|
|
>I still see references to _armboot_start, _armboot_end_data, and
|
||
|
|
>_armboot_end - which role do these play now? Can we get rid of them?
|
||
|
|
>
|
||
|
|
>How are they (should they be) set in your memory map above?
|
||
|
|
|
||
|
|
_armboot_start contains the value of TEXT_BASE (0xA07E0000); it seems
|
||
|
|
TEXT_BASE and _armboot_start are both used for the same purpose in
|
||
|
|
different parts of the (ARM) code.
|
||
|
|
Furthermore, the startup code (cpu/<arm>/start.S) internally uses
|
||
|
|
another variable (_TEXT_BASE) with the same content as _armboot_start.
|
||
|
|
I agree that this mess should be cleaned up.
|