| /rk3399_rockchip-uboot/board/renesas/sh7753evb/ |
| H A D | Makefile | 3f8b5391ec531adec6fa7602aeb8894b7a23d44d Sun Nov 27 22:15:25 UTC 2016 Vladimir Zapolskiy <vz@mleia.com> sh4: use single u-boot linker script for all boards
Three supported SH4/SH4A boards with the bootloader image stored on
SPI flash have own flavour of a linker script, in turn they are equal
among each other. The only difference is that the text from
lowlevel_init.o is placed right after start.o, which makes sense.
Note that .bss section is not marked as NOLOAD, because for about
10 years this is a default option of a GNU linker, either the
attribute is found or not the resulting image file is the same.
Signed-off-by: Vladimir Zapolskiy <vz@mleia.com>
Reviewed-by: Simon Glass <sjg@chromium.org>
|
| /rk3399_rockchip-uboot/board/renesas/sh7752evb/ |
| H A D | Makefile | 3f8b5391ec531adec6fa7602aeb8894b7a23d44d Sun Nov 27 22:15:25 UTC 2016 Vladimir Zapolskiy <vz@mleia.com> sh4: use single u-boot linker script for all boards
Three supported SH4/SH4A boards with the bootloader image stored on
SPI flash have own flavour of a linker script, in turn they are equal
among each other. The only difference is that the text from
lowlevel_init.o is placed right after start.o, which makes sense.
Note that .bss section is not marked as NOLOAD, because for about
10 years this is a default option of a GNU linker, either the
attribute is found or not the resulting image file is the same.
Signed-off-by: Vladimir Zapolskiy <vz@mleia.com>
Reviewed-by: Simon Glass <sjg@chromium.org>
|
| /rk3399_rockchip-uboot/board/renesas/sh7757lcr/ |
| H A D | Makefile | 3f8b5391ec531adec6fa7602aeb8894b7a23d44d Sun Nov 27 22:15:25 UTC 2016 Vladimir Zapolskiy <vz@mleia.com> sh4: use single u-boot linker script for all boards
Three supported SH4/SH4A boards with the bootloader image stored on
SPI flash have own flavour of a linker script, in turn they are equal
among each other. The only difference is that the text from
lowlevel_init.o is placed right after start.o, which makes sense.
Note that .bss section is not marked as NOLOAD, because for about
10 years this is a default option of a GNU linker, either the
attribute is found or not the resulting image file is the same.
Signed-off-by: Vladimir Zapolskiy <vz@mleia.com>
Reviewed-by: Simon Glass <sjg@chromium.org>
|
| /rk3399_rockchip-uboot/arch/sh/cpu/ |
| H A D | u-boot.lds | 3f8b5391ec531adec6fa7602aeb8894b7a23d44d Sun Nov 27 22:15:25 UTC 2016 Vladimir Zapolskiy <vz@mleia.com> sh4: use single u-boot linker script for all boards
Three supported SH4/SH4A boards with the bootloader image stored on
SPI flash have own flavour of a linker script, in turn they are equal
among each other. The only difference is that the text from
lowlevel_init.o is placed right after start.o, which makes sense.
Note that .bss section is not marked as NOLOAD, because for about
10 years this is a default option of a GNU linker, either the
attribute is found or not the resulting image file is the same.
Signed-off-by: Vladimir Zapolskiy <vz@mleia.com>
Reviewed-by: Simon Glass <sjg@chromium.org>
|
| /rk3399_rockchip-uboot/include/configs/ |
| H A D | sh7753evb.h | 3f8b5391ec531adec6fa7602aeb8894b7a23d44d Sun Nov 27 22:15:25 UTC 2016 Vladimir Zapolskiy <vz@mleia.com> sh4: use single u-boot linker script for all boards
Three supported SH4/SH4A boards with the bootloader image stored on
SPI flash have own flavour of a linker script, in turn they are equal
among each other. The only difference is that the text from
lowlevel_init.o is placed right after start.o, which makes sense.
Note that .bss section is not marked as NOLOAD, because for about
10 years this is a default option of a GNU linker, either the
attribute is found or not the resulting image file is the same.
Signed-off-by: Vladimir Zapolskiy <vz@mleia.com>
Reviewed-by: Simon Glass <sjg@chromium.org>
|
| H A D | sh7752evb.h | 3f8b5391ec531adec6fa7602aeb8894b7a23d44d Sun Nov 27 22:15:25 UTC 2016 Vladimir Zapolskiy <vz@mleia.com> sh4: use single u-boot linker script for all boards
Three supported SH4/SH4A boards with the bootloader image stored on
SPI flash have own flavour of a linker script, in turn they are equal
among each other. The only difference is that the text from
lowlevel_init.o is placed right after start.o, which makes sense.
Note that .bss section is not marked as NOLOAD, because for about
10 years this is a default option of a GNU linker, either the
attribute is found or not the resulting image file is the same.
Signed-off-by: Vladimir Zapolskiy <vz@mleia.com>
Reviewed-by: Simon Glass <sjg@chromium.org>
|
| H A D | sh7757lcr.h | 3f8b5391ec531adec6fa7602aeb8894b7a23d44d Sun Nov 27 22:15:25 UTC 2016 Vladimir Zapolskiy <vz@mleia.com> sh4: use single u-boot linker script for all boards
Three supported SH4/SH4A boards with the bootloader image stored on
SPI flash have own flavour of a linker script, in turn they are equal
among each other. The only difference is that the text from
lowlevel_init.o is placed right after start.o, which makes sense.
Note that .bss section is not marked as NOLOAD, because for about
10 years this is a default option of a GNU linker, either the
attribute is found or not the resulting image file is the same.
Signed-off-by: Vladimir Zapolskiy <vz@mleia.com>
Reviewed-by: Simon Glass <sjg@chromium.org>
|