summaryrefslogtreecommitdiffstats
path: root/arch/arm/Makefile
Commit message (Collapse)AuthorAgeFilesLines
* ARM: mach-types: don't generate header at buildtimeAhmad Fatoum2024-01-041-7/+1
| | | | | | | | | | | | Now that we have removed 4642 machine types unused by barebox, we are just left with 65 boards. Let's just include the generated header in the source tree and stop generating the header anew at build time. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Link: https://lore.barebox.org/20231212120949.3459707-2-a.fatoum@pengutronix.de Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
* ARM: Add Texas Instruments K3 architectureSascha Hauer2023-11-061-0/+1
| | | | | | | | | | | This adds the Kconfig snippets for supporting the Texas Instruments K3 architecure. This also enables deep probe support on a SoC basis as all new boards should work with deep probe enabled. Likewise we need PM domain support for the initially supported AM62x SoC, so enable that for this SoC as well. Link: https://lore.barebox.org/20230803105003.4088205-18-s.hauer@pengutronix.de Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
* Merge branch 'for-next/misc'Sascha Hauer2023-06-221-25/+18
|\
| * ARM: don't assume 32-bit when no boards are selectedAhmad Fatoum2023-06-091-21/+14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | barebox build errors are very confusing if no board is selected. This should have been fixed with commit 14b296d2a7e6 ("arm: error out if __LINUX_ARM_ARCH__ is undefined"), but unfortunately that's only true for ARM32. On ARM64, the error message in question is not printed, because build aborts even earlier, because Kbuild assumes it should build for 32-bit ARM and thus passes the ARM64 compiler options that it can't understand: aarch64-oe-linux-gcc: error: unrecognized argument in option '-mabi=apcs-gnu' aarch64-oe-linux-gcc: note: valid arguments to '-mabi=' are: ilp32 lp64 aarch64-oe-linux-gcc: error: unrecognized command-line option '-msoft-float' aarch64-oe-linux-gcc: error: unrecognized command-line option '-mno-unaligned-access' Let's fix that for ARM64 builds by not assuming !CONFIG_CPU_64 to be 32-bit, but instead explicitly check that CONFIG_CPU_32 is set before doing 32-bit specific changes. This ensures we now fail during compilation on both ARM32 and ARM64 if no boards were selected. We can't fail earlier via $(error ...) as this would impact use of targets like menuconfig. Reported-by: Lior Weintraub <liorw@pliops.com> Reported-by: Ulrich Ölmann <u.oelmann@pengutronix.de> Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Link: https://lore.barebox.org/20230607153152.2681009-2-a.fatoum@pengutronix.de Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
| * ARM: replace CONFIG_CPU_V8 with CONFIG_CPU_64 in MakefileAhmad Fatoum2023-06-091-7/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We use CONFIG_CPU_V8 and CONFIG_CPU_64 interchangeably in barebox, because we don't yet support any SoCs with ARMv9 and because we always target the A64 instruction set on ARMv8 processors. In the Makefile where we have decisions dependent on whether we are compiling for 64-bit or not, we should rather use CONFIG_CPU_64 though, because the same options would likely be applicable to ARMv9 as well. Given that the follow-up commit will introduce a number of CONFIG_CPU_32, let's replace the CONFIG_CPU_V8 symbols with CONFIG_CPU_64 for symmetry. No functional change. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Link: https://lore.barebox.org/20230607153152.2681009-1-a.fatoum@pengutronix.de Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
* | ARM64: crypto: add Crypto Extensions accelerated SHA implementationAhmad Fatoum2023-05-261-1/+2
|/ | | | | | | | | | | | | | | | | | | | | | | | | | | This imports the Linux v6.3 state of the ARMv8 Crypto Extensions (CE) accelerated SHA1/SHA2 routines. This increases hashing rate a tenfold: sha1-generic: digest(7 bytes) = 11750ns digest(4097 bytes) = 59125ns sha224-generic: digest(7 bytes) = 12750ns digest(4097 bytes) = 95000ns sha256-generic: digest(7 bytes) = 2250ns digest(4097 bytes) = 94875ns sha1-ce: digest(7 bytes) = 2875ns digest(4097 bytes) = 8125ns sha224-ce: digest(7 bytes) = 3125ns digest(4097 bytes) = 7750ns sha256-ce: digest(7 bytes) = 750ns digest(4097 bytes) = 7625ns This shaves 400ms of a FIT image boot that uses sha256 as digest for the images referenced by the selected configuration: barebox@imx8mn-old:/ time bootm -d kernel-a Dryrun. Aborted. time: 998ms barebox@imx8mn-new:/ time bootm -d kernel-a Dryrun. Aborted. time: 601ms Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Link: https://lore.barebox.org/20230526063746.1155297-8-a.fatoum@pengutronix.de Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
* Merge branch 'for-next/arm64-virt'Sascha Hauer2023-05-241-1/+1
|\
| * ARM: Remove qemu_virt64_defconfigSascha Hauer2023-05-021-1/+1
| | | | | | | | | | | | | | The ARM64 QEMU Virt board is now enabled in multi_v8_defconfig. Remove the now unnecessary defconfig. Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
* | ARM: Add _32 suffix to aarch32 specific filenamesSascha Hauer2023-05-221-1/+4
|/ | | | | | | | | | | | Several files in arch/arm/cpu/ have 32bit and 64bit versions. The 64bit versions have a _64 suffix, but the 32bit versions have none. This can be confusing sometimes as one doesn't know if a file is 32bit specific or common code. Add a _32 suffix to the 32bit files to avoid this confusion. Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de> Reviewed-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
* arm: error out if __LINUX_ARM_ARCH__ is undefinedAhmad Fatoum2023-04-171-0/+1
| | | | | | | | | | | | | | | | | With recent multiarch (really, multiplatform) rework, oldconfig will reask users what platforms they want to build for. The default is N, so holding return (or an olddefconfig) will just disable all boards and with it all CPUs leading to a cryptic torrent of: arch/arm/include/asm/swab.h:31:28: warning: "__LINUX_ARM_ARCH__" is not defined, evaluates to 0 [-Wundef] 31 | #if defined(__KERNEL__) && __LINUX_ARM_ARCH__ >= 6 | ^~~~~~~~~~~~~~~~~~ Make user experience a bit better by printing an error message instead. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Link: https://lore.barebox.org/20230414171421.1745965-1-a.fatoum@pengutronix.de Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
* ARM: add multi-arch supportSascha Hauer2023-03-071-24/+24
| | | | | | | | | | | | | | This allows to build barebox for multiple arch/arm/mach-* for architectures that allow it. To get there we convert machine-y to a list. Architectures that want to support multi-arch must make sure that all boards support multi PBL support (i.e. select HAVE_PBL_MULTI_IMAGES). Also they must make sure that all initcalls can gracefully be executed on other SoCs. Two architectures that fulfil these requirements are added right from the start: i.MX and Rockchip. Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
* ARM: Drop mach dir include pathSascha Hauer2023-03-061-4/+0
| | | | | | arch/arm/mach-*/include/mach no longer exists, drop the include path. Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
* ARM: Makefile: Drop board-ySascha Hauer2023-03-031-20/+1
| | | | | | | | | board-y has the only purpose to include a global config.h file directly with #include <config.h>. This is no longer needed, let the remaining users include their config.h directly. Link: https://lore.barebox.org/20230302111606.1054037-11-s.hauer@pengutronix.de Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
* ARM: drop unused am35xx code in MakefileSascha Hauer2023-03-031-13/+0
| | | | | | | | All users of AM335x SPI images are multi-image, so the SPI image generation code in arch/arm/Makefile is unused. Drop it. Link: https://lore.barebox.org/20230302111606.1054037-10-s.hauer@pengutronix.de Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
* ARM: drop unused mvebu code in MakefileSascha Hauer2023-03-031-21/+0
| | | | | | | | All mvebu boards are multi-image, so they don't need image generation in arch/arm/Makefile anymore. Drop it. Link: https://lore.barebox.org/20230302111606.1054037-9-s.hauer@pengutronix.de Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
* ARM: drop unused zynq code in MakefileSascha Hauer2023-03-031-10/+0
| | | | | | | | The Zynq board in tree is converted to multi-image, thus doesn't need image generation in arch/arm/Makefile anymore. Drop it. Link: https://lore.barebox.org/20230302111606.1054037-8-s.hauer@pengutronix.de Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
* ARM: i.MX: Remove old boardsSascha Hauer2023-03-021-17/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This removes a bunch of old boards that nobody showed interest in for a long time: Freescale boards ================ MACH_IMX21ADS MACH_IMX27ADS MACH_FREESCALE_MX25_3STACK MACH_FREESCALE_MX35_3STACK MACH_FREESCALE_MX53_SMD Eukrea boards ============= MACH_EUKREA_CPUIMX25 MACH_EUKREA_CPUIMX27 MACH_EUKREA_CPUIMX35 MACH_EUKREA_CPUIMX51SD Garz+Fricke boards ================== MACH_NESO MACH_GUF_CUPID Phytec boards ============= MACH_PCM037 MACH_PCM043 Amazon boards ============= MACH_KINDLE3 All these boards have not been converted to device tree nor do they support multi-image generation. As they are becoming a maintenance burden remove them now. A board can always be added back once it is ported to support the recent barebox interfaces. Link: https://lore.barebox.org/20230302105225.943524-2-s.hauer@pengutronix.de Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
* ARM: remove samsung archSascha Hauer2023-03-011-13/+0
| | | | | | | | | arch/arm/mach-samsung/ hasn't seen any active maintenance or interest for a long time. Remove the architecture, boards and defconfig files Reviewed-by: Marco Felsch <m.felsch@pengutronix.de> Link: https://lore.barebox.org/20230228135727.1602351-2-s.hauer@pengutronix.de Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
* ARM: fix GCC 11.x build failures for ARMv7Ian Abbott2022-04-121-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | Building barebox for ARMv7 with GCC 11.x results in errors similar to the following: CC common/state/state_variables.o {standard input}: Assembler messages: {standard input}:1535: Error: selected processor does not support `rev r3,r3' in Thumb mode {standard input}:1576: Error: selected processor does not support `rev r3,r3' in Thumb mode Or: CC common/state/state_variables.o {standard input}: Assembler messages: {standard input}:1405: Error: selected processor does not support `rev r3,r3' in ARM mode {standard input}:1453: Error: selected processor does not support `rev r3,r3' in ARM mode The problem is that the compiler option `-march=armv7-a` is not being chosen by "arch/arm/Makefile", but rather the fallback options `-march=armv5t -Wa,-march=armv7-a` are being chosen. Appending `-msoft-float` to `KBUILD_CPPFLAGS` earlier in "arch/arm/Makefile" before the tests for supported `-march` options seems to fix the problem. Signed-off-by: Ian Abbott <abbotti@mev.co.uk> Link: https://lore.barebox.org/20220408170154.114526-1-abbotti@mev.co.uk Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
* treewide: add SPDX-License-Identifier for Kbuild/KconfigAhmad Fatoum2022-01-051-0/+2
| | | | | | | | | | | | | | | To verify only Kconfig/Makefile is touched: git show --numstat --format=oneline HEAD | grep -v 'Kconfig\|Makefile' will print only arch/powerpc/Kbuild. To verify nothing unexpected is added: git show -U0 | grep '^-[^-]\|^+[^+]' | sort -u Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Link: https://lore.barebox.org/20220103120539.1730644-3-a.fatoum@pengutronix.de Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
* ARM: i.MX: Remove KaRo TX51 board supportSascha Hauer2021-05-171-1/+0
| | | | | | | | So far nobody cared enough to convert the board to multiimage support. Given that nobody seems to care for this board remove it and reduce the number of defconfigs by one. Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
* Merge branch 'for-next/arm-qemu-virt64'Sascha Hauer2021-03-231-1/+0
|\
| * ARM64: qemu-virt64: migrate to generic DT imageAhmad Fatoum2021-03-171-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Current qemu-virt64 barebox support doesn't look much like what's offered on physical boards. It's not relocatable, lacks PBL and doesn't use device tree. As qemu-system-aarch64 -M virt -kernel already supplies an external device tree, we could just replace all existing support with BOARD_ARM_GENERIC_DT, which builds a barebox image that reuses an externally passed device tree. The 32-bit ARM VIRT support has some board code for host name setting and overlay applying to handle environment and state on flash. We could do without that, given the new virtio-blk support, but the code is already there, so reuse it and drop all current virt64-specific board code. As the barebox ELF image resulting from the build can no longer be directly booted as before and only with -kernel, not -bios, rename the Kconfig symbol, so existing users can notice this during build. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
* | ARM: remove Calxeda Highbank supportSascha Hauer2021-03-221-1/+0
|/ | | | | | | | | | Calxeda went out off business back in 2013. The Calxeda Highbank port did not get any active maintenance since then. Since the Highbank support plays some tricks with devices trees passed to barebox from the firmware it becomes a maintenance burden. Remove Highbank support altogether. Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
* ARM: drop no-thumb-interwork in EABI modeStefan Agner2021-02-161-1/+1
| | | | | | | | | | | | | | According to GCC documentation -m(no-)thumb-interwork is meaningless in AAPCS configurations. Also clang does not support the flag: clang-5.0: error: unknown argument: '-mno-thumb-interwork' Just drop -mno-thumb-interwork in AEABI configuration. Signed-off-by: Stefan Agner <stefan@agner.ch> [afa: ported from Linux 22905a24306c ("ARM: 8766/1: drop no-thumb-interwork in EABI mode")] Signed-off-by: Ahmad Fatoum <ahmad@a3f.at> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
* Merge branch 'for-next/module'Sascha Hauer2020-07-271-1/+5
|\
| * arm: module: Allow modules outside of bl rangeDavid Dgien2020-07-011-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Unlike the Linux kernel, barebox does not have a dedicated heap for storing modules. Therefore, if the system memory configuration places the general heap further away than can be reached by a 'bl' instruction (24 bits of address, or 16 MiB), then the module relocations will fail due to being out of range. Allocate PLTs when loading modules so that jumps and calls whose targets are too far away for their relative offsets to be encoded in the instructions themselves can be bounced via veneers in the module's PLT. The modules will use slightly more memory, but after rounding up to page size, the actual memory footprint is usually the same. Adoption of Linux commits: 66e94ba3c8ea ARM: kernel: avoid brute force search on PLT generation 1031a7e674d1 ARM: kernel: sort relocation sections before allocating PLTs 05123fef0982 ARM: kernel: allocate PLT entries only for external symbols 35fa91eed817 ARM: kernel: merge core and init PLTs 7d485f647c1f ARM: 8220/1: allow modules outside of bl range Signed-off-by: David Dgien <dgienda125@gmail.com> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
| * arm: makefile: Fix compiler flag variableDavid Dgien2020-07-011-1/+1
| | | | | | | | | | | | | | | | | | | | In order for ARM modules to compile with the correct relocation types, they must be built without -fPIE. Move -fPIE from KBUILD_CPPFLAGS to KBUILD_CFLAGS_KERNEL so that the flag is only included when compiling files being built into the barebox image. Signed-off-by: David Dgien <dgienda125@gmail.com> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
* | kbuild: remove AS variableMasahiro Yamada2020-06-171-2/+0
|/ | | | | | | | | | | | | | | | The assembler files in the barebox are *.S instead of *.s, so they must be preprocessed. Since 'as' of GNU binutils is not able to preprocess, we always use $(CC) as an assembler driver. Remove AS variable. Linux also removed AS. See Linux commits: aa824e0c962b ("kbuild: remove AS variable") 1ca0c2f61211 ("kbuild: remove unused AS assignment") Signed-off-by: Masahiro Yamada <masahiroy@kernel.org> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
* arch: remove KBUILD_SRC checks from arch MakefileMasahiro Yamada2020-05-121-4/+0
| | | | | | | You can always add $(srctree)/ to the mach include path. Signed-off-by: Masahiro Yamada <masahiroy@kernel.org> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
* kbuild: prefix compiler flag variables with KBUILD_Masahiro Yamada2020-04-271-17/+17
| | | | | | | | | | | | | | | | | | | | | | | | In old days, Linux also used to use well-known variables such CFLAGS, CPPFLAGS, etc. They were prefixed with KBUILD_ presumably for preventing users from overriding them accidentally. Rename as follows: CFLAGS -> KBUILD_CFLAGS AFLAGS -> KBUILD_AFLAGS CPPFLAGS -> KBUILD_CPPFLAGS LDFLAGS -> KBUILD_LDFLAGS HOSTCFLAGS -> KBUILD_HOSTCFLAGS HOSTCXXFLAGS -> KBUILD_HOSTCXXFLAGS HOSTLDFLAGS -> KBUILD_HOSTLDFLAGS HOST_LOADLIBES -> KBUILD_HOSTLDLIBS HOSTCFLAGS, HOSTCXXFLAGS, HOSTLDFLAGS, HOSTLDLIBS are re-used to allow users to pass-in additional flags to the host compiler. Signed-off-by: Masahiro Yamada <masahiroy@kernel.org> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
* images: Use separate LDFLAGS for PBLChristian Eggers2020-02-101-0/+7
| | | | | | | | | | | | | | | When setting CONFIG_PBL_RELOCATABLE=y (selected by PBL_MULTI_IMAGES) and CONFIG_RELOCATABLE=n (trying to reduce image size), the PBL is also linked with "-static" instead of "-pie". The result is a non-working PBL. As a side effect, also get rid of erroneous "-Map barebox.map" when linking the PBL. Only changed for ARM, are any other platforms affected? Signed-off-by: Christian Eggers <ceggers@arri.de> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
* ARM: Compile with -fPIESascha Hauer2019-11-121-0/+3
| | | | | | | | | | | | | | | | Early code in barebox often runs at an address the binary is not linked at. This causes problems for example when simple initializations in a switch are converted to an array lookup (-ftree-switch-conversion). These arrays are then addressed where they are linked at. Some code where this is known to cause problems is already compiled with -fno-tree-switch-conversion. This however is limited to single files. This patch compiles barebox with -fPIE enabled. This causes such tables to be looked up PC relative rather than with its absolute address. This makes the -fno-tree-switch-conversion and -fno-jump-table options unnecessary. Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
* ARM: remove now unused PBL codeSascha Hauer2019-10-011-8/+0
| | | | | | | Single PBL is now built as part of the multi PBL images, so drop the now unused single PBL code. Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
* ARM: NETX: remove architectureSascha Hauer2019-09-231-13/+0
| | | | | | | NETX support has been removed from the Kernel, so there's no point in supporting it in barebox any longer. Remove the architecture. Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
* ARM: stm32mp1: rename to stm32mpAhmad Fatoum2019-06-131-1/+1
| | | | | | | | | | | | Serial and clk driver both depend on CONFIG_ARCH_STM32MP1, so either the Kconfig symbol or their depend needs to change. Patches posted by the vendor to Linux, U-Boot and their BSP Yocto-Layer speak of a STM32MP-Family of which the STM32MP1 is the first series, thus rename the arch by dropping the 1. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
* arch: add KBUILD_DEFCONFIG to allow "make defconfig"Masahiro Yamada2019-05-131-0/+1
| | | | | | | | | | | | | | | | | | | | Currently, "make defconfig" is only supported for sandbox and x86. I set KBUILD_DEFCONFIG to support "make defconfig" where I was able to find a suitable one. nios2 and openrisc have a single generic_defconfig, so it is definitely good for KBUILD_DEFCONFIG. For arm, mips, I assume qemu is a preferred choice over a real board. blackfin has only one defconfig. Since it is inactive (it is gone in Linux), so no more defconfig will come in. I am not sure about ppc and riscv, so I did not touch them. Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
* Merge branch 'for-next/stm32'Sascha Hauer2019-04-091-0/+1
|\
| * ARM: Add initial STM32MP1 supportSascha Hauer2019-03-131-0/+1
| | | | | | | | | | | | | | | | | | | | | | This adds initial STMicroelectronics MP1 support along with support for the DK2 devel board. Only very basic support: - UART - SDRAM memory base/size - No 1st stage support Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
* | Merge branch 'for-next/layerscape'Sascha Hauer2019-04-081-0/+1
|\ \
| * | ARM: Add basic Layerscape supportSascha Hauer2019-03-131-0/+1
| |/ | | | | | | | | | | | | | | | | | | This adds basic Layerscape support: - Makefile/Kconfig - Register maps - errata workarounds Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
* / ARM: Makefile: restore kindle3 imxcfg-y settingAlexander Kurz2019-03-181-0/+1
|/ | | | | | | | | Commit 45f38c1a846f ("ARM: Makefile: Drop unnecessary imxcfg-y settings") dropped the imximg generation for the kindle3. This device is not covered within multiimage support and can be configured with kindle3_defconfig. Signed-off-by: Alexander Kurz <akurz@blala.de> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
* ARM: Makefile: Drop unnecessary imxcfg-y settingsSascha Hauer2019-01-161-3/+0
| | | | | | | For boards built with multiimage support imxcfg-y is not needed. Remove it for these boards. Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
* Merge branch 'for-next/ultrascale'Sascha Hauer2019-01-151-0/+5
|\
| * ARM: zynqmp: add support for Xilinx ZCU104 boardMichael Tretter2018-12-101-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Add support for the Xilinx Zynq Ultrascale+ MPSoC architecture (ZynqMP) and the Xilinx ZCU104 board. Barebox is booted as BL33 in EL-1 and expects that a BL2 (i.e. the FSBL) already took care of initializing the RAM. Also for debug_ll, the UART is expected to be already setup correctly. Thus, you have to add the Barebox binary to a boot image as described in "Chapter 11: Boot and Configuration" of "Zynq Ultrascale+ Device Technical Reference Manual". Signed-off-by: Michael Tretter <m.tretter@pengutronix.de> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
| * ARM: aarch64: compile with general-regs-onlyMichael Tretter2018-12-101-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | Without this flag, gcc generates code to save the Q/V registers to the stack for handling the va_list in pr_print(). Saving the registers is useless, as the registers are never restored, but accessing the registers to save them hangs the CPU. Follow the Linux arch/arm64/Makefile and use the general-regs-only flag to prevent usage of floating point and Advanced SIMD register. Signed-off-by: Michael Tretter <m.tretter@pengutronix.de> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
* | ARM: CCMX51: Switch to multiimage supportAlexander Shiyan2019-01-031-1/+0
|/ | | | | | | | | | | | This is a cumulative patch for the Digi ConnectCore CCMX51 SOM. It includes: - Switch board to devicetree probe. - Add MMC update handler. - Switch to multiimage support. - Cleanup and optimize board code. Signed-off-by: Alexander Shiyan <shc_work@mail.ru> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
* Merge branch 'for-next/imx'Sascha Hauer2018-04-061-2/+0
|\
| * i.MX53/TX53: rework to dts based bootMichael Grzeschik2018-03-261-2/+0
| | | | | | | | | | | | | | | | Since nobody likes to use platformcode based machines any more, we also switch this one to use dts based booting. Signed-off-by: Michael Grzeschik <m.grzeschik@pengutronix.de> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
* | ARM: aarch64: disable 32bit boot commandsSascha Hauer2018-04-041-1/+0
| | | | | | | | | | | | | | | | The 32bit boot support is full of legacy cruft. While it should be possible to merge the aarch64 support there, a fresh start looks more promising. Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
generated by cgit v1.2.3 (git 2.39.1) at 2024-04-19 14:31:35 +0000