2005-04-17 06:20:36 +08:00
|
|
|
/*
|
|
|
|
|
* Copyright (C) Paul Mackerras 1997.
|
|
|
|
|
*
|
2014-04-24 15:23:37 +08:00
|
|
|
* Adapted for 64 bit LE PowerPC by Andrew Tauferner
|
|
|
|
|
*
|
2005-04-17 06:20:36 +08:00
|
|
|
* This program is free software; you can redistribute it and/or
|
|
|
|
|
* modify it under the terms of the GNU General Public License
|
|
|
|
|
* as published by the Free Software Foundation; either version
|
|
|
|
|
* 2 of the License, or (at your option) any later version.
|
|
|
|
|
*
|
|
|
|
|
*/
|
|
|
|
|
|
2005-08-08 11:24:38 +08:00
|
|
|
#include "ppc_asm.h"
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2014-04-24 15:23:37 +08:00
|
|
|
RELA = 7
|
|
|
|
|
RELACOUNT = 0x6ffffff9
|
|
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
.text
|
2011-04-13 04:38:55 +08:00
|
|
|
/* A procedure descriptor used when booting this as a COFF file.
|
|
|
|
|
* When making COFF, this comes first in the link and we're
|
|
|
|
|
* linked at 0x500000.
|
|
|
|
|
*/
|
2007-06-07 20:21:31 +08:00
|
|
|
.globl _zimage_start_opd
|
2006-01-14 12:04:06 +08:00
|
|
|
_zimage_start_opd:
|
2011-04-13 04:38:55 +08:00
|
|
|
.long 0x500000, 0, 0, 0
|
|
|
|
|
|
2014-04-24 15:23:37 +08:00
|
|
|
#ifdef __powerpc64__
|
|
|
|
|
.balign 8
|
2017-03-09 13:42:12 +08:00
|
|
|
p_start: .8byte _start
|
|
|
|
|
p_etext: .8byte _etext
|
|
|
|
|
p_bss_start: .8byte __bss_start
|
|
|
|
|
p_end: .8byte _end
|
2014-04-24 15:23:37 +08:00
|
|
|
|
2017-03-09 13:42:12 +08:00
|
|
|
p_toc: .8byte __toc_start + 0x8000 - p_base
|
|
|
|
|
p_dyn: .8byte __dynamic_start - p_base
|
|
|
|
|
p_rela: .8byte __rela_dyn_start - p_base
|
|
|
|
|
p_prom: .8byte 0
|
2014-04-24 15:23:37 +08:00
|
|
|
.weak _platform_stack_top
|
2017-03-09 13:42:12 +08:00
|
|
|
p_pstack: .8byte _platform_stack_top
|
2014-04-24 15:23:37 +08:00
|
|
|
#else
|
2011-04-13 04:38:55 +08:00
|
|
|
p_start: .long _start
|
|
|
|
|
p_etext: .long _etext
|
|
|
|
|
p_bss_start: .long __bss_start
|
|
|
|
|
p_end: .long _end
|
|
|
|
|
|
|
|
|
|
.weak _platform_stack_top
|
|
|
|
|
p_pstack: .long _platform_stack_top
|
2014-04-24 15:23:37 +08:00
|
|
|
#endif
|
2006-01-14 12:04:06 +08:00
|
|
|
|
[POWERPC] zImage: Cleanup and improve zImage entry point
This patch re-organises the way the zImage wrapper code is entered, to
allow more flexibility on platforms with unusual entry conditions.
After this patch, a platform .o file has two options:
1) It can define a _zimage_start, in which case the platform code gets
control from the very beginning of execution. In this case the
platform code is responsible for relocating the zImage if necessary,
clearing the BSS, performing any platform specific initialization, and
finally calling start() to load and enter the kernel.
2) It can define platform_init(). In this case the generic crt0.S
handles initial entry, and calls platform_init() before calling
start(). The signature of platform_init() is changed, however, to
take up to 5 parameters (in r3..r7) as they come from the platform's
initial loader, instead of a fixed set of parameters based on OF's
usage.
When using the generic crt0.S, the platform .o can optionally
supply a custom stack to use, using the BSS_STACK() macro. If this
is not supplied, the crt0.S will assume that the loader has
supplied a usable stack.
In either case, the platform code communicates information to the
generic code (specifically, a PROM pointer for OF systems, and/or an
initrd image address supplied by the bootloader) via a global
structure "loader_info".
In addition the wrapper script is rearranged to ensure that the
platform .o is always linked first. This means that platforms where
the zImage entry point is at a fixed address or offset, rather than
being encoded in the binary header can be supported using option (1).
Signed-off-by: David Gibson <dwg@au1.ibm.com>
Signed-off-by: Paul Mackerras <paulus@samba.org>
2007-03-05 11:24:52 +08:00
|
|
|
.weak _zimage_start
|
2005-10-29 08:46:49 +08:00
|
|
|
.globl _zimage_start
|
|
|
|
|
_zimage_start:
|
2007-03-21 23:02:53 +08:00
|
|
|
.globl _zimage_start_lib
|
|
|
|
|
_zimage_start_lib:
|
2006-01-14 12:04:06 +08:00
|
|
|
/* Work out the offset between the address we were linked at
|
|
|
|
|
and the address where we're running. */
|
2011-04-13 04:38:55 +08:00
|
|
|
bl .+4
|
|
|
|
|
p_base: mflr r10 /* r10 now points to runtime addr of p_base */
|
2014-04-24 15:23:37 +08:00
|
|
|
#ifndef __powerpc64__
|
2011-04-13 04:38:55 +08:00
|
|
|
/* grab the link address of the dynamic section in r11 */
|
|
|
|
|
addis r11,r10,(_GLOBAL_OFFSET_TABLE_-p_base)@ha
|
|
|
|
|
lwz r11,(_GLOBAL_OFFSET_TABLE_-p_base)@l(r11)
|
|
|
|
|
cmpwi r11,0
|
|
|
|
|
beq 3f /* if not linked -pie */
|
|
|
|
|
/* get the runtime address of the dynamic section in r12 */
|
|
|
|
|
.weak __dynamic_start
|
|
|
|
|
addis r12,r10,(__dynamic_start-p_base)@ha
|
|
|
|
|
addi r12,r12,(__dynamic_start-p_base)@l
|
|
|
|
|
subf r11,r11,r12 /* runtime - linktime offset */
|
|
|
|
|
|
|
|
|
|
/* The dynamic section contains a series of tagged entries.
|
|
|
|
|
* We need the RELA and RELACOUNT entries. */
|
|
|
|
|
li r9,0
|
|
|
|
|
li r0,0
|
|
|
|
|
9: lwz r8,0(r12) /* get tag */
|
|
|
|
|
cmpwi r8,0
|
|
|
|
|
beq 10f /* end of list */
|
|
|
|
|
cmpwi r8,RELA
|
|
|
|
|
bne 11f
|
|
|
|
|
lwz r9,4(r12) /* get RELA pointer in r9 */
|
|
|
|
|
b 12f
|
|
|
|
|
11: addis r8,r8,(-RELACOUNT)@ha
|
|
|
|
|
cmpwi r8,RELACOUNT@l
|
|
|
|
|
bne 12f
|
|
|
|
|
lwz r0,4(r12) /* get RELACOUNT value in r0 */
|
|
|
|
|
12: addi r12,r12,8
|
|
|
|
|
b 9b
|
2005-10-29 08:46:48 +08:00
|
|
|
|
2011-04-13 04:38:55 +08:00
|
|
|
/* The relocation section contains a list of relocations.
|
|
|
|
|
* We now do the R_PPC_RELATIVE ones, which point to words
|
|
|
|
|
* which need to be initialized with addend + offset.
|
|
|
|
|
* The R_PPC_RELATIVE ones come first and there are RELACOUNT
|
|
|
|
|
* of them. */
|
|
|
|
|
10: /* skip relocation if we don't have both */
|
|
|
|
|
cmpwi r0,0
|
2005-11-18 05:09:02 +08:00
|
|
|
beq 3f
|
2011-04-13 04:38:55 +08:00
|
|
|
cmpwi r9,0
|
|
|
|
|
beq 3f
|
|
|
|
|
|
|
|
|
|
add r9,r9,r11 /* Relocate RELA pointer */
|
|
|
|
|
mtctr r0
|
|
|
|
|
2: lbz r0,4+3(r9) /* ELF32_R_INFO(reloc->r_info) */
|
|
|
|
|
cmpwi r0,22 /* R_PPC_RELATIVE */
|
|
|
|
|
bne 3f
|
|
|
|
|
lwz r12,0(r9) /* reloc->r_offset */
|
|
|
|
|
lwz r0,8(r9) /* reloc->r_addend */
|
|
|
|
|
add r0,r0,r11
|
|
|
|
|
stwx r0,r11,r12
|
|
|
|
|
addi r9,r9,12
|
2005-11-18 05:09:02 +08:00
|
|
|
bdnz 2b
|
2005-10-29 08:46:48 +08:00
|
|
|
|
[POWERPC] zImage: Cleanup and improve zImage entry point
This patch re-organises the way the zImage wrapper code is entered, to
allow more flexibility on platforms with unusual entry conditions.
After this patch, a platform .o file has two options:
1) It can define a _zimage_start, in which case the platform code gets
control from the very beginning of execution. In this case the
platform code is responsible for relocating the zImage if necessary,
clearing the BSS, performing any platform specific initialization, and
finally calling start() to load and enter the kernel.
2) It can define platform_init(). In this case the generic crt0.S
handles initial entry, and calls platform_init() before calling
start(). The signature of platform_init() is changed, however, to
take up to 5 parameters (in r3..r7) as they come from the platform's
initial loader, instead of a fixed set of parameters based on OF's
usage.
When using the generic crt0.S, the platform .o can optionally
supply a custom stack to use, using the BSS_STACK() macro. If this
is not supplied, the crt0.S will assume that the loader has
supplied a usable stack.
In either case, the platform code communicates information to the
generic code (specifically, a PROM pointer for OF systems, and/or an
initrd image address supplied by the bootloader) via a global
structure "loader_info".
In addition the wrapper script is rearranged to ensure that the
platform .o is always linked first. This means that platforms where
the zImage entry point is at a fixed address or offset, rather than
being encoded in the binary header can be supported using option (1).
Signed-off-by: David Gibson <dwg@au1.ibm.com>
Signed-off-by: Paul Mackerras <paulus@samba.org>
2007-03-05 11:24:52 +08:00
|
|
|
/* Do a cache flush for our text, in case the loader didn't */
|
2011-04-13 04:38:55 +08:00
|
|
|
3: lwz r9,p_start-p_base(r10) /* note: these are relocated now */
|
|
|
|
|
lwz r8,p_etext-p_base(r10)
|
2005-11-18 05:09:02 +08:00
|
|
|
4: dcbf r0,r9
|
2005-04-17 06:20:36 +08:00
|
|
|
icbi r0,r9
|
|
|
|
|
addi r9,r9,0x20
|
2006-03-04 20:15:40 +08:00
|
|
|
cmplw cr0,r9,r8
|
2005-11-18 05:09:02 +08:00
|
|
|
blt 4b
|
2005-04-17 06:20:36 +08:00
|
|
|
sync
|
|
|
|
|
isync
|
|
|
|
|
|
[POWERPC] zImage: Cleanup and improve zImage entry point
This patch re-organises the way the zImage wrapper code is entered, to
allow more flexibility on platforms with unusual entry conditions.
After this patch, a platform .o file has two options:
1) It can define a _zimage_start, in which case the platform code gets
control from the very beginning of execution. In this case the
platform code is responsible for relocating the zImage if necessary,
clearing the BSS, performing any platform specific initialization, and
finally calling start() to load and enter the kernel.
2) It can define platform_init(). In this case the generic crt0.S
handles initial entry, and calls platform_init() before calling
start(). The signature of platform_init() is changed, however, to
take up to 5 parameters (in r3..r7) as they come from the platform's
initial loader, instead of a fixed set of parameters based on OF's
usage.
When using the generic crt0.S, the platform .o can optionally
supply a custom stack to use, using the BSS_STACK() macro. If this
is not supplied, the crt0.S will assume that the loader has
supplied a usable stack.
In either case, the platform code communicates information to the
generic code (specifically, a PROM pointer for OF systems, and/or an
initrd image address supplied by the bootloader) via a global
structure "loader_info".
In addition the wrapper script is rearranged to ensure that the
platform .o is always linked first. This means that platforms where
the zImage entry point is at a fixed address or offset, rather than
being encoded in the binary header can be supported using option (1).
Signed-off-by: David Gibson <dwg@au1.ibm.com>
Signed-off-by: Paul Mackerras <paulus@samba.org>
2007-03-05 11:24:52 +08:00
|
|
|
/* Clear the BSS */
|
2011-04-13 04:38:55 +08:00
|
|
|
lwz r9,p_bss_start-p_base(r10)
|
|
|
|
|
lwz r8,p_end-p_base(r10)
|
|
|
|
|
li r0,0
|
|
|
|
|
5: stw r0,0(r9)
|
[POWERPC] zImage: Cleanup and improve zImage entry point
This patch re-organises the way the zImage wrapper code is entered, to
allow more flexibility on platforms with unusual entry conditions.
After this patch, a platform .o file has two options:
1) It can define a _zimage_start, in which case the platform code gets
control from the very beginning of execution. In this case the
platform code is responsible for relocating the zImage if necessary,
clearing the BSS, performing any platform specific initialization, and
finally calling start() to load and enter the kernel.
2) It can define platform_init(). In this case the generic crt0.S
handles initial entry, and calls platform_init() before calling
start(). The signature of platform_init() is changed, however, to
take up to 5 parameters (in r3..r7) as they come from the platform's
initial loader, instead of a fixed set of parameters based on OF's
usage.
When using the generic crt0.S, the platform .o can optionally
supply a custom stack to use, using the BSS_STACK() macro. If this
is not supplied, the crt0.S will assume that the loader has
supplied a usable stack.
In either case, the platform code communicates information to the
generic code (specifically, a PROM pointer for OF systems, and/or an
initrd image address supplied by the bootloader) via a global
structure "loader_info".
In addition the wrapper script is rearranged to ensure that the
platform .o is always linked first. This means that platforms where
the zImage entry point is at a fixed address or offset, rather than
being encoded in the binary header can be supported using option (1).
Signed-off-by: David Gibson <dwg@au1.ibm.com>
Signed-off-by: Paul Mackerras <paulus@samba.org>
2007-03-05 11:24:52 +08:00
|
|
|
addi r9,r9,4
|
|
|
|
|
cmplw cr0,r9,r8
|
|
|
|
|
blt 5b
|
2005-04-17 06:20:36 +08:00
|
|
|
|
[POWERPC] zImage: Cleanup and improve zImage entry point
This patch re-organises the way the zImage wrapper code is entered, to
allow more flexibility on platforms with unusual entry conditions.
After this patch, a platform .o file has two options:
1) It can define a _zimage_start, in which case the platform code gets
control from the very beginning of execution. In this case the
platform code is responsible for relocating the zImage if necessary,
clearing the BSS, performing any platform specific initialization, and
finally calling start() to load and enter the kernel.
2) It can define platform_init(). In this case the generic crt0.S
handles initial entry, and calls platform_init() before calling
start(). The signature of platform_init() is changed, however, to
take up to 5 parameters (in r3..r7) as they come from the platform's
initial loader, instead of a fixed set of parameters based on OF's
usage.
When using the generic crt0.S, the platform .o can optionally
supply a custom stack to use, using the BSS_STACK() macro. If this
is not supplied, the crt0.S will assume that the loader has
supplied a usable stack.
In either case, the platform code communicates information to the
generic code (specifically, a PROM pointer for OF systems, and/or an
initrd image address supplied by the bootloader) via a global
structure "loader_info".
In addition the wrapper script is rearranged to ensure that the
platform .o is always linked first. This means that platforms where
the zImage entry point is at a fixed address or offset, rather than
being encoded in the binary header can be supported using option (1).
Signed-off-by: David Gibson <dwg@au1.ibm.com>
Signed-off-by: Paul Mackerras <paulus@samba.org>
2007-03-05 11:24:52 +08:00
|
|
|
/* Possibly set up a custom stack */
|
2011-04-13 04:38:55 +08:00
|
|
|
lwz r8,p_pstack-p_base(r10)
|
[POWERPC] zImage: Cleanup and improve zImage entry point
This patch re-organises the way the zImage wrapper code is entered, to
allow more flexibility on platforms with unusual entry conditions.
After this patch, a platform .o file has two options:
1) It can define a _zimage_start, in which case the platform code gets
control from the very beginning of execution. In this case the
platform code is responsible for relocating the zImage if necessary,
clearing the BSS, performing any platform specific initialization, and
finally calling start() to load and enter the kernel.
2) It can define platform_init(). In this case the generic crt0.S
handles initial entry, and calls platform_init() before calling
start(). The signature of platform_init() is changed, however, to
take up to 5 parameters (in r3..r7) as they come from the platform's
initial loader, instead of a fixed set of parameters based on OF's
usage.
When using the generic crt0.S, the platform .o can optionally
supply a custom stack to use, using the BSS_STACK() macro. If this
is not supplied, the crt0.S will assume that the loader has
supplied a usable stack.
In either case, the platform code communicates information to the
generic code (specifically, a PROM pointer for OF systems, and/or an
initrd image address supplied by the bootloader) via a global
structure "loader_info".
In addition the wrapper script is rearranged to ensure that the
platform .o is always linked first. This means that platforms where
the zImage entry point is at a fixed address or offset, rather than
being encoded in the binary header can be supported using option (1).
Signed-off-by: David Gibson <dwg@au1.ibm.com>
Signed-off-by: Paul Mackerras <paulus@samba.org>
2007-03-05 11:24:52 +08:00
|
|
|
cmpwi r8,0
|
|
|
|
|
beq 6f
|
|
|
|
|
lwz r1,0(r8)
|
|
|
|
|
li r0,0
|
|
|
|
|
stwu r0,-16(r1) /* establish a stack frame */
|
|
|
|
|
6:
|
2014-04-24 15:23:37 +08:00
|
|
|
#else /* __powerpc64__ */
|
|
|
|
|
/* Save the prom pointer at p_prom. */
|
|
|
|
|
std r5,(p_prom-p_base)(r10)
|
|
|
|
|
|
|
|
|
|
/* Set r2 to the TOC. */
|
|
|
|
|
ld r2,(p_toc-p_base)(r10)
|
|
|
|
|
add r2,r2,r10
|
|
|
|
|
|
|
|
|
|
/* Grab the link address of the dynamic section in r11. */
|
|
|
|
|
ld r11,-32768(r2)
|
|
|
|
|
cmpwi r11,0
|
|
|
|
|
beq 3f /* if not linked -pie then no dynamic section */
|
|
|
|
|
|
|
|
|
|
ld r11,(p_dyn-p_base)(r10)
|
|
|
|
|
add r11,r11,r10
|
|
|
|
|
ld r9,(p_rela-p_base)(r10)
|
|
|
|
|
add r9,r9,r10
|
|
|
|
|
|
2015-02-11 12:55:44 +08:00
|
|
|
li r13,0
|
2014-04-24 15:23:37 +08:00
|
|
|
li r8,0
|
2015-02-11 12:55:44 +08:00
|
|
|
9: ld r12,0(r11) /* get tag */
|
|
|
|
|
cmpdi r12,0
|
2014-04-24 15:23:37 +08:00
|
|
|
beq 12f /* end of list */
|
2015-02-11 12:55:44 +08:00
|
|
|
cmpdi r12,RELA
|
2014-04-24 15:23:37 +08:00
|
|
|
bne 10f
|
2015-02-11 12:55:44 +08:00
|
|
|
ld r13,8(r11) /* get RELA pointer in r13 */
|
2014-04-24 15:23:37 +08:00
|
|
|
b 11f
|
2015-02-11 12:55:44 +08:00
|
|
|
10: addis r12,r12,(-RELACOUNT)@ha
|
|
|
|
|
cmpdi r12,RELACOUNT@l
|
2014-04-24 15:23:37 +08:00
|
|
|
bne 11f
|
|
|
|
|
ld r8,8(r11) /* get RELACOUNT value in r8 */
|
|
|
|
|
11: addi r11,r11,16
|
|
|
|
|
b 9b
|
|
|
|
|
12:
|
2015-02-11 12:55:44 +08:00
|
|
|
cmpdi r13,0 /* check we have both RELA and RELACOUNT */
|
2014-04-24 15:23:37 +08:00
|
|
|
cmpdi cr1,r8,0
|
|
|
|
|
beq 3f
|
|
|
|
|
beq cr1,3f
|
|
|
|
|
|
|
|
|
|
/* Calcuate the runtime offset. */
|
2015-02-11 12:55:44 +08:00
|
|
|
subf r13,r13,r9
|
[POWERPC] zImage: Cleanup and improve zImage entry point
This patch re-organises the way the zImage wrapper code is entered, to
allow more flexibility on platforms with unusual entry conditions.
After this patch, a platform .o file has two options:
1) It can define a _zimage_start, in which case the platform code gets
control from the very beginning of execution. In this case the
platform code is responsible for relocating the zImage if necessary,
clearing the BSS, performing any platform specific initialization, and
finally calling start() to load and enter the kernel.
2) It can define platform_init(). In this case the generic crt0.S
handles initial entry, and calls platform_init() before calling
start(). The signature of platform_init() is changed, however, to
take up to 5 parameters (in r3..r7) as they come from the platform's
initial loader, instead of a fixed set of parameters based on OF's
usage.
When using the generic crt0.S, the platform .o can optionally
supply a custom stack to use, using the BSS_STACK() macro. If this
is not supplied, the crt0.S will assume that the loader has
supplied a usable stack.
In either case, the platform code communicates information to the
generic code (specifically, a PROM pointer for OF systems, and/or an
initrd image address supplied by the bootloader) via a global
structure "loader_info".
In addition the wrapper script is rearranged to ensure that the
platform .o is always linked first. This means that platforms where
the zImage entry point is at a fixed address or offset, rather than
being encoded in the binary header can be supported using option (1).
Signed-off-by: David Gibson <dwg@au1.ibm.com>
Signed-off-by: Paul Mackerras <paulus@samba.org>
2007-03-05 11:24:52 +08:00
|
|
|
|
2014-04-24 15:23:37 +08:00
|
|
|
/* Run through the list of relocations and process the
|
|
|
|
|
* R_PPC64_RELATIVE ones. */
|
|
|
|
|
mtctr r8
|
|
|
|
|
13: ld r0,8(r9) /* ELF64_R_TYPE(reloc->r_info) */
|
|
|
|
|
cmpdi r0,22 /* R_PPC64_RELATIVE */
|
|
|
|
|
bne 3f
|
2015-02-11 12:55:44 +08:00
|
|
|
ld r12,0(r9) /* reloc->r_offset */
|
2014-04-24 15:23:37 +08:00
|
|
|
ld r0,16(r9) /* reloc->r_addend */
|
2015-02-11 12:55:44 +08:00
|
|
|
add r0,r0,r13
|
|
|
|
|
stdx r0,r13,r12
|
2014-04-24 15:23:37 +08:00
|
|
|
addi r9,r9,24
|
|
|
|
|
bdnz 13b
|
|
|
|
|
|
|
|
|
|
/* Do a cache flush for our text, in case the loader didn't */
|
|
|
|
|
3: ld r9,p_start-p_base(r10) /* note: these are relocated now */
|
|
|
|
|
ld r8,p_etext-p_base(r10)
|
|
|
|
|
4: dcbf r0,r9
|
|
|
|
|
icbi r0,r9
|
|
|
|
|
addi r9,r9,0x20
|
|
|
|
|
cmpld cr0,r9,r8
|
|
|
|
|
blt 4b
|
|
|
|
|
sync
|
|
|
|
|
isync
|
|
|
|
|
|
|
|
|
|
/* Clear the BSS */
|
|
|
|
|
ld r9,p_bss_start-p_base(r10)
|
|
|
|
|
ld r8,p_end-p_base(r10)
|
|
|
|
|
li r0,0
|
|
|
|
|
5: std r0,0(r9)
|
|
|
|
|
addi r9,r9,8
|
|
|
|
|
cmpld cr0,r9,r8
|
|
|
|
|
blt 5b
|
|
|
|
|
|
|
|
|
|
/* Possibly set up a custom stack */
|
|
|
|
|
ld r8,p_pstack-p_base(r10)
|
|
|
|
|
cmpdi r8,0
|
|
|
|
|
beq 6f
|
|
|
|
|
ld r1,0(r8)
|
|
|
|
|
li r0,0
|
2015-02-11 12:55:44 +08:00
|
|
|
stdu r0,-112(r1) /* establish a stack frame */
|
2014-04-24 15:23:37 +08:00
|
|
|
6:
|
|
|
|
|
#endif /* __powerpc64__ */
|
[POWERPC] zImage: Cleanup and improve zImage entry point
This patch re-organises the way the zImage wrapper code is entered, to
allow more flexibility on platforms with unusual entry conditions.
After this patch, a platform .o file has two options:
1) It can define a _zimage_start, in which case the platform code gets
control from the very beginning of execution. In this case the
platform code is responsible for relocating the zImage if necessary,
clearing the BSS, performing any platform specific initialization, and
finally calling start() to load and enter the kernel.
2) It can define platform_init(). In this case the generic crt0.S
handles initial entry, and calls platform_init() before calling
start(). The signature of platform_init() is changed, however, to
take up to 5 parameters (in r3..r7) as they come from the platform's
initial loader, instead of a fixed set of parameters based on OF's
usage.
When using the generic crt0.S, the platform .o can optionally
supply a custom stack to use, using the BSS_STACK() macro. If this
is not supplied, the crt0.S will assume that the loader has
supplied a usable stack.
In either case, the platform code communicates information to the
generic code (specifically, a PROM pointer for OF systems, and/or an
initrd image address supplied by the bootloader) via a global
structure "loader_info".
In addition the wrapper script is rearranged to ensure that the
platform .o is always linked first. This means that platforms where
the zImage entry point is at a fixed address or offset, rather than
being encoded in the binary header can be supported using option (1).
Signed-off-by: David Gibson <dwg@au1.ibm.com>
Signed-off-by: Paul Mackerras <paulus@samba.org>
2007-03-05 11:24:52 +08:00
|
|
|
/* Call platform_init() */
|
|
|
|
|
bl platform_init
|
|
|
|
|
|
|
|
|
|
/* Call start */
|
|
|
|
|
b start
|
2014-04-24 15:23:36 +08:00
|
|
|
|
|
|
|
|
#ifdef __powerpc64__
|
|
|
|
|
|
|
|
|
|
#define PROM_FRAME_SIZE 512
|
|
|
|
|
#define SAVE_GPR(n, base) std n,8*(n)(base)
|
|
|
|
|
#define REST_GPR(n, base) ld n,8*(n)(base)
|
|
|
|
|
#define SAVE_2GPRS(n, base) SAVE_GPR(n, base); SAVE_GPR(n+1, base)
|
|
|
|
|
#define SAVE_4GPRS(n, base) SAVE_2GPRS(n, base); SAVE_2GPRS(n+2, base)
|
|
|
|
|
#define SAVE_8GPRS(n, base) SAVE_4GPRS(n, base); SAVE_4GPRS(n+4, base)
|
|
|
|
|
#define SAVE_10GPRS(n, base) SAVE_8GPRS(n, base); SAVE_2GPRS(n+8, base)
|
|
|
|
|
#define REST_2GPRS(n, base) REST_GPR(n, base); REST_GPR(n+1, base)
|
|
|
|
|
#define REST_4GPRS(n, base) REST_2GPRS(n, base); REST_2GPRS(n+2, base)
|
|
|
|
|
#define REST_8GPRS(n, base) REST_4GPRS(n, base); REST_4GPRS(n+4, base)
|
|
|
|
|
#define REST_10GPRS(n, base) REST_8GPRS(n, base); REST_2GPRS(n+8, base)
|
|
|
|
|
|
|
|
|
|
/* prom handles the jump into and return from firmware. The prom args pointer
|
|
|
|
|
is loaded in r3. */
|
|
|
|
|
.globl prom
|
|
|
|
|
prom:
|
|
|
|
|
mflr r0
|
|
|
|
|
std r0,16(r1)
|
|
|
|
|
stdu r1,-PROM_FRAME_SIZE(r1) /* Save SP and create stack space */
|
|
|
|
|
|
|
|
|
|
SAVE_GPR(2, r1)
|
|
|
|
|
SAVE_GPR(13, r1)
|
|
|
|
|
SAVE_8GPRS(14, r1)
|
|
|
|
|
SAVE_10GPRS(22, r1)
|
|
|
|
|
mfcr r10
|
|
|
|
|
std r10,8*32(r1)
|
|
|
|
|
mfmsr r10
|
|
|
|
|
std r10,8*33(r1)
|
|
|
|
|
|
|
|
|
|
/* remove MSR_LE from msr but keep MSR_SF */
|
|
|
|
|
mfmsr r10
|
|
|
|
|
rldicr r10,r10,0,62
|
|
|
|
|
mtsrr1 r10
|
|
|
|
|
|
|
|
|
|
/* Load FW address, set LR to label 1, and jump to FW */
|
|
|
|
|
bl 0f
|
|
|
|
|
0: mflr r10
|
|
|
|
|
addi r11,r10,(1f-0b)
|
|
|
|
|
mtlr r11
|
|
|
|
|
|
|
|
|
|
ld r10,(p_prom-0b)(r10)
|
|
|
|
|
mtsrr0 r10
|
|
|
|
|
|
|
|
|
|
rfid
|
|
|
|
|
|
|
|
|
|
1: /* Return from OF */
|
2014-04-24 15:23:39 +08:00
|
|
|
FIXUP_ENDIAN
|
2014-04-24 15:23:36 +08:00
|
|
|
|
|
|
|
|
/* Restore registers and return. */
|
|
|
|
|
rldicl r1,r1,0,32
|
|
|
|
|
|
|
|
|
|
/* Restore the MSR (back to 64 bits) */
|
|
|
|
|
ld r10,8*(33)(r1)
|
|
|
|
|
mtmsr r10
|
|
|
|
|
isync
|
|
|
|
|
|
|
|
|
|
/* Restore other registers */
|
|
|
|
|
REST_GPR(2, r1)
|
|
|
|
|
REST_GPR(13, r1)
|
|
|
|
|
REST_8GPRS(14, r1)
|
|
|
|
|
REST_10GPRS(22, r1)
|
|
|
|
|
ld r10,8*32(r1)
|
|
|
|
|
mtcr r10
|
|
|
|
|
|
|
|
|
|
addi r1,r1,PROM_FRAME_SIZE
|
|
|
|
|
ld r0,16(r1)
|
|
|
|
|
mtlr r0
|
|
|
|
|
blr
|
|
|
|
|
#endif
|