aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* x86: add preinit hook for bootloader upgradeTomasz Maciej Nowak2020-03-012-1/+21
| | | | | | | | | | | | | | | | This commit fills the void for current OpenWrt installations which will be still on old bootloader version even after "x86: add bootloader upgrade on sysupgrade", since it performs bootloader upgrade only on sysupgrade. To keep all OpenWrt deploynents on the same GRUB version, add preinit hook, which will perform upgrade of the bootloader on first boot after sysupgrade. It's temporary solution and should be deleted, when the first release including this hook will no longer be supported by OpenWrt team. We can assume that all installations should be on current bootolader version and from there sysupgrade routine will be sufficient. Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
* x86: add bootloader upgrade on sysupgradeTomasz Maciej Nowak2020-03-013-3/+33
| | | | | | | | | | | | | | Currently bootloader always stays on the same version as when first written to boot medium (not true if partition layout changed, which will trigger sysupgrade process to write full disk image). That creates inconveniences as it always stays with same features or/and bugs. Users wishing to add support to additional modules or new version, would need to write the whole image, potentially destroying previous system configuration. To fix these, this commit adds additional routine to sysupgrade which upgrades unconditionally the bootloader to the latest state provided by OpenWrt. Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
* x86: image: cleanup before creating imageTomasz Maciej Nowak2020-03-011-0/+2
| | | | | | | | | There can be some leftovers from other image recipes, if the same directory names are used and multiply image types are selected. Therefore remove directories used in the recipe, before contents for the image are prepared. Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
* kernel: iio: add fxos8700 driver supportTim Harvey2020-03-011-0/+50
| | | | | | | | Adds various kernel modules for Freescale FXOS8700 3-axis accelerometer. Signed-off-by: Tim Harvey <tharvey@gateworks.com> [added missing commit description] Signed-off-by: Petr Štetiar <ynezz@true.cz>
* kernel: iio: add st-accel driver modulesTim Harvey2020-03-011-0/+54
| | | | | | | | Adds kernel modules for various STMicroelectronics accelerometers. Signed-off-by: Tim Harvey <tharvey@gateworks.com> [added missing commit description] Signed-off-by: Petr Štetiar <ynezz@true.cz>
* imx6: 5.4: dts: backport lsm9ds1 imu support for GW553xTim Harvey2020-03-011-0/+73
| | | | | | | | | Add one node for the accel/gyro i2c device and another for the separate magnetometer device in the lsm9ds1. Signed-off-by: Tim Harvey <tharvey@gateworks.com> [commit subject/description tweaks, kernel version in patch filename] Signed-off-by: Petr Štetiar <ynezz@true.cz>
* kernel: 5.4: backport fxos8700 accel support from 5.5Tim Harvey2020-03-011-0/+912
| | | | | | | | | | | | Backport kernel module from 5.5 for FXOS8700CQ, which is a small, low-power, 3-axis linear accelerometer and 3-axis magnetometer combined into a single package. The device features a selectable I2C or point-to-point SPI serial interface with 14-bit accelerometer and 16-bit magnetometer ADC resolution along with smart-embedded functions. Signed-off-by: Tim Harvey <tharvey@gateworks.com> [added commit description] Signed-off-by: Petr Štetiar <ynezz@true.cz>
* kernel: can: add MCP251x CAN controller module supportTim Harvey2020-03-011-0/+17
| | | | | | | | Adds kernel module for Microchip MCP251x SPI CAN controller. Signed-off-by: Tim Harvey <tharvey@gateworks.com> [added missing commit description] Signed-off-by: Petr Štetiar <ynezz@true.cz>
* mkrasimage: fix segmentation faultMichael T Farnworth2020-03-011-9/+10
| | | | | | | | | | | | | Code was attempting to determine the size of the file before it was actually known and allocating insufficient memory space. Images above a certain size caused a segmentation fault. Moving the calloc() ensured ensured that large images didn't result in a buffer overflow on memcpy(). Signed-off-by: Michael T Farnworth <michael@turf.org> [fixed name in From to match one in SoB] Signed-off-by: Petr Štetiar <ynezz@true.cz>
* tools/pkgconf: Run pkg-config wrapper through shellcheckRosen Penev2020-03-011-1/+4
| | | | | | | | Mainly quoting fixes. Separated parameters by \ for easier readability. Signed-off-by: Rosen Penev <rosenp@gmail.com>
* tools/pkg-config: Replace with pkgconfRosen Penev2020-03-014-16/+46
| | | | | | | | | | | | | | | | | | | | | | pkgconf is a newer, actively maintained implementation of pkg-config that supports more aspects of the pkg-config file specification and provides a library interface that applications can use to incorporate intelligent handling of pkg-config files into themselves (such as build file generators, IDEs, and compilers). Through its pkg-config compatibility interface (activated when it is run as "pkg-config"), it also can completely replace the original implementation. It is also lighterweight and does not require glib2, as pkg-config does. On other distros, pkgconf is symlinked to pkg-config. For simplicity here, it is renamed to pkg-config.real, as in the original package. Initial results have been positive. As before, pkgconf works as long as the pkg-config files point to the proper paths. Signed-off-by: Rosen Penev <rosenp@gmail.com> [backported upstream fix for Meson] Signed-off-by: Petr Štetiar <ynezz@true.cz>
* 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>
* mvebu: uDPU: drop patch compiling dtbTomasz Maciej Nowak2020-03-012-11/+1
| | | | | | | | | If device recipe has specified DEVICE_DTS variable, the dtb is built anyway by OpenWrt buildroot image rules. Drop the patch and adjust the location of compiled dtb. Cc: Scott Roberts <ttocsr@gmail.com> Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
* mvebu: image: rework uDPU-firmware recipeTomasz Maciej Nowak2020-03-011-3/+9
| | | | | | | | | Tar has ability to change current dir, so use that instead additional command invocation. Also being here, change tar arguments to make final archive reproducible. Cc: Scott Roberts <ttocsr@gmail.com> Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
* mvebu: uDPU: clean package selectionTomasz Maciej Nowak2020-03-011-3/+1
| | | | | | | | | This device receipe selects bunch of packages which some are re-defined, unnecessary or irrelevant. Clean them up, so only basic functionality persist. Cc: Scott Roberts <ttocsr@gmail.com> Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
* mvebu: image: keep global DTS_DIR intactTomasz Maciej Nowak2020-03-011-1/+2
| | | | | | | | Don't rewrite global DTS_DIR, instead, use proper variable for specifying devices dts directory. For consistency, also specify the variable in default profile, as suggested by Adrian Schmutzler. Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
* tools: Fix "lib" symlink created inside $(STAGING_DIR_HOST)/libJeffery To2020-03-011-1/+1
| | | | | | | | | | | | | | | | | | | Currently, if "make tools/install" is called after tools have already been installed, a symbolic link named "lib" will be created inside $(STAGING_DIR_HOST)/lib, pointing to "lib" (i.e. itself). During tools/prepare, a "lib64" symlink is created inside $(STAGING_DIR_HOST) that points to "lib" (also inside $(STAGING_DIR_HOST)). If tools/prepare is called and the "lib64" symlink already exists, then ln will treat it as a directory and instead create a symlink named "lib" inside of that directory. This adds the -n option for ln so that $(STAGING_DIR_HOST)/lib64 is always treated as a normal file (the link name), not as a directory. Signed-off-by: Jeffery To <jeffery.to@gmail.com>
* build: Fix directory symlinks not removed when cleaning STAGING_DIRJeffery To2020-03-011-1/+1
| | | | | | | | | | | | | | | | | | Currently, a symbolic link whose target is a directory will not be removed when cleaning packages from STAGING_DIR. In the first cleaning pass in scripts/clean-package.sh, the -f test for a directory symlink returns false (because the link target is a directory) and so the symlink is not removed. In the second pass, the -d test returns true for a directory symlink, but the symlink is not removed by rmdir because rmdir only removes (real) directories. This updates clean-package.sh to remove all non-directories (including symbolic links) in the first pass. Signed-off-by: Jeffery To <jeffery.to@gmail.com>
* build: Remove STAGING_DIR_HOST references for InstallDev/UninstallDevJeffery To2020-03-011-3/+3
| | | | | | | | | | | | | Build/InstallDev no longer places a file list in $(STAGING_DIR_HOST)/packages; this change removes the creation of $(STAGING_DIR_HOST)/packages and the attempted removal of a STAGING_DIR_HOST file list during package clean. This also changes the host directory passed to Build/UninstallDev from $(STAGING_DIR_HOST) to $(STAGING_DIR)/host, to match the directory passed to Build/InstallDev. Signed-off-by: Jeffery To <jeffery.to@gmail.com>
* base-files: Add /etc/shinit for non-login shell initJeffery To2020-03-014-20/+24
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Because /etc/profile (and ~/.profile) are read by login shells only, aliases and functions defined there are not available to non-login shells, e.g. when using screen or tmux. If the ENV environment variable exists (exported by /etc/profile or ~/.profile) and references an existing file, then all interactive shells (login or non-login) will read that file as well. This sets the ENV environment variable in /etc/profile, pointing to /etc/shinit. This also adds /etc/shinit, which: * Contains alias and function definitions originally in /etc/profile * Sources /etc/mkshrc if the user is using mksh (also originally in /etc/profile), as /etc/mkshrc is meant for all interactive shells * Sources ~/.mkshrc if the user is using mksh, to compensate for the fact that mksh will not read ~/.mkshrc if ENV is set * Sources ~/.shinit if the user is not using mksh This also removes the shebang from /etc/profile, as the file is sourced, not executed. Signed-off-by: Jeffery To <jeffery.to@gmail.com>
* ppp: activate PIE ASLR by defaultPetr Štetiar2020-03-011-0/+1
| | | | | | | | | | | | | | This activates PIE ASLR support by default when the regular option is selected. Size increase on imx6: 112681 ppp_2.4.8-2_arm_cortex-a9_neon.ipk 121879 ppp_2.4.8-2_arm_cortex-a9_neon.ipk = 9198 diff Acked-by: Alexander Couzens <lynxis@fe80.eu> Signed-off-by: Petr Štetiar <ynezz@true.cz>
* libpcap: activate PIE ASLR by defaultStijn Tintel2020-03-011-0/+1
| | | | | | | | | | | This activates PIE ASLR support by default when the regular option is selected. This is required to enable PIE ASLR support by default in ppp, as it fails to build without it, on x86/64. The .so file size stays identical. Suggested-by: Felix Fietkau <nbd@nbd.name> Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* ar71xx: correct AVM FRITZ Repeater 450E WPS button flagDavid Bauer2020-03-011-1/+1
| | | | | | | | | The AVM FRITZ!WLAN Repeater 450E's WPS button is not active low. Correct the active low flag to avoid unintenional activation of failsafe mode on boot. Signed-off-by: David Bauer <mail@david-bauer.net>
* linux-5.4: backport ARM symbol export fixÁlvaro Fernández Rojas2020-03-011-0/+60
| | | | | | | Fixes the following warning for ARM targets: WARNING: "return_address" [vmlinux] is a static EXPORT_SYMBOL_GPL Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* linux-5.4: backport modpost upstream patchesÁlvaro Fernández Rojas2020-03-014-11/+121
| | | | | | | | | Fixes modpost Segmentation Fault with bcm2708 and bcm2709: MODPOST vmlinux.o Segmentation fault make[6]: *** [scripts/Makefile.modpost:66: __modpost] Error 139 Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm27xx: bcm2708: refresh linux 5.4 configÁlvaro Fernández Rojas2020-03-011-18/+30
| | | | | | I missed this when adding linux 5.4 support Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* mpc85xx: disable kernel uImage generationDavid Bauer2020-03-012-31/+42
| | | | | | | | | | The previous workaround for the unsupported mkimage xz compression leads to the TP-Link TL-WDR4900s simpleImage bootwrapper being gzip compressed, which does not fit the kernel partition. Removing the uImage gerneration works around this problem. Signed-off-by: David Bauer <mail@david-bauer.net>
* treewide: move commonly disabled symbols to generic configDavid Bauer2020-03-019-22/+6
| | | | | | | Move new commonly disabled kernel 5.4 symbols to the generic kernel configuration. Signed-off-by: David Bauer <mail@david-bauer.net>
* mpc85xx: add missing kernel symbolsDavid Bauer2020-03-013-0/+6
| | | | | | | These symbols were previously not set. Define their state to avoid potentially breaking builds. Signed-off-by: David Bauer <mail@david-bauer.net>
* build: add xargs as prerequisiteKevin Darbyshire-Bryant2020-02-291-0/+5
| | | | | | | | | | | | | Build system needs an 'xargs' that supports '-r' which darwin doesn't. Homebrew installs a 'gxargs' with the findutils package so look for 'gxargs' as well as 'xargs' This is a bit of a 'fun' corner case anyway. xargs is only required by the build if 'CONFIG_AUTOREMOVE' is set and after the build system has built 'tools/findutils' we have a fully working xargs for host anyway. Until that time we have to rely on the host's xargs implementation. Signed-off-by: Kevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk>
* apm821xx: remove gpio-interrupt cruftChristian Lamparter2020-02-291-6/+0
| | | | | | | | | | | This hunk became obsolete the moment when our gpio-button-hotplug learned how to deal with interrupt-supported gpio buttons. The gpio driver never supported interrupt handling, so these properties never served any use (outside of a enhanced ppc4xx-gpio driver that was dropped). Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* mvebu: fix build regression due to neon-asm ghash moduleChristian Lamparter2020-02-291-7/+3
| | | | | | | | | | | | | | This patch fixes the regression caused by adding the NEON variant of the ghash as the default ghash package package: > ERROR: module '[...]/arch/arm/crypto/ghash-arm-ce.ko' is missing. > modules/crypto.mk:286: recipe for target > '[...]/kmod-crypto-ghash_4.19.106-1_aarch64_cortex-a53.ipk' failed This patch limits the scope to the ARM32/cortexa9 target of mvebu. Fixes: 285df63efc70 ("kernel: build neon-asm version of ghash module") Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* bcm27xx: add linux 5.4 supportÁlvaro Fernández Rojas2020-02-29456-1/+179443
| | | | | | Tested on bcm2710 (Raspberry Pi 3B). Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm27xx: update kernel configsÁlvaro Fernández Rojas2020-02-293-0/+57
| | | | Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm27xx: update to latest patches from RPi foundationÁlvaro Fernández Rojas2020-02-2940-0/+264
| | | | Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm27xx-gpu-fw: update to latest versionÁlvaro Fernández Rojas2020-02-291-14/+14
| | | | Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* spi: ath79: remove spi-master setup and cleanup assignmentDavid Bauer2020-02-291-0/+28
| | | | | | | | | | | This removes the assignment of setup and cleanup functions for the ath79 target. Assigning the setup-method will lead to 'setup_transfer' not being assigned in spi_bitbang_init. Also drop the redundant cleanup assignment, as this also happens in spi_bitbang_init. Signed-off-by: David Bauer <mail@david-bauer.net>
* mpc85xx: move NAND symbol to target configDavid Bauer2020-02-296-3/+5
| | | | | | | | | All mpc85xx subtargets utilize NAND, thus enable NAND support target-wide. Fixes: 1287bb48dc72 ("mpc85xx: fix build with kernel 5.4") Signed-off-by: David Bauer <mail@david-bauer.net>
* mpc85xx: fix build with kernel 5.4David Bauer2020-02-285-6/+64
| | | | | | | | | | This fixes some outstanding issues with the Kernel 5.4 build: * Adds missing support patch for the Enterasys WS-AP3710i * Fixes incorrect NAND symbols * Adds patch for broken image wrapping Signed-off-by: David Bauer <mail@david-bauer.net>
* apm821xx: 5.4: add important NAND symbolsChristian Lamparter2020-02-281-0/+3
| | | | | | | | This patch adds important NAND config symbols. These are necessary as otherwise the devices won't find the rootfs on the NAND chips. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* ipq40xx: 5.4: refresh patches and configChristian Lamparter2020-02-2823-206/+49
| | | | | | | | | | | This patch just refreshes the 5.4 patches. It seems as if 070-v4.20-soc-qcom-spm-add-SCM-probe-dependency.patch is already applied, so drop it. It also does a quick make kernel_oldconfig to get rid of unneeded symbols. [Looks like USB and Ethernet need some more work]. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* kernel: 5.4: add unconfigured symbolsChristian Lamparter2020-02-281-0/+5
| | | | | | | This patch adds a few more symbols that I found that need disabling in order to not break the automatic build. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* kernel: build arm/neon-optimized sha1/512 modulesEneas U de Queiroz2020-02-281-0/+35
| | | | | | | | | | | This builds the regular arm and arm-neon asm optmized modules for sha1 and sha512, for targets that set CONFIG_ARM_CRYPTO. On ip40xx, the arm-asm version of sha1 improves performance by 5% over the generic C implementation; sha1-neon is 25% faster than generic, and sha512-neon, 259%. Signed-off-by: Eneas U de Queiroz <cotequeiroz@gmail.com>
* kernel: build neon-asm version of ghash moduleEneas U de Queiroz2020-02-281-1/+12
| | | | | | | | This alone improves AES-GCM performance by up to 50% on ipq40xx. This is enabled for targets that support neon and set CONFIG_ARM_CRYPTO: imx6, ipq40xx, and mvebu. Signed-off-by: Eneas U de Queiroz <cotequeiroz@gmail.com>
* ipq40xx: qce - add fixes for AES ciphersEneas U de Queiroz2020-02-2818-0/+1866
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This backports commits from master that fix AES ciphers when using the qce driver: - A couple of simple fixes for CTR and XTS modes used with AES: * 041-crypto-qce-fix-ctr-aes-qce-block-chunk-sizes.patch * 042-crypto-qce-fix-xts-aes-qce-key-sizes.patch - A fix for a bug that affected cases when there were more entries in the input sg list than necessary to actually encrypt, resulting in failure in gcm, where the authentication tag is present after the encryption data: * 043-crypto-qce-save-a-sg-table-slot-for-result-buf.patch - A fix to update the IV buffer passed to the driver from the kernel: * 044-crypto-qce-update-the-skcipher-IV.patch - A patch that reduces memory footprint and driver initialization by only initializing the fallback mechanism where it is actually used: * 046-crypto-qce-initialize-fallback-only-for-AES.patch - Three patches that make gcm and xts modes work with the qce driver, and improve performance with small blocks: * 047-crypto-qce-use-cryptlen-when-adding-extra-sgl.patch * 048-crypto-qce-use-AES-fallback-for-small-requests.patch * 049-crypto-qce-handle-AES-XTS-cases-that-qce-fails.patch - A patch that allows the hashes/ciphers to be built individually. * 051-crypto-qce-allow-building-only-hashes-ciphers.patch Signed-off-by: Eneas U de Queiroz <cotequeiroz@gmail.com> [renumbered patches, added patches from dropped commit, refreshed, 5.4] Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* ipq40xx: use neon crypto driversEneas U de Queiroz2020-02-282-0/+24
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This adds the neon based implementations of AES & SHA256. For AES, according to the kernel config help: Use a faster and more secure NEON based implementation of AES in CBC, CTR and XTS modes. Bit sliced AES gives around 45% speedup on Cortex-A15 for CTR mode and for XTS mode encryption, CBC and XTS mode decryption speedup is around 25%. (CBC encryption speed is not affected by this driver.) This implementation does not rely on any lookup tables so it is believed to be invulnerable to cache timing attacks. ... The observed speedups on ipq40xx are more modest: speedup is around 20% for CTR mode and for XTS mode encryption, CBC and XTS mode decryption speedup is around 10%. Measurements were made using tcrypt, with 1024-bytes blocks for CTR & CBC, and 4096-bytes for XTS. The aes-neon-bs driver uses a fallback for CBC encryption; that fallback could be either the generic driver written in C, or the scalar arm-asm one. Even though aes-arm is 1.9% slower, it is more resilient to timing attacks (the reason for being slower), so it is being included here. The neon sha256 module increases performance over the generic module by 33%. Signed-off-by: Eneas U de Queiroz <cotequeiroz@gmail.com> [Enable only ciphers for now, reorder patch in series to help bisect as new symbols could lead to build failures, 5.4] Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* ipq40xx: qce - switch to skcipher APIEneas U de Queiroz2020-02-284-2/+1968
| | | | | | | | | This backports a commit updating the API of the QCE crypto engine to what is used in current kerenl, easing future upstream backports. Signed-off-by: Eneas U de Queiroz <cotequeiroz@gmail.com> [renumber patches, refreshed, added 5.4 patches] Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* kernel: 4.19,5.4: disable ARM CE & NEONChristian Lamparter2020-02-282-0/+20
| | | | | | | | | | This patch disables the CRYPTO KERNEL SYMBOLs that are touched by the upcoming ipq40xx patch "ipq40xx: use neon crypto drivers" from "Eneas U de Queiroz" and more so for his follow up patches for the other ARM targets in this series. This should help to prevent at least a few potential build errors on other archs. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* ipq40xx: add support for EnGenius EAP2200Steven Lin2020-02-2813-7/+601
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | SOC: IPQ4019 / QCA Dakota CPU: Quad-Core ARMv7 Processor rev 5 (v7l) Cortex-A7 DRAM: 256 MiB FLASH: NOR 4 MiB + NAND 128 MiB ETH: Qualcomm Atheros QCA8072 WLAN1: Qualcomm Atheros QCA4019 2.4GHz 802.11bgn 2:2x2 WLAN2: Qualcomm Atheros QCA4019 5GHz 802.11a/n/ac 2:2x2 WLAN2: Qualcomm Atheros QCA9888 5GHz 802.11a/n/ac 2:2x2 INPUT: WPS Button LEDS: Power, LAN1, LAN2, WLAN 2.4GHz, WLAN 5GHz-1, WLAN 5GHz-2, OPMODE 1. Load Ramdisk via U-Boot To set up the flash memory environment, do the following: a. As a preliminary step, ensure that the board console port is connected to the PC using these RS232 parameters: * 115200bps * 8N1 b. Confirm that the PC is connected to the board using one of the Ethernet ports. c. Set a static ip 192.168.99.8 for Ethernet that connects to board. d. The PC must have a TFTP server launched and listening on the interface to which the board is connected. e. At this stage power up the board and, after a few seconds, press 4 and then any key during the countdown. U-BOOT> set serverip 192.168.99.9 && tftpboot 0x84000000 192.168.99.8:openwrt.itb && bootm Signed-off-by: Steven Lin <steven.lin@senao.com> [copied 4.19 dts to 5.4] Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* ipq807x: fix indent in image/MakefileAdrian Schmutzler2020-02-281-1/+1
| | | | | | Convert space indent to tab like the rest of the file. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-19 06:32:23 +0000