aboutsummaryrefslogtreecommitdiffstats
path: root/package/boot
Commit message (Collapse)AuthorAgeFilesLines
...
* at91bootstrap: at91bootstrap default selectionSandeep Sheriker Mallikarjun2018-01-091-16/+16
| | | | | | | | | | | The fixes following problems 1. changing prefix at91bootstrap to AT91bootstrap will fix the default selection of at91bootstrap for the selected sama5 subtarget. 2. fixed missing default selection of sama5d4 nand flash for the selected sama5d4 subtarget. 3. corrected at91bootstrap Title name. Signed-off-by: Sandeep Sheriker Mallikarjun <sandeepsheriker.mallikarjun@microchip.com>
* uboot-at91: fix build after fpu activationSandeep Sheriker Mallikarjun2018-01-091-1/+1
| | | | | | | | | neon and VFPv4 support is added to this target and uboot-at91 build fails due to TARGET_CFLAGS -mfloat-abi set to hard. as a fix, setting uboot-at91 CFLAGS -mfloat-abi=soft. Fixes: 01cc6bd495f ("at91: sama5: activate fpu") Signed-off-by: Sandeep Sheriker Mallikarjun <sandeepsheriker.mallikarjun@microchip.com>
* kirkwood: sort occurrences of boardame alphabeticallyMathias Kresin2018-01-091-5/+5
| | | | | | | This restores the alphabetical sort that was present before the renaming of boardname. Signed-off-by: Mathias Kresin <dev@kresin.me>
* uboot-envtools: add pogoplug v4Alberto Bursi2018-01-091-1/+2
| | | | | | add pogoplug v4 envs support in uboot-envtools Signed-off-by: Alberto Bursi <alberto.bursi@outlook.it>
* uboot-kirkwood: add uboot for pogoplug v4Alberto Bursi2018-01-092-1/+1581
| | | | | | | | | | | | | | | | | | | | | add an uboot able to boot a kernel in an ubi partition This uboot also has a "recovery" feature, before booting from flash it will try to boot a initramfs image called "initramfs.bin" from a FAT32-formatted USB drive connected to the USB 2.0 port. (u-boot lacks drivers for usb 3.0 controllers) Just rename the initramfs image and place it on the usb drive, the uboot will load it. In case there is no USB drive or no such file is found, the uboot will boot from internal flash. The whole check takes less than a second, boot times are not impacted. Signed-off-by: Alberto Bursi <alberto.bursi@outlook.it>
* kirkwood: sync image filename with boardnameMathias Kresin2018-01-091-3/+11
| | | | | | | | | | Use <manufacturer>_<modelname> as image name. Use the BOARD_NAME variable to ensure that the former used boardname is still used as the subdirectory name for the sysupgrade-tar image, to not break sysupgrade from earlier versions. Signed-off-by: Mathias Kresin <dev@kresin.me>
* kirkwood: use the generic board detectMathias Kresin2018-01-091-7/+7
| | | | | | | Drop the target specific detection function in favour of the generic one provided by base-files. Signed-off-by: Mathias Kresin <dev@kresin.me>
* uboot-kirkwood: fix default u-boot selectionMathias Kresin2018-01-091-0/+2
| | | | | | | | | Build the Seagate GoFlexHome u-boot for the Seagate GoFlexNet as well. The name clearly indicates that the u-boot can be used for both boards Build the Zyxel NSA310 u-boot if the NSA310B image is selected. Signed-off-by: Mathias Kresin <dev@kresin.me>
* kirkwood: drop support for orphaned boardsMathias Kresin2018-01-093-31/+2
| | | | | | | No image build code for the Guruplug, Sheevaplug and NSA310S exists. Drop support for the boards for now. Signed-off-by: Mathias Kresin <dev@kresin.me>
* uboot-envtool: remove superfluous + sign from PKG_BUILD_DEPENDSMatthias Schiffer2018-01-071-1/+1
| | | | | | A + sign does not have meaning in build depends. Signed-off-by: Matthias Schiffer <mschiffer@universe-factory.net>
* layerscape: fix package downloadHauke Mehrtens2017-12-211-2/+2
| | | | | | | | | | | | | | | | The git hash was changed for multiple layerscape packages without changing the version number. The LEDE build system will not download the packages again if the old version is already there and so some people and the build bots are using wrong version of some packages. Use PKG_SOURCE_DATE instead of PKG_VERSION to generate packages with the date and the first charterers of the git hash. This will change the file name and make the build system download them again, also if in future the git hash is changed the file name will change and trigger a new download. This should fix a problem spotted by build bot. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* ramips: drop LinkIt Smart 7688 Duo userspace supportMathias Kresin2017-12-211-1/+0
| | | | | | | | | | The LinkIt Smart 7688/LinkIt Smart 7688 Duo are identical beside the extra ATmega32U4 - accessible via UART - on the the Duo. Since all relevant hardware is identical, drop the Duo special handling in userspace. Signed-off-by: Mathias Kresin <dev@kresin.me>
* uboot-layerscape-armv8_32b: fix package downloadHauke Mehrtens2017-12-201-2/+2
| | | | | | | | | | | | | | | | In commit 2b1ec44dbd3cd3 ("layerscape: add ls1012afrdm device support") The git revision and the mirror hash for this package was updated to a version which includes ls1012afrdm-uboot.bin, but the file name at dl/uboot-layerscape-armv8_32b-2017.09.tar.xz staid the same. This way most user did not download the new version but used the old file. Convert this package to the normal git clone parameters by using PKG_SOURCE_DATE instated of PKG_VERSION, now the file name in dl also contains the git hash and should change every time the git hash is updated. This should fix a problem spotted by build bot. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* lantiq: sync image filename with boardnameMathias Kresin2017-12-161-47/+47
| | | | | | | | | | | | | Use <manufacturer>_<modelname> as image name. Use the BOARD_NAME variable to ensure that the former used boardname is still used as the subdirectory name for the sysupgrade-tar image, to not break sysupgrade from earlier versions. While at it, normalise the image filenames by using only lower case characters and bin as file extension for sysupgrade images. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: use the compatible string as board nameMathias Kresin2017-12-161-5/+5
| | | | | | | | | | | Use the first compatible string as board name in userspace. Add the new board name as well as the former used board name to the image metadata to keep compatibilty with already deployed installations. Don't add the former used boardname for boards which exists only in master or evaluation boards. Signed-off-by: Mathias Kresin <dev@kresin.me>
* merge: targets: update image generation and targetsZoltan HERPAI2017-12-081-1/+1
| | | | Signed-off-by: Zoltan HERPAI <wigyori@uid0.hu>
* uboot-sunxi: fix build of HAOYU Electronics Marsboard A10Hauke Mehrtens2017-11-231-1/+2
| | | | | | | | The uboot target is named MarsBoard_A10 and it was not build at all. This fixes a build problem seen by the build bot. Fixes: 6a3565985fde ("sunxi: Added profile for HAOYU Electronics Marsboard A10") Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* uboot-sunxi: add NanoPi M1 Plus boardLuis Araneda2017-11-171-0/+7
| | | | Signed-off-by: Luis Araneda <luaraneda@gmail.com>
* add PKG_CPE_ID ids to package and toolsAlexander Couzens2017-11-171-0/+1
| | | | | | | | | | | CPE ids helps to tracks CVE in packages. https://cpe.mitre.org/specification/ Thanks to swalker for CPE to package mapping and keep tracking CVEs. Acked-by: Jo-Philipp Wich <jo@mein.io> Signed-off-by: Alexander Couzens <lynxis@fe80.eu>
* kobs-ng: add header for integer definitionsSimon Wunderlich2017-11-161-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | My compilation failed because of missing uint.* definitions: In file included from mtd.h:33:0, from bootstream.c:35: BootControlBlocks.h:58:2: error: unknown type name 'uint8_t' uint8_t m_u8DataSetup; ^ BootControlBlocks.h:59:2: error: unknown type name 'uint8_t' uint8_t m_u8DataHold; ^ BootControlBlocks.h:60:2: error: unknown type name 'uint8_t' uint8_t m_u8AddressSetup; ^ BootControlBlocks.h:61:2: error: unknown type name 'uint8_t' uint8_t m_u8DSAMPLE_TIME; Adding the header file fixes the problem. Signed-off-by: Simon Wunderlich <sw@simonwunderlich.de> [fold changes into 001-compile.patch] Signed-off-by: Mathias Kresin <dev@kresin.me>
* uboot-envtools: add support for Wallys DR342Piotr Dymacz2017-11-141-0/+1
| | | | Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
* layerscape: add ls1012afrdm device supportYangbo Lu2017-11-103-3/+59
| | | | | | | | The QorIQ FRDM-LS1012A Board is an ultra-low-cost development platform for QorIQ LS1012A Series Network Processors built on ARM Cortex-A53 processor. Signed-off-by: Yangbo Lu <yangbo.lu@nxp.com>
* layerscape: enlarge ext4 rootfs size to 30MBYangbo Lu2017-11-104-5/+5
| | | | | | This patch is to enlarge ext4 rootfs size to 30MB. Signed-off-by: Yangbo Lu <yangbo.lu@nxp.com>
* layerscape: stop pfe before starting up kernelYangbo Lu2017-11-102-3/+3
| | | | | | | For ls1012ardb, pfe should be stopped before starting up kernel. Signed-off-by: Yangbo Lu <yangbo.lu@nxp.com>
* layerscape: update u-boot to LSDK-1709-update-103017 tagYangbo Lu2017-11-102-4/+4
| | | | | | Updated u-boot to LSDK-1709-update-103017 tag. Signed-off-by: Yangbo Lu <yangbo.lu@nxp.com>
* layerscape: support LEDE boot for ls1088ardb/ls2088ardbYangbo Lu2017-11-102-0/+112
| | | | | | | Added u-boot patches to support LEDE boot for ls1088ardb and ls2088ardb. Signed-off-by: Yangbo Lu <yangbo.lu@nxp.com>
* layerscape: support all-in-one firmware for ls1088ardb/ls2088ardbYangbo Lu2017-11-101-1/+13
| | | | | | | Suppport all-in-one firmware for ls1088ardb/ls2088ardb by integrating u-boot/rcw/mc/dpl/restool. Signed-off-by: Yangbo Lu <yangbo.lu@nxp.com>
* sunxi: add Orange Pi 2 supportZoltan HERPAI2017-11-061-0/+7
| | | | | | | | | | | | | - H3 @ 1.3 GHz - 1GiB DDR3 - 10/100Mbps Ethernet - Realtek RTL8189ETV wifi - 4 USB 2.0 Difference to the "Orange Pi Plus" is the lack of Gbit ethernet and lack of onboard flash. Signed-off-by: Zoltan HERPAI <wigyori@uid0.hu>
* sunxi: Added profile for HAOYU Electronics Marsboard A10Kayo Phoenix2017-11-061-0/+6
| | | | | | | | | The MarsBoard was a short-lived credit-card sized, extendable board with an Allwinner A10 SoC. http://linux-sunxi.org/MarsBoard_A10 Signed-off-by: Kayo Phoenix <kayo@illumium.org> [Forward-ported to new target layout:] Signed-off-by: Zoltan HERPAI <wigyori@uid0.hu>
* uboot-kirkwood: update to 2017.09Paul Wassi2017-11-039-101/+160
| | | | | | | | | | Upgrade uboot-kirkwood to upstream release 2017.09 Catch up with upstream and move configuration options from simple defines to Kconfig, as otherwise dependencies would not be resolved and code would not compile. Tested-by: Alberto Bursi <alberto.bursi@outlook.it> Signed-off-by: Paul Wassi <p.wassi@gmx.at>
* uboot-sunxi: Backport fix for stale CONFIG_SUNXIG_GMAC referencesFlorian Fainelli2017-10-235-28/+84
| | | | | | | | | | This backports the upstream commit fixing stale references to CONFIG_SUNXI_GMAC which have been later replaced by CONFIG_SUN7I_GMAC. This fixes the designware MAC pinmuxing on e.g: Lamobo R1. Refresh patches while we are at it. Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
* uboot-envtools: add support for Nokia WI2A-AC200iFelix Fietkau2017-10-191-0/+3
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* at91bootstrap: remove manual copy of binaries to BIN_DIRSandeep Sheriker Mallikarjun2017-10-141-2/+10
| | | | | | | removed copying of binaries to BIN_DIR during install and using default/install to install binaries to BIN_DIR folder. Signed-off-by: Sandeep Sheriker Mallikarjun <sandeepsheriker.mallikarjun@microchip.com>
* at91bootstrap: Add BUILD_SUBTARGET variableSandeep Sheriker Mallikarjun2017-10-141-2/+3
| | | | | | | | | Added sama5 to BUILD_SUBTARGET variable.This will populate at91bootstrap menu options in bootloader menu only when SAMA5 devices are selected as SUBTARGET and to avoid showing up this menu when legacy device is selected as SUBTARGET and fixed typo mistake: sama5d3 -> sama5d2. Signed-off-by: Sandeep Sheriker Mallikarjun <sandeepsheriker.mallikarjun@microchip.com>
* uboot-at91: multiple build fixesHauke Mehrtens2017-10-141-21/+23
| | | | | | | | | | | This fixes the following problems: * Add BUILD_DEVICES for legacy subtarget * Use features from u-boot.mk for sama5 subtarget This is mainly done by changing the prefix from uboot to U-Boot. This makes them depend on the sama5 subtarget and not selectable for the legacy subtarget any more Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* uboot-sunxi: build for NanoPi NEODaniel Golle2017-10-081-0/+7
| | | | Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* layerscape: update packages with LSDK git treesYangbo Lu2017-10-075-14/+173
| | | | | | | | | | | | | | | | | NXP Layerscape LSDK had set up its own open source web site and github for release. https://lsdk.github.io https://github.com/qoriq-open-source This patch is to update rcw/fman_ucode/u-boot packages with LSDK git trees. Also add some patches of packages to support LEDE. Since ARMv8 32-bit u-boot images are same with ARMv8 64-bit images but 64-bit toolchain couldn't be used for 32-bit targets, we still use a private tree for ARMv8 32-bit u-boot images. This is in plan to move this private tree to NXP Layerscape github. Signed-off-by: Yangbo Lu <yangbo.lu@nxp.com>
* layerscape: rename subtargets and update makefile filesYangbo Lu2017-10-072-10/+10
| | | | | | | | Rename subtargets 32b/64b with armv8_32b/armv8_64b which are more proper, and update makefile files. There also will be other subtargets added in the future, like armv7. Signed-off-by: Yangbo Lu <yangbo.lu@nxp.com>
* rbcfg: Implement CPU frequency controlThibaut VARENE2017-10-073-4/+139
| | | | | | | | | | | | | | | | | | | | | | This patch implements CPU frequency control as found on several routerboard devices. Supported SoCs: - QCA953X - AR9344 Tested on hAP lite and mAP lite (QCA953x): steps of 50MHz Tested on LHG 5 (AR9344): steps of 50MHz On unsupported hardware, this patch is a NOP: it will not alter the new field. "rbcfg help" will display an empty "cpu_freq" help listing. "rbcfg show" will not show the cpu_freq field. "rbcfg set/get cpu_freq" will return an error code. Signed-off-by: Thibaut VARENE <hacks@slashdirt.org> [adjusted subject] Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* sunxi: add Orange Pi R1 supportHauke Mehrtens2017-10-013-0/+237
| | | | | | | | | | | | | | | The following features are working and tested: * both Ethernet ports * MMC * LED The following features are not working: * Wifi (There is a crappy driver we could port) * SPI flash (I haven't looked into this) I haven't tried out the rest. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* sunxi: improve A20 Lime2 upload speedLucian Cristian2017-09-302-1/+14
| | | | Signed-off-by: Lucian Cristian <lucian.cristian@gmail.com>
* ramips: improve Xiaomi Mi Router 3G supportKevin Darbyshire-Bryant2017-09-281-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This commit improves support for the Xiaomi Mi Router 3G originally added in commit 6e283cdc0da25928f8148805ebef7f8f2b769ee8 Improvements: - Remove software watchdog as hardware watchdog now working as per commit 3fbf3ab44f5cebb22e30a4c8681b13341feed6a6 for all mt7621 devices. - Reset button polarity corrected - length of press determines reboot (short press) vs. reset to defaults (long press) behaviour. - Enable GPIO amber switch port LEDs on board rear - lit indicates 1Gbit link and blink on activity. Green LEDs driven directly by switch indicating any link speed and tx activity. - USB port power on/off GPIO exposed as 'usbpower' - Add access to uboot environment settings for checking/setting uboot boot order preference from user space. Changes: - Front LED indicator is physically made of independent Yellow/Amber, Red & Blue LEDs combined via a plastic 'lightpipe' to a front panel indicator, hence the colour behaviour is similar to an RGB LED. RGB LEDs are not supported at this time because they produce colour results that do not then match colour labels, e.g. enabling 'mir3g:red' and 'mir3g:blue' would result in a purple indicator and we have no such label for purple. The yellow, red & blue LEDs have been split out as individual yellow, red & blue status LEDs, with yellow being the default status LED as before and with red's WAN and blue's USB default associations removed. - Swapped order of vlan interfaces (eth0.1 & eth0.2) to match stock vlan layout. eth0.1 is LAN, eth0.2 is WAN - Add 'lwlll' vlan layout to mt7530 switch driver to prevent packet leakage between kernel switch init and uci swconfig uboot behaviour & system 'recovery' uboot expects to find bootable kernels at nand addresses 0x200000 & 0x600000 known by uboot as "system 1" and "system 2" respectively. uboot chooses which system to hand control to based on 3 environment variables: flag_last_success, flag_try_sys1_failed & flag_try_sys2_failed last_success represents a preference for a particular system and is set to 0 for system 1, set to 1 for system 2. last_success is considered *if* and only if both try_sys'n'_failed flags are 0 (ie. unset) If *either* failed flags are set then uboot will attempt to hand control to the non failed system. If both failed flags are set then uboot will check the uImage CRC of system 1 and hand control to it if ok. If the uImage CRC of system is not ok, uboot will hand control to system 2 irrespective of system 2's uImage CRC. NOTE: uboot only ever sets failed flags, it *never* clears them. uboot sets a system's failed flag if that system's was selected for boot but the uImage CRC is incorrect. Fortunately with serial console access, uboot provides the ability to boot an initramfs image transferred via tftp, similarly an image may be flashed to nand however it will flash to *both* kernels so a backup of stock kernel image is suggested. Note that the suggested install procedure below set's system 1's failed flag (stock) thus uboot ignores the last_success preference and boots LEDE located in system 2. Considerable thought has gone into whether LEDE should replace both kernels, only one (and which one) etc. LEDE kernels do not include a minimal rootfs and thus unlike the stock kernel cannot include a method of controlling uboot environment variables in the event of rootfs mount failure. Similarly uboot fails to provide an external mechanism for indicating boot system failure. Installation - from stock. Installation through telnet/ssh: - copy lede-ramips-mt7621-mir3g-squashfs-kernel1.bin and lede-ramips-mt7621-mir3g-squashfs-rootfs0.bin to usb disk or wget it from LEDE download site to /tmp - switch to /extdisks/sda1/ (if copied to USB drive) or to /tmp if wgetted from LEDE download site - run: mtd write lede-ramips-mt7621-mir3g-squashfs-kernel1.bin kernel1 - run: mtd write lede-ramips-mt7621-mir3g-squashfs-rootfs0.bin rootfs0 - run: nvram set flag_try_sys1_failed=1 - run: nvram commit - run: reboot Recovery - to stock. Assuming you used the above installation instructions you will have a stock kernel image in system 1. If it can be booted then it may be used to perform a stock firmware recovery, thus erasing LEDE completely. From a 'working' LEDE state (even failsafe) Failsafe only: - run: mount_root - run: sh /etc/uci-defaults/30_uboot-envtools Then do the steps for 'All' All: - run: fw_setenv flag_try_sys2_failed 1 - run: reboot The board will reboot into system 1 (stock basic kernel) and wait with system red light slowly blinking for a FAT formatted usb stick with a recovery image to be inserted. Press and hold the reset button for around 1 second. Status LED will turn yellow during recovery and blue when recovery complete. Signed-off-by: Kevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk>
* 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>
* sunxi: add Olimex A20-OLinuXino-LIME2-eMMCLucian Cristian2017-09-243-0/+113
| | | | | | Signed-off-by: Lucian Cristian <lucian.cristian@gmail.com> [replaced u-boot patch with original version from u-boot git] Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* arm-trusted-firmware-sunxi: depend on sunxi targetStijn Tintel2017-09-201-0/+1
| | | | | | | | | The arm-trusted-firmware-sunxi package is only used by the Allwinner A64, so only make it selectable for its subtarget sunxi/cortexa53. Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be> Acked-by: Hauke Mehrtens <hauke@hauke-m.de> Reviewed-by: Jonas Gorski <jonas.gorski@gmail.com>
* at91bootstrap: New package at91bootstrapSandeep Sheriker Mallikarjun2017-09-202-0/+173
| | | | | | | | | at91bootstrap is a second-level bootloader for Microchip(Atmel AT91) SoCs. It provides a set of algorithms to manage the hardware initialization and to download the main application or a third-level bootloader(i.e. uboot) from specified boot media to main memory and execute it. Signed-off-by: Sandeep Sheriker Mallikarjun <sandeepsheriker.mallikarjun@microchip.com>
* uboot-at91: Add support for SAMA5D4 Xplained boardSandeep Sheriker Mallikarjun2017-09-201-2/+22
| | | | | | | Add support for SAMA5D4 Xplained board and options to select & build u-boot configs for different media storage. Signed-off-by: Sandeep Sheriker Mallikarjun <sandeepsheriker.mallikarjun@microchip.com>
* uboot-at91: Add support for SAMA5D2 Xplained boardSandeep Sheriker Mallikarjun2017-09-201-1/+16
| | | | | | | Add support for SAMA5D2 Xplained board and options to select & build u-boot configs for different media storage. Signed-off-by: Sandeep Sheriker Mallikarjun <sandeepsheriker.mallikarjun@microchip.com>
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-04 06:36:52 +0000