Hi Sascha, On 19.07.2012 15:10, Sascha Hauer wrote:
Hi Jürgen, On Wed, Jul 18, 2012 at 02:58:46PM +0200, Juergen Kilb wrote:Signed-off-by: Juergen Kilb <J.Kilb@xxxxxxxxx> --- arch/arm/boards/phycard-a-l1/pca-a-l1.c | 2 ++ arch/arm/mach-omap/include/mach/omap3-silicon.h | 1 + 2 files changed, 3 insertions(+), 0 deletions(-) diff --git a/arch/arm/boards/phycard-a-l1/pca-a-l1.c b/arch/arm/boards/phycard-a-l1/pca-a-l1.c index 1cc2815..8fae405 100644 --- a/arch/arm/boards/phycard-a-l1/pca-a-l1.c +++ b/arch/arm/boards/phycard-a-l1/pca-a-l1.c @@ -292,6 +292,8 @@ static int pcaal1_mem_init(void) */ gpmc_generic_init(0x10); #endif + add_mem_device("sram0", OMAP_SRAM_BASE, 60 * SZ_1K, + IORESOURCE_MEM_WRITEABLE);Isn't this 64K? Or does the ROM code store stuff in the upper 4k which you want to preserve?
Yes it is a 64K memory range but it is splitted into 5 regions and they are used during the booting process. 0x4020_0000 - 0x4020_EFFF => Used for storing a downloaded booting image 0x4020_F000 - 0x4020_FCAF => Public Stack (reserved for stacks) 0x4020_FCB0 - 0x4020_FFC7 => Tracing Data 0x4020_FFC8 - 0x4020_FFFF => RAM exception Vectors We can increase the size to 0xFCB0 but I think it's better to use only 60K. At least the tracing vectors should be preserved.
Sascha
Jürgen _______________________________________________ barebox mailing list barebox@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/barebox
