public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Prabhakar Kushwaha <prabhakar@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] powerpc SPL framework: Avoiding relocate_code
Date: Mon, 9 Sep 2013 16:43:14 +0530	[thread overview]
Message-ID: <522DAD4A.3010504@freescale.com> (raw)

Hi,

  SPL framework is used to support multi-stage booting.  Where first 
level boot loader is created via SPL having relocate_code() function.
I am working on a Freescale's SoC which has less internal SRAM.
I don't want to use relocate_code() as to support this function, I need 
to reduce SPL bin  to SRAM/2 size.

is there way to avoid relocate_code function ?

I tried with below sequence, but it is not working for me :(

     .globl    relocate_code
relocate_code:
     mr    r1,r3        /* Set new stack pointer        */
     mr    r9,r4        /* Save copy of Init Data pointer    */
     mr    r10,r5        /* Save copy of Destination Address    */

     GET_GOT
#ifndef CONFIG_SPL_BUILD

--
--
#endif
     .globl    in_ram
in_ram:

The reason is bss "variables" which are mapped to 0x0000_0000 onwards 
because "bss"section are mapped after 0xfffffffc in lds. They are not 
available during SPL execution.  is there way to relocate bss section in 
the execution range of SPL?

Please advice.

Regards,
Prabhakar

             reply	other threads:[~2013-09-09 11:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-09 11:13 Prabhakar Kushwaha [this message]
2013-09-12 17:58 ` [U-Boot] powerpc SPL framework: Avoiding relocate_code Scott Wood
2013-09-13  9:53   ` Prabhakar Kushwaha
2013-09-16 20:46     ` Scott Wood
  -- strict thread matches above, loose matches on Subject: below --
2013-09-09 11:10 Prabhakar Kushwaha

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=522DAD4A.3010504@freescale.com \
    --to=prabhakar@freescale.com \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox