From mboxrd@z Thu Jan  1 00:00:00 1970
From: Richard Retanubun <RichardRetanubun@RuggedCom.com>
Date: Thu, 14 Jan 2010 16:46:56 -0500
Subject: [U-Boot] ppc: How to get uboot (relocated) start address in RAM
Message-ID: <4B4F90D0.90604@RuggedCom.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

Hi,

I a world post-ppc-relocation-patch, with gd->reloc_off removed,

I seem to have lost my way of figuring out uboot's address in RAM at run time.
Previously, I am able to use (gd->reloc_off+CONFIG_SYS_MONITOR_BASE) to get the answer.

Knowing the address is very useful for debuggging uboot using gdb.

The only spot that works now is the dest_addr variable in lib_ppc/board.c::board_init_r

debug ("Now running in RAM - U-Boot at: %08lx\n", dest_addr);

But the dest_addr is not saved into a global data variable.

Is it ok if I submit a patch that copies this dest_addr to gd->relocaddr
(currently only used by CONFIG_AMIGAONEG3SE) and print it as part of bdinfo?


Or is there a better method I am missing?

Regards,

- Richard Retanubun