Searched hist:"3 fb8016360d5433f3c4da51f8dd57550e7ef9018" (Results 1 – 7 of 7) sorted by relevance
| /rk3399_rockchip-uboot/arch/arc/include/asm/ |
| H A D | u-boot-arc.h | 3fb8016360d5433f3c4da51f8dd57550e7ef9018 Tue Feb 24 16:40:36 UTC 2015 Alexey Brodkin <abrodkin@synopsys.com> arc: clean-up init procedure
Intention behind this work was elimination of as much assembly-written
code as it is possible.
In case of ARC we already have relocation fix-up implemented in C so why
don't we use C for U-Boot copying, .bss zeroing etc.
It turned out x86 uses pretty similar approach so we re-used parts of
code in "board_f.c" initially implemented for x86.
Now assembly usage during init is limited to stack- and frame-pointer
setup before and after relocation.
Signed-off-by: Alexey Brodkin <abrodkin@synopsys.com>
Cc: Simon Glass <sjg@chromium.org>
|
| /rk3399_rockchip-uboot/arch/arc/lib/ |
| H A D | init_helpers.c | 3fb8016360d5433f3c4da51f8dd57550e7ef9018 Tue Feb 24 16:40:36 UTC 2015 Alexey Brodkin <abrodkin@synopsys.com> arc: clean-up init procedure
Intention behind this work was elimination of as much assembly-written
code as it is possible.
In case of ARC we already have relocation fix-up implemented in C so why
don't we use C for U-Boot copying, .bss zeroing etc.
It turned out x86 uses pretty similar approach so we re-used parts of
code in "board_f.c" initially implemented for x86.
Now assembly usage during init is limited to stack- and frame-pointer
setup before and after relocation.
Signed-off-by: Alexey Brodkin <abrodkin@synopsys.com>
Cc: Simon Glass <sjg@chromium.org>
|
| H A D | cpu.c | 3fb8016360d5433f3c4da51f8dd57550e7ef9018 Tue Feb 24 16:40:36 UTC 2015 Alexey Brodkin <abrodkin@synopsys.com> arc: clean-up init procedure
Intention behind this work was elimination of as much assembly-written
code as it is possible.
In case of ARC we already have relocation fix-up implemented in C so why
don't we use C for U-Boot copying, .bss zeroing etc.
It turned out x86 uses pretty similar approach so we re-used parts of
code in "board_f.c" initially implemented for x86.
Now assembly usage during init is limited to stack- and frame-pointer
setup before and after relocation.
Signed-off-by: Alexey Brodkin <abrodkin@synopsys.com>
Cc: Simon Glass <sjg@chromium.org>
|
| H A D | relocate.c | 3fb8016360d5433f3c4da51f8dd57550e7ef9018 Tue Feb 24 16:40:36 UTC 2015 Alexey Brodkin <abrodkin@synopsys.com> arc: clean-up init procedure
Intention behind this work was elimination of as much assembly-written
code as it is possible.
In case of ARC we already have relocation fix-up implemented in C so why
don't we use C for U-Boot copying, .bss zeroing etc.
It turned out x86 uses pretty similar approach so we re-used parts of
code in "board_f.c" initially implemented for x86.
Now assembly usage during init is limited to stack- and frame-pointer
setup before and after relocation.
Signed-off-by: Alexey Brodkin <abrodkin@synopsys.com>
Cc: Simon Glass <sjg@chromium.org>
|
| H A D | start.S | 3fb8016360d5433f3c4da51f8dd57550e7ef9018 Tue Feb 24 16:40:36 UTC 2015 Alexey Brodkin <abrodkin@synopsys.com> arc: clean-up init procedure
Intention behind this work was elimination of as much assembly-written
code as it is possible.
In case of ARC we already have relocation fix-up implemented in C so why
don't we use C for U-Boot copying, .bss zeroing etc.
It turned out x86 uses pretty similar approach so we re-used parts of
code in "board_f.c" initially implemented for x86.
Now assembly usage during init is limited to stack- and frame-pointer
setup before and after relocation.
Signed-off-by: Alexey Brodkin <abrodkin@synopsys.com>
Cc: Simon Glass <sjg@chromium.org>
|
| H A D | Makefile | 3fb8016360d5433f3c4da51f8dd57550e7ef9018 Tue Feb 24 16:40:36 UTC 2015 Alexey Brodkin <abrodkin@synopsys.com> arc: clean-up init procedure
Intention behind this work was elimination of as much assembly-written
code as it is possible.
In case of ARC we already have relocation fix-up implemented in C so why
don't we use C for U-Boot copying, .bss zeroing etc.
It turned out x86 uses pretty similar approach so we re-used parts of
code in "board_f.c" initially implemented for x86.
Now assembly usage during init is limited to stack- and frame-pointer
setup before and after relocation.
Signed-off-by: Alexey Brodkin <abrodkin@synopsys.com>
Cc: Simon Glass <sjg@chromium.org>
|
| /rk3399_rockchip-uboot/common/ |
| H A D | board_f.c | 3fb8016360d5433f3c4da51f8dd57550e7ef9018 Tue Feb 24 16:40:36 UTC 2015 Alexey Brodkin <abrodkin@synopsys.com> arc: clean-up init procedure
Intention behind this work was elimination of as much assembly-written
code as it is possible.
In case of ARC we already have relocation fix-up implemented in C so why
don't we use C for U-Boot copying, .bss zeroing etc.
It turned out x86 uses pretty similar approach so we re-used parts of
code in "board_f.c" initially implemented for x86.
Now assembly usage during init is limited to stack- and frame-pointer
setup before and after relocation.
Signed-off-by: Alexey Brodkin <abrodkin@synopsys.com>
Cc: Simon Glass <sjg@chromium.org>
|