diff options
| author | Timothy Pearson <tpearson@raptorengineering.com> | 2019-05-11 15:12:49 -0500 |
|---|---|---|
| committer | Timothy Pearson <tpearson@raptorengineering.com> | 2019-05-11 15:12:49 -0500 |
| commit | 9e80202352dd49bdd9e67b8b906d86f058431505 (patch) | |
| tree | 5673c17aad6e3833da8c4ff21b5a11f666ec9fbe /src/roms/u-boot/doc/README.ARM-memory-map | |
| download | hqemu-master.zip hqemu-master.tar.gz | |
Diffstat (limited to 'src/roms/u-boot/doc/README.ARM-memory-map')
| -rw-r--r-- | src/roms/u-boot/doc/README.ARM-memory-map | 17 |
1 files changed, 17 insertions, 0 deletions
diff --git a/src/roms/u-boot/doc/README.ARM-memory-map b/src/roms/u-boot/doc/README.ARM-memory-map new file mode 100644 index 0000000..1b120ac --- /dev/null +++ b/src/roms/u-boot/doc/README.ARM-memory-map @@ -0,0 +1,17 @@ +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 CONFIG_SYS_TEXT_BASE (0xA07E0000); it seems +CONFIG_SYS_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. |
