aboutsummaryrefslogtreecommitdiffstats
path: root/package/boot/uboot-mvebu
Commit message (Collapse)AuthorAgeFilesLines
* uboot-mvebu: update to v2022.07Andre Heider2022-08-063-33/+22
| | | | | | | | | | | | | | | | | - Release announcement: https://lore.kernel.org/u-boot/20220711134339.GV1146598@bill-the-cat/ - Changes between 2022.04 and 2022.07: https://source.denx.de/u-boot/u-boot/-/compare/v2022.04...v2022.07?from_project_id=531 Remove one upstreamed patch and add patch to fix issue with sunxi tool as it uses function from newer version libressl (3.5.0). Signed-off-by: Andre Heider <a.heider@gmail.com> Tested-by: Josef Schlehofer <pepe.schlehofer@gmail.com> [Turris Omnia] (cherry picked from commit 24bf6813bad98a8eba5430ed5e4da89d54797274) Signed-off-by: Josef Schlehofer <pepe.schlehofer@gmail.com> [Improve commit message]
* uboot-mvebu: update to version v2022.04Josef Schlehofer2022-06-148-524/+2
| | | | | | | | | | | | | | | Release announcement: https://lore.kernel.org/u-boot/20220404143253.GQ14476@bill-the-cat/ Release notes between tags: https://source.denx.de/u-boot/u-boot/-/compare/v2022.01...v2022.04?from_project_id=531 All patches were removed, since they are included in this release. Run tested: Turris Omnia, mvebu/cortex-a9, OpenWrt daily snapshots Signed-off-by: Josef Schlehofer <pepe.schlehofer@gmail.com> (cherry picked from commit 4f51f1fc9b3597d24de442cfff253fddce478d17)
* uboot-mvebu: remove enabled CONFIG_CMD_SETEXPRJosef Schlehofer2022-06-141-7/+0
| | | | | | | | | | | | | | | | | | | | | | | We don't need to make sure that we want to have enabled CONFIG_CMD_SETEXPR by default, since this is already done in U-boot [1]. This was actually needed only for clearfog board [2], which was added in commit: da0005a6d08ae33d958a6d8a6c0c12dc07b5b2b8 ("uboot-mvebu: add patch to enable setexpr for clearfog boards) and send to U-boot to fix it properly. After a while, there was added support for Turris Omnia, which uses setexpr as well [3], but for this board, there are no fixes needed in U-boot and that's why we can remove this option here. It is helpful with shell scripting. If some downstream distributions are using it, they should correct it in defconfig for related boards. [1] https://source.denx.de/u-boot/u-boot/-/blob/e95afa56753cebcd20a5114b6d121f281b789006/cmd/Kconfig#L1504 [2] https://github.com/openwrt/openwrt/blob/852126680e21edc71c0c66561ae5a6d7479dcc67/target/linux/mvebu/image/clearfog.bootscript#L7 [3] https://github.com/openwrt/openwrt/blob/852126680e21edc71c0c66561ae5a6d7479dcc67/target/linux/mvebu/image/turris-omnia.bootscript#L2 Signed-off-by: Josef Schlehofer <pepe.schlehofer@gmail.com> (cherry picked from commit 69cef74c671cb7fa738a5a4c9a283c29f45326c7)
* uboot-mvebu: add patch to enable setexpr for clearfog boardsJosef Schlehofer2022-06-141-0/+31
| | | | | | | | | | | | | | | Option CMD_SETEXPR is already default in U-boot [1], since this was disabled since initial version for this board, there is send this patch to U-boot mailing list to enable it. It is required to use in OpenWrt bootscript for these boards [2]. [1] https://source.denx.de/u-boot/u-boot/-/blob/e95afa56753cebcd20a5114b6d121f281b789006/cmd/Kconfig#L1504 [2] https://github.com/openwrt/openwrt/blob/852126680e21edc71c0c66561ae5a6d7479dcc67/target/linux/mvebu/image/clearfog.bootscript#L7 Signed-off-by: Josef Schlehofer <pepe.schlehofer@gmail.com> (cherry picked from commit b3c2072504867b8ca00dde37f531edf0cfbe3359)
* uboot-mvebu: backport patch to fix eMMCRobert Marko2022-04-051-0/+64
| | | | | | | | | | | v2022.01 has a regression that broke eMMC usage on most if not all Armada SoC-s, thus breaking boards like uDPU which use eMMC for storage. Fix it by backporting a recent upstream patch. Fixes: 782d4c8306c8 ("uboot-mvebu: update to version 2022.01") Signed-off-by: Robert Marko <robert.marko@sartura.hr> (cherry picked from commit a70383080694f26d13db8341a83261f6b1c45f12)
* uboot-mvebu: backport patch to fix nvme detail crashJosef Schlehofer2022-03-051-0/+92
| | | | | | | | | | | | | | | | | | | | | Steps to reproduce: 1. Insert NVMe disk with a reduction to Turris Omnia 2. Go to U-boot 3. Run these two commands: a) ``nvme scan`` b) ``nvme detail`` 4. Wait for crash This is backported from U-boot upstream repository. It should be included in the upcoming release - 2022.04 [1]. It was tested on Turris Omnia, mvebu, cortex-a9, OpenWrt master. [1] https://patchwork.ozlabs.org/project/uboot/patch/20211209100639.21530-1-pali@kernel.org/ Signed-off-by: Josef Schlehofer <pepe.schlehofer@gmail.com> [Export the patch from U-Boot git] Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* uboot-mvebu: backport pending patches for Marvell A38xJosef Schlehofer2022-02-203-0/+152
| | | | | | | | | | | | | | | | | | | | | | | 100-ddr-marvell-a38x-fix-BYTE_HOMOGENEOUS_SPLIT_OUT-deci.patch [1]: SoC Marvell A38x is used in Turris Omnia, and we thought that with recent fiddling around DDR training to fix it once for all, there were reproduced the issue in the upcoming new revision Turris Omnia boards. 101-arm-mvebu-spl-Add-option-to-reset-the-board-on-DDR-t.patch [2]: This is useful when some board may occasionally fail with DDR training, and it adds the option to reset the board on the DDR training failure 102-arm-mvebu-turris_omnia-Reset-the-board-immediately-o.patch [3]: This enables the option CONFIG_DDR_RESET_ON_TRAINING_FAILURE (added by 101 patch), so the Turris Omnia board is restarted immediately, and it does not require to reset the board manually or wait 120s for MCU to reset the board [1] https://patchwork.ozlabs.org/project/uboot/patch/20220217000837.13003-1-kabel@kernel.org/ [2] https://patchwork.ozlabs.org/project/uboot/patch/20220217000849.13028-1-kabel@kernel.org/ [3] https://patchwork.ozlabs.org/project/uboot/patch/20220217000849.13028-2-kabel@kernel.org/ Signed-off-by: Josef Schlehofer <pepe.schlehofer@gmail.com>
* uboot-mvebu: backport two patches for Marvell A38xJosef Schlehofer2022-02-032-0/+214
| | | | | | | | | | | This solves issue with DDR training on Turris Omnia. Log: ******** DRAM initialization Failed (res 0x1) ******** DDR3 Training Sequence - FAILED ERROR ### Please RESET the board ### Signed-off-by: Josef Schlehofer <pepe.schlehofer@gmail.com>
* uboot-mvebu: Add U-boot for Turris OmniaJosef Schlehofer2022-02-031-0/+9
| | | | | | * Add U-boot support for Turris Omnia Signed-off-by: Josef Schlehofer <pepe.schlehofer@gmail.com>
* uboot-mvebu: update to version 2022.01Josef Schlehofer2022-02-031-2/+2
| | | | | Signed-off-by: Josef Schlehofer <pepe.schlehofer@gmail.com> Tested-by: Andre Heider <a.heider@gmail.com> # ESPRESSObin
* uboot-mvebu: update to v2021.10Andre Heider2021-11-271-2/+2
| | | | Signed-off-by: Andre Heider <a.heider@gmail.com>
* u-boot.mk: always link host libraries staticAndre Heider2021-10-241-14/+0
| | | | | | | | Host libraries are only build static, so let's pass --static to pkg-config globally and remove the then unnecessary patches doing exactly that individually. Signed-off-by: Andre Heider <a.heider@gmail.com>
* u-boot.mk: fix pkg-config usageAndre Heider2021-10-241-2/+0
| | | | | | | | Using Host/Exports doesn't work as intended, explicitly add the required vars so that u-boot finds the required libraries when building its tools. Signed-off-by: Andre Heider <a.heider@gmail.com>
* uboot-mvebu: update to v2021.07Andre Heider2021-07-252-4/+4
| | | | | | | Refresh the patches. Switch to AUTORELEASE while at it. Signed-off-by: Andre Heider <a.heider@gmail.com>
* uboot-mvebu: update to v2021.01Andre Heider2021-01-304-533/+2
| | | | | | | u-boot now detects emmc variants at runtime, we don't need to build seperate binaries anymore. Signed-off-by: Andre Heider <a.heider@gmail.com>
* uboot-mvebu: don't install 64bit binariesAndre Heider2020-10-111-0/+4
| | | | | | | u-boot binaries are not useful for these boards, they need to be combined with atf for a proper firmware. Signed-off-by: Andre Heider <a.heider@gmail.com>
* uboot-mvebu: don't default to enable a3700 buildsAndre Heider2020-10-111-3/+0
| | | | | | | u-boot binaries for this SoC are only required for the atf package, disable them per default so they don't get build unnecessarily. Signed-off-by: Andre Heider <a.heider@gmail.com>
* uboot-mvebu: don't add CONFIG_NET_RANDOM_ETHADDR to defconfigAndre Heider2020-10-111-1/+0
| | | | | | | All targets already enable it in their defconfig with the used u-boot version. Signed-off-by: Andre Heider <a.heider@gmail.com>
* uboot-mvebu: update to v2020.10Andre Heider2020-10-118-186/+40
| | | | | | Remove merged patches and update the emmc set. Signed-off-by: Andre Heider <a.heider@gmail.com>
* uboot-mvebu: add support for espressobinAndre Heider2020-09-186-0/+663
| | | | | | | This builds two u-boot binaries: one for boards without eMMC and one with. Signed-off-by: Andre Heider <a.heider@gmail.com>
* uboot-mvebu: update to v2020.10-rc4Andre Heider2020-09-185-52/+9
| | | | | | | | TODO: switch to release v2020.10 once released. Remove one merged patch, refresh the rest. Signed-off-by: Andre Heider <a.heider@gmail.com>
* uboot-mvebu: add uboot for helios 4Alberto Bursi2020-07-171-0/+8
| | | | | | add u-boot for Helios 4 NAS Signed-off-by: Alberto Bursi <bobafetthotmail@gmail.com>
* mvebu: uDPU: switch default kernel and U-Boot PHY modeJakov Petrina2020-05-091-0/+43
| | | | | | | | | | | | | | | | Certain SFP modules (most notably Nokia GPON ones) first check connectivity on 1000base-x, and switch to 2500base-x afterwards. This is considered a quirk so the phylink switches the interface to 2500base-x as well. However, after power-cycling the uDPU device, network interface/SFP module will not work correctly until the module is re-seated. This patch resolves this issue by forcing the interface to be brought up in 2500base-x mode by default. Signed-off-by: Jakov Petrina <jakov.petrina@sartura.hr> Signed-off-by: Vladimir Vid <vladimir.vid@sartura.hr> Cc: Luka Perkov <luka.perkov@sartura.hr>
* uboot-mvebu: point to UBOOT_CONFIG when setting optionsTomasz Maciej Nowak2020-03-011-4/+4
| | | | | | | | | The BUILD_VARIANT might differ from UBOOT_CONFIG, so point to a file we are actually changing. Being here let's call 'Build/Configure/U-Boot' definition, instead of definig the same command. This'll be more future proof, if U-Boot configuration procedure will change. Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
* uboot-mvebu: add uDPU boardVladimir Vid2019-11-212-2/+22
| | | | | | | | | | * add u-boot support for uDPU * add line to copy u-boot binary to STAGING_DIR_IMAGE, this can later be used as BL33 variable required for ATF build * add patch to increase max gunzip size in mvebu_armada-37xx.h which is required for booting the itb recovery images Signed-off-by: Vladimir Vid <vladimir.vid@sartura.hr>
* uboot-mvebu: add support for Macronix mx25u12835f flashVladimir Vid2019-11-011-0/+10
| | | | | | Some of A3700 boards use mx25u12835f, specifically uDPU and ESPRESSObin v7. Signed-off-by: Vladimir Vid <vladimir.vid@sartura.hr>
* u-boot-mvebu: bump to 2019.04Vladimir Vid2019-06-281-2/+2
| | | | | | | | | Some devices and packages require newer version of u-boot to work properly, update u-boot to keep up with 4.19 kernel. Signed-off-by: Vladimir Vid <vladimir.vid@sartura.hr> [re-added missing commit message] Signed-off-by: Petr Štetiar <ynezz@true.cz>
* mvebu: align device names to vendor_device formatTomasz Maciej Nowak2019-05-111-1/+1
| | | | | | | | | | Add vendors in device names and also rename few device names, for easier identyfying potential firmware to flash. The vendor and device string is mainly derived from model/compatipble string in dts from particular device, but since not all devices are well described, some of the renames follow marketing names. Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
* uboot-mvebu: fix build on hosts lacking pkg-configJo-Philipp Wich2018-05-231-0/+3
| | | | | | | | | | | | The uboot-mvebu package incorrectly used the host pkg-config for the tool build parts, which broke the build on systems lacking pkg-config and only worked by accident on those that have it installed. Export the host-build specific environment variables for the uboot build to redirect pkg-config invocations to our staged host build pkg-config in buildroot. Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* uboot-mvebu: Fix build with libressl 2.7.2Hauke Mehrtens2018-04-291-0/+14
| | | | | | | When libressl was linked the libpthread was missing, add it in addition. Fixes: 2c192b69163f ("tools/libressl: update to version 2.7.2") Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* u-boot-mvebu: update to 2018.03Josua Mayer2018-03-313-136/+2
| | | | | | | | | This release brings various improvements to clearfog support, such as distro-boot. Obsoletes: 0002-clearfog-reset-usom-onboard-1512-phy.patch 0003-clearfog-enable-distro-boot-code.patch Signed-off-by: Josua Mayer <josua.mayer97@gmail.com>
* u-boot-mvebu: set configuration options in MakefileJosua Mayer2018-03-313-52/+8
| | | | | | | | | | | CONFIG_* variables can easily be set by overriding Build/Configure. so set NET_RANDOM_ETHADDR=y and CMD_SETEXPR=y here. This replaces the following patches: 0001-clearfog-generate-random-MAC-address.patch 0004-clearfog-enable-setexpr-command-by-default.patch Signed-off-by: Josua Mayer <josua.mayer97@gmail.com>
* mvebu: Add subtarget for Cortex A9 buildHauke Mehrtens2018-03-101-0/+1
| | | | | | This is in preparation for adding a subtarget for the Cortex A53 later. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* uboot-mvebu: fix build ; use the build's tools/libresslAlexandru Ardelean2018-02-103-251/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Since I have no openssl-dev on my machine, I first get this error: ``` tools/kwbimage.c:21:10: fatal error: openssl/bn.h: No such file or directory #include <openssl/bn.h> ``` After removing the UBOOT_MAKE_FLAGS the next error is: ``` tools/kwbimage.c:40:6: error: conflicting types for ‘EVP_MD_CTX_cleanup’ void EVP_MD_CTX_cleanup(EVP_MD_CTX *ctx) ``` After removing the OpenSSL patches the next error is: ``` HOSTLD tools/dumpimage /usr/bin/ld: cannot find -lssl /usr/bin/ld: cannot find -lcrypto collect2: error: ld returned 1 exit status scripts/Makefile.host:108: recipe for target 'tools/dumpimage' failed make[5]: *** [tools/dumpimage] Error 1 ``` So, the final part is to add the build system's HOST_LDFLAGS to the UBOOT_MAKE_FLAGS. (which was done in the previous commit) Then the image builds. Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
* uboot-mvebu: add OpenSSL compat patchesMarko Ratkaj2017-09-252-0/+249
| | | | | | | | | | | | | | Fixes the following build issue: "undefined reference to `EVP_MD_CTX_create'" From: Jelle van der Waa <jelle@vdwaa.nl> The rsa_st struct has been made opaque in 1.1.x, add forward compatible code to access the n, e, d members of rsa_struct. EVP_MD_CTX_cleanup has been removed in 1.1.x and EVP_MD_CTX_reset should be called to reinitialise an already created structure. Signed-off-by: Marko Ratkaj <marko.ratkaj@sartura.hr>
* uboot-mvebu: fix SETEXPR redefinition warningMarko Ratkaj2017-09-251-12/+8
| | | | Signed-off-by: Marko Ratkaj <marko.ratkaj@sartura.hr>
* uboot-mvebu: add missing UBOOT_MAKE_FLAGS variableMarko Ratkaj2017-09-251-0/+2
| | | | | | This patch removes "/bin/sh: HOSTCPPFLAGS: command not found" errors douring build. Signed-off-by: Marko Ratkaj <marko.ratkaj@sartura.hr>
* u-boot-mvebu: clearfog: enable setexpr commandJosua Mayer2017-05-301-0/+28
| | | | Signed-off-by: Josua Mayer <josua.mayer97@gmail.com>
* u-boot-mvebu: clearfog: implement distro-bootJosua Mayer2017-05-305-49/+126
| | | | | | | Add a patchfile that implements distro-boot and is meant to go upstream Also make the other patches git-am'able for easier maintenance. Signed-off-by: Josua Mayer <josua.mayer97@gmail.com>
* u-boot-mvebu: update to 2017.03Josua Mayer2017-05-304-15/+26
| | | | Signed-off-by: Josua Mayer <josua.mayer97@gmail.com>
* mvebu: add ClearFog Base supportMarko Ratkaj2017-05-141-1/+1
| | | | | | | | | | Add support for SolidRun ClearFog Base board. The base model is a smaller version of ClearFog Pro without the DSA switch, replacing it with a second copper gigabit port, and only one PCIe socket. Signed-off-by: Marko Ratkaj <marko.ratkaj@sartura.hr>
* mvebu: ClearFog renamed upstream to ClearFog ProMarko Ratkaj2017-05-141-1/+1
| | | | | | The conventional model is now known as the "Clearfog Pro" Signed-off-by: Marko Ratkaj <marko.ratkaj@sartura.hr>
* mvebu: put u-boot images into image staging directoryJo-Philipp Wich2017-01-271-2/+2
| | | | | | | | | | | | Do not put the u-boot images into the kernel build directory as this directory might get removed after kernel updates while the u-boot packages InstallDev recipe is not getting re-executed because it is still considered current, leading to image build failures later on due to missing u-boot images. To ensure that built bootloader images persist over kernel version updates in the buildroot, put them into the new STAGING_DIR_IMAGE directory. Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* uboot-mvebu: switch to u-boot.mkFelix Fietkau2017-01-242-82/+12
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* uboot-mvebu: enable loader with the default profileFelix Fietkau2017-01-081-1/+1
| | | | | | Fixes build error Signed-off-by: Felix Fietkau <nbd@nbd.name>
* treewide: clean up download hashesFelix Fietkau2016-12-161-1/+1
| | | | | | Replace *MD5SUM with *HASH, replace MD5 hashes with SHA256 Signed-off-by: Felix Fietkau <nbd@nbd.name>
* uboot-mvebu: reset the 88E1512 PHY to make the wan port workJonas Gorski2016-09-261-0/+32
| | | | | Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com> Acked-by: Felix Fietkau <nbd@nbd.name>
* uboot-mvebu: make hidden and be m for clearfog to fix IB failing to add itJonas Gorski2016-09-261-3/+5
| | | | | | | | | | | | | Uboot-mvebu isn't a real package, which will break the image builder when it tries to install it during the packing step. Instead of cleafog selecting it through its default packages, make it default to m if the clearfog profile is selected. This will ensure it is always build, but never added to the rootfs. This fixes creating images for clearfog with IB. Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com> Acked-by: Felix Fietkau <nbd@nbd.name>
* uboot-mvebu: also install into KDIR to ensure it packaged in IBJonas Gorski2016-09-261-0/+3
| | | | | | | | The clearfog image requires u-boot, so package it into KDIR to make sure it is available in imageBuilder. Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com> Acked-by: Felix Fietkau <nbd@nbd.name>
* mvebu: fix boot script for booting from mmcFelix Fietkau2016-09-023-1/+44
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
generated by cgit v1.2.3 (git 2.25.1) at 2024-07-06 10:46:45 +0000