All of lore.kernel.org
 help / color / mirror / Atom feed
From: YanMin Qiao <sepherosa@sjtu.edu.cn>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] another question of relocate_code
Date: Sat, 04 Jan 2003 22:35:57 +0800	[thread overview]
Message-ID: <3E16F14D.8030808@sjtu.edu.cn> (raw)
In-Reply-To: 20030104135753.B8E0EC608E@atlas.denx.de

Wolfgang Denk wrote:

>In message <3E16E5AE.4090002@sjtu.edu.cn> you wrote:
>  
>
>>Hi all:
>>
>><u-boot>/cpu/mpc8xx/start.S
>>
>>....
>>relocate_code:
>>    mr    r1,  r3        /* Set new stack pointer        */
>>    mr    r9,  r4        /* Save copy of Global Data pointer    */
>>    mr    r10, r5        /* Save copy of Destination Address    */
>>....
>>    sub    r15, r10, r4
>>
>>    /* First our own GOT */
>>    add    r14, r14, r15
>>    /* the the one used by the C code */
>>    add    r30, r30, r15
>>              ^^^
>>....
>>
>>I have followed the code to the end of board_init_r().  I didn't figured 
>>out where r30 is used
>>as mentioned.
>>    
>>
>
>Which part of this section from the README didn't you understand?
>
>	... we are restricted  by  the 
>	relevant  (E)ABI  specifications for the current architecture, and by
>	GCC's implementation.
>	   
>	For PowerPC, the following registers have specific use:
>		R1:     stack pointer 
>		R2:     TOC pointer 
>		R3-R4:  parameter passing and return values
>		R5-R10: parameter passing 
>		R13:    small data area pointer 
>		R30:    GOT pointer 
>		R31:    frame pointer 
>	   
>		(U-Boot also uses R14 as internal GOT pointer.)
>
>If you want to know all the ugly details  I  recommend  to  read  the
>(E)ABI specifications and the relevant parts of the GCC source code.
>
>Best regards,
>
>Wolfgang Denk
>
>  
>
thanks for the mention of eabi  :)

Best regards

      reply	other threads:[~2003-01-04 14:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-04 13:46 [U-Boot-Users] another question of relocate_code YanMin Qiao
2003-01-04 13:57 ` Wolfgang Denk
2003-01-04 14:35   ` YanMin Qiao [this message]

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=3E16F14D.8030808@sjtu.edu.cn \
    --to=sepherosa@sjtu.edu.cn \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.