aboutsummaryrefslogtreecommitdiffstats
path: root/target
Commit message (Collapse)AuthorAgeFilesLines
* imx6: remove unnecessary wildcard from board name matchingTim Harvey2020-03-121-7/+7
| | | | | | | The wildcard used in the network config matching is not necessary given the board names returned by imx6_board_detect() in lib/imx6.sh. Signed-off-by: Tim Harvey <tharvey@gateworks.com>
* layerscape: sysupgrade: require metadataTomasz Maciej Nowak2020-03-122-0/+3
| | | | | | | | Require the image metadata check so no invalid image could be fed to sysupgrade without force option. Cc: Mathew McBride <matt@traverse.com.au> Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
* layerscape: ls10121frdm: add sysupgradeTomasz Maciej Nowak2020-03-122-0/+11
| | | | | | | | | Instead of dangerous rewriting full chip with firmware.bin image to update OpenWrt, add sysupgrade image. This image will be used to update kernel and rootfs, leaving bootloader intact and making recovery possible, without resorting to external hardware tools. Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
* layerscape: ls1012afrdm: introduce dynamic partitioningTomasz Maciej Nowak2020-03-122-1/+4
| | | | | | | | | | | | Combine fixed sizes of "kernel" and "rootfs" partitions into one partition managed by OpenWrt splitter, it will allow better management of chip capacity and less maintenance burden when compiled kernel image will outgrow allocated size for kernel partition. This also changes kernel image format, since splitter only manages kernel and rootfs partitions, the dtb needs to be updated with the kernel, so for convenience, kernel is packed to FIT image. Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
* layerscape: ls1012afrdm: convert image to squashfsTomasz Maciej Nowak2020-03-121-3/+2
| | | | | | | This commit replaces UBIFS root partition with squashfs+overlay. It's preparation for introducing dynamic partitioning. Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
* layerscape: ls1012afrdm: add uncompressed initramfsTomasz Maciej Nowak2020-03-121-0/+1
| | | | | | | Uncompressing of initramfs image fails on board with U-Boot from "QorIQ SDK (FSL Reference Distro) 2.0". Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
* layerscape: resurrect support for FRDM-LS1012ATomasz Maciej Nowak2020-03-121-0/+23
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Re-add support for NXP FRDM-LS1012A, which mimics the flash layout of the rest boards supported by LSDK. 0x000000000000-0x000000100000 : "bl2" 0x000000100000-0x000000500000 : "fip" 0x000000500000-0x000000600000 : "u-boot-env" 0x000000600000-0x000000a00000 : "reserved-1" 0x000000a00000-0x000000d00000 : "pfe" 0x000000d00000-0x000000f00000 : "reserved-2" 0x000000f00000-0x000001000000 : "dtb" 0x000001000000-0x000002000000 : "kernel" 0x000002000000-0x000004000000 : "ubifs" Specification SoC: LS1012A single core 800MHz RAM: 512 MB DDR3 Flash: 64 MB QSPI NOR Ethernet: 2x 10/100/1000 Mbps Connectors: µUSB 3.0 OTG µUSB 2.0 (debugging & power input) 2x 3.5mm jack for microphone & headphone (SGTL5000) Arduino Shield expansion with I2C, SPI, UART, and GPIO JTAG LEDS: 3x (non-configurable) Buttons: 1x (reset, non-configurable) Be advised that erasing or writing 64MB flash takes some time to finish. Do not reset the board until all operations end with success, otherwise You'll need external tools to re-program the flash chip. Installation Follow the QSPI programing procedure for LS1012AFRWY board in target/linux/layerscape/README, point 3.3. Don't forget about updating U-Boot environment with MAC addresses of ethernet interfaces, variable 'ethaddr' for eth0 and 'eth1addr' for eth1. As the LSDK images do not support sysupgrade, nor do changes in this commit, it's planed in upcoming submissions. Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
* kernel: 5.4: add unconfigured symbolsTim Harvey2020-03-121-0/+3
| | | | | | | This patch adds a few symbols that I found that need disabling in order to not break the build of octeontx Signed-off-by: Tim Harvey <tharvey@gateworks.com>
* generic: 5.4: Add 4B_OPCODES flag to w25q256Robert Marko2020-03-126-8/+35
| | | | | | | This patch backports the upstream patch that adds the 4B_OPCODES flag to w25q256 under 5.4 kernel. This is needed for ipq40xx and ramips. Signed-off-by: Robert Marko <robimarko@gmail.com>
* generic: 4.19: Add 4B_OPCODES flag to w25q256Robert Marko2020-03-126-8/+8
| | | | | | This patch backports the upstream patch that adds the 4B_OPCODES flag to w25q256 under 4.19 kernel. This is needed for ipq40xx and ramips. Signed-off-by: Robert Marko <robimarko@gmail.com>
* oxnas: switch to kernel 5.4 and remove kernel 4.14Daniel Golle2020-03-1223-2782/+1
| | | | | | | Run-tested 5.4 on Shuttle KD20 for some days now, everything seems fine so far. Let's have snapshot builds based on 5.4. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* x86: Remove kernel 4.14 supportHauke Mehrtens2020-03-129-1887/+0
| | | | | | | | | This target was switched to kernel 4.19 more than 6 months ago in commit f342ffd300da ("treewide: kernel: bump some targets to 4.19") and now with kernel 5.4 support being added it gets harder to support kernel 4.14 in addition to kernel 4.19 and 5.4. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* tegra: Remove kernel 4.14 supportHauke Mehrtens2020-03-123-681/+0
| | | | | | | | | This target was switched to kernel 4.19 more than 6 months ago in commit f342ffd300da ("treewide: kernel: bump some targets to 4.19") and now with kernel 5.4 support being added it gets harder to support kernel 4.14 in addition to kernel 4.19 and 5.4. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* sunxi: Remove kernel 4.14 supportHauke Mehrtens2020-03-1229-3437/+0
| | | | | | | | | This target was switched to kernel 4.19 more than 6 months ago in commit f342ffd300da ("treewide: kernel: bump some targets to 4.19") and now with kernel 5.4 support being added it gets harder to support kernel 4.14 in addition to kernel 4.19 and 5.4. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* octeon: Remove kernel 4.14 supportHauke Mehrtens2020-03-125-447/+0
| | | | | | | | | This target was switched to kernel 4.19 more than 6 months ago in commit f342ffd300da ("treewide: kernel: bump some targets to 4.19") and now with kernel 5.4 support being added it gets harder to support kernel 4.14 in addition to kernel 4.19 and 5.4. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* mvebu: Remove kernel 4.14 supportHauke Mehrtens2020-03-1264-6809/+0
| | | | | | | | | This target was switched to kernel 4.19 more than 6 months ago in commit f342ffd300da ("treewide: kernel: bump some targets to 4.19") and now with kernel 5.4 support being added it gets harder to support kernel 4.14 in addition to kernel 4.19 and 5.4. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* mpc85xx: Remove kernel 4.14 supportHauke Mehrtens2020-03-129-763/+0
| | | | | | | | | This target was switched to kernel 4.19 more than 6 months ago in commit f342ffd300da ("treewide: kernel: bump some targets to 4.19") and now with kernel 5.4 support being added it gets harder to support kernel 4.14 in addition to kernel 4.19 and 5.4. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* malta: Remove kernel 4.14 supportHauke Mehrtens2020-03-121-326/+0
| | | | | | | | | | This target was switched to kernel 4.19 more than 6 months ago in commit f342ffd300da ("treewide: kernel: bump some targets to 4.19") and now with kernel 5.4 support being added it gets harder to support kernel 4.14 in addition to kernel 4.19 and 5.4. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de> Acked-by: Yousong Zhou <yszhou4tech@gmail.com>
* ipq40xx: Remove kernel 4.14 supportHauke Mehrtens2020-03-1281-22206/+0
| | | | | | | | | This target was switched to kernel 4.19 more than 6 months ago in commit f342ffd300da ("treewide: kernel: bump some targets to 4.19") and now with kernel 5.4 support being added it gets harder to support kernel 4.14 in addition to kernel 4.19 and 5.4. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* imx6: Remove kernel 4.14 supportHauke Mehrtens2020-03-125-716/+0
| | | | | | | | | This target was switched to kernel 4.19 more than 6 months ago in commit f342ffd300da ("treewide: kernel: bump some targets to 4.19") and now with kernel 5.4 support being added it gets harder to support kernel 4.14 in addition to kernel 4.19 and 5.4. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* gemini: Remove kernel 4.14 supportHauke Mehrtens2020-03-1240-7766/+0
| | | | | | | | | This target was switched to kernel 4.19 more than 6 months ago in commit f342ffd300da ("treewide: kernel: bump some targets to 4.19") and now with kernel 5.4 support being added it gets harder to support kernel 4.14 in addition to kernel 4.19 and 5.4. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* ath79: Remove kernel 4.14 supportHauke Mehrtens2020-03-1250-8808/+0
| | | | | | | | | This target was switched to kernel 4.19 more than 6 months ago in commit f342ffd300da ("treewide: kernel: bump some targets to 4.19") and now with kernel 5.4 support being added it gets harder to support kernel 4.14 in addition to kernel 4.19 and 5.4. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* armvirt: Remove kernel 4.14 supportHauke Mehrtens2020-03-123-481/+0
| | | | | | | | | | This target was switched to kernel 4.19 more than 6 months ago in commit f342ffd300da ("treewide: kernel: bump some targets to 4.19") and now with kernel 5.4 support being added it gets harder to support kernel 4.14 in addition to kernel 4.19 and 5.4. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de> Acked-by: Yousong Zhou <yszhou4tech@gmail.com>
* kernel: make kmod-ata-core selected by dependent modulesupstreamless-old-masterSungbo Eo2020-03-116-40/+36
| | | | | | | | | | | | | | | | Currently kmod-ata-* will not get into images unless kmod-ata-core is added to DEVICE_PACKAGES as well. By changing the dependencies from "depends on" to "select", we do not have the issue anymore. Furthermore, we can remove most occurrences of the package from DEVICE_PACKAGES and similar variables, as it is now pulled by dependent modules such as: - kmod-ata-ahci - kmod-ata-ahci-mtk - kmod-ata-sunxi While at it, use AddDepends/ata for kmod-ata-pdc202xx-old. Signed-off-by: Sungbo Eo <mans0n@gorani.run>
* ipq806x: replace ${} with $()Sungbo Eo2020-03-111-4/+4
| | | | | | ${} and $() are exactly the same. Follow the convention of using $(). Signed-off-by: Sungbo Eo <mans0n@gorani.run>
* ipq40xx: replace ${} with $()Sungbo Eo2020-03-111-3/+3
| | | | | | ${} and $() are exactly the same. Follow the convention of using $(). Signed-off-by: Sungbo Eo <mans0n@gorani.run>
* sunxi: remove SUNXI_UBOOT from DEVICE_VARSSungbo Eo2020-03-111-1/+1
| | | | | | | All SUNXI_UBOOT usages were removed in e018c4d7ab8b ("uboot-sunxi: clean up, switch to u-boot.mk"). Now drop the variable completely. Signed-off-by: Sungbo Eo <mans0n@gorani.run>
* oxnas: clean up DEVICE_VARSSungbo Eo2020-03-112-4/+3
| | | | | | | DTS variable is not used in any device. Just drop it. UBIFS_OPTS is not device-dependent here. Remove it from DEVICE_VARS. Signed-off-by: Sungbo Eo <mans0n@gorani.run>
* build: image: move IMAGE_SIZE to image.mkSungbo Eo2020-03-115-6/+4
| | | | | | | | | | IMAGE_SIZE is widely used in many targets. Declare it in the default template to clean up redundant code. This also prevents deriving IMAGE_SIZE unintentionally from the previously defined device. While at it, remove duplicate KERNEL_SIZE declaration. Signed-off-by: Sungbo Eo <mans0n@gorani.run>
* ar71xx: fix port order on TP-Link Archer C60 v1/v2Adrian Schmutzler2020-03-111-6/+2
| | | | | | | | | The labels on the LAN ports of the TP-Link Archer C60 v1/v2 are actually inverted compared to the ports of the internal switch. Add this information to 02_network. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ath79: fix port order on TP-Link Archer C60 v1/v2Adrian Schmutzler2020-03-111-3/+3
| | | | | | | | | | | The labels on the LAN ports of the TP-Link Archer C60 v1/v2 are actually inverted compared to the ports of the internal switch. Add this information to 02_network. This is the same for to-be-supported v3 of this device. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ar71xx: remove wrong MAC address adjustment for Archer C60 v2Adrian Schmutzler2020-03-111-2/+1
| | | | | | | | | | | The adjustment of the MAC address for Archer C60 v2 in 10_fix_wifi_mac is broken since a "mac" partition is not set up for this device on ar71xx. Instead, the MAC address is already patched correctly in 11-ath10k-caldata. Remove the useless adjustment. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ar71xx: fix swapped LAN/WAN MAC address for Archer C60 v1/v2Adrian Schmutzler2020-03-112-5/+5
| | | | | | | | | | | | | | | | | | | The MAC addresses for lan/wan are swapped compared to the vendor firmware. This adjusts to vendor configuration, which is: lan *:7b label wan *:7c label+1 2.4g *:7b label 5g *:7a label-1 Only one address is stored in <&mac 0x8>, corresponding to the label. This has been checked on revisions v1, v2 and v3. Since ar71xx calculates the ath10k MAC address based on the ethernet addresses, the number there is adjusted, too. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ath79: fix swapped LAN/WAN MAC address for Archer C60 v1/v2Adrian Schmutzler2020-03-111-2/+2
| | | | | | | | | | | | | | | | The MAC addresses for lan/wan are swapped compared to the vendor firmware. This adjusts to vendor configuration, which is: lan *:7b label wan *:7c label+1 2.4g *:7b label 5g *:7a label-1 Only one address is stored in <&mac 0x8>, corresponding to the label. This has been checked on revisions v1, v2 and v3. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* armvirt: fix missing watchdog core dependency for hwmon-sch5627Petr Štetiar2020-03-111-0/+1
| | | | | | | | | | | | | | | | Fixes following error uncovered while building armvirt/64 on 5.4: Package kmod-hwmon-sch5627 is missing dependencies for the following libraries: watchdog.ko That dependency was introduced in upstream via 2d8c7ff52c24 ("hwmon/sch56xx: Depend on watchdog for watchdog core functions") in v3.5. The issue emerged in 5.4 because the kconfig symbol CONFIG_WATCHDOG_CORE is now a tristate value. Previously it was a bool. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* ar71xx/ath79: ew-dorin, fix the trigger level for WPS buttonCatrinel Catrinescu2020-03-112-2/+2
| | | | | | | | | Because the WPS button had the wrong trigger level, the failsafe mode was triggered quite often, after this commit: https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=27f3f493de Signed-off-by: Catrinel Catrinescu <cc@80211.de>
* kernel: backport out-of-memory fix for non-Ethernet devicesRafał Miłecki2020-03-113-0/+213
| | | | | | | Doing up & down on non-Ethernet devices (e.g. monitor mode interface) was consuming memory. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* ramips: add support for Ubiquiti UniFi nanoHDDavid Bauer2020-03-103-1/+151
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Hardware -------- SoC: MediaTek MT7621AT WiFi: MediaTek MT7603 bgn 2T2R MediaTek MT7615 ac 4T4R Flash: 32M SPI (Macronix MX25L25635F) RAM: 128M DDR3 (Winbond W631GG6KB) LED: Dome (Blue / White) BTN: Reset Installation ------------ These instructions were written for firmware version v3.9.27. Downgrade if necessary. 1. Copy the OpenWrt sysupgrade image to the devices /tmp folder via scp. On factory defaults, user and password is "ubnt" at 192.168.1.20/24. 2. Write the bootselect flag. Otherwise, the device might boot from the wrong partition. Verify the mtd partition used in the command below is the one labled "bs" in /proc/mtd (as this might change in the future). > dd if=/dev/zero bs=1 count=1 of=/dev/mtd4 3. Write the OpenWrt sysupgrade to the mtd partitions labled "kernel0" and "kernel1". > dd if=/tmp/openwrt-sysupgrade.bin of=/dev/mtdblock6 > dd if=/tmp/openwrt-sysupgrade.bin of=/dev/mtdblock7 4. Reboot or powercycle the device. Signed-off-by: David Bauer <mail@david-bauer.net>
* bcm47xx: add support for kernel 5.4Rafał Miłecki2020-03-1021-1/+2301
| | | | | | | | | | | | | | Ethernet, switch, LEDs, buttons, USB, sysupgrade & LuCI were successfully tested on BCM4706. WARNING: Hack for BCM4710 adding BCM4710_PROTECTED_FILL_TLB() to the local_r4k_flush_cache_sigtramp() could not be ported. That function has been dropped in: commit adcc81f148d7 ("MIPS: math-emu: Write-protect delay slot emulation pages") commit 3315b6b336c8 ("MIPS: Delete unused flush_cache_sigtramp()") it's unsure if that chipset will still work reliably. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* bcm47xx: switch to kernel 4.19Rafał Miłecki2020-03-101-1/+1
| | | | | | | Ethernet, switch, LEDs, buttons, USB, sysupgrade & LuCI were successfully tested on BCM4706. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* ipq40xx: add cpximg to flash Compex WPJ428 via bootloaderLeon M. George2020-03-101-1/+18
| | | | | | | | | | | | | | | | | | | | | | Generate a cpximg that is compatible with the cpximg loader in Compex' u-boot. The cpximg loader can be started either by holding the reset button during power up or by entering the u-boot prompt and entering 'cpximg'. Once it's running, a TFTP-server under 192.168.1.1 will accept an image appropriate for the board revision that is etched on the board (e.g. 6A04). The image can be pushed using tftp: tftp -v -m binary 192.168.1.1 -c put openwrt-ipq40xx-generic-compex_wpj428-squashfs-cpximg-6a04.bin cpximg files can also be used with the sysupgrade utility in stock images. (add SSH key in luci for root access) In mkmylofw_32m, the calculation of the "partition size" has been preferred to just padding the partition as this will result in less block transfers during flashing (while the additional complexity is bearable). Signed-off-by: Leon M. George <leon@georgemail.eu> Co-developed-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* armvirt: switch to kernel 5.4Yousong Zhou2020-03-101-1/+1
| | | | Signed-off-by: Yousong Zhou <yszhou4tech@gmail.com>
* armvirt: 5.4: kconfig syncYousong Zhou2020-03-103-25/+78
| | | | | | | "make kernel_menuconfig CONFIG_TARGET=subtarget_platform" first, then move common ones to platform level config Signed-off-by: Yousong Zhou <yszhou4tech@gmail.com>
* armvirt: add config-5.4Yousong Zhou2020-03-103-0/+547
| | | | | | Copied from config-4.19 Signed-off-by: Yousong Zhou <yszhou4tech@gmail.com>
* kernel: 5.4: remove some dup config options already set in genericYousong Zhou2020-03-105-25/+0
| | | | | | | This furthers 860652f4b9da ("kernel: 5.4: move some kconfig options to generic") Signed-off-by: Yousong Zhou <yszhou4tech@gmail.com>
* malta: switch to kernel 5.4 by defaultYousong Zhou2020-03-101-1/+1
| | | | Signed-off-by: Yousong Zhou <yszhou4tech@gmail.com>
* malta: fix missing watchdog core dependency for hwmon-sch5627Petr Štetiar2020-03-101-0/+1
| | | | | | | | | | | | | | | | | | | Fixes following error uncovered while building malta/be on 5.4: Package kmod-hwmon-sch5627 is missing dependencies for the following libraries: watchdog.ko That dependency was introduced in upstream via 2d8c7ff52c24 ("hwmon/sch56xx: Depend on watchdog for watchdog core functions") in v3.5. The issue emerged in 5.4 because the kconfig symbol CONFIG_WATCHDOG_CORE is now a tristate value. Previously it was a bool Cc: Yousong Zhou <yszhou4tech@gmail.com> Signed-off-by: Petr Štetiar <ynezz@true.cz> Signed-off-by: Yousong Zhou <yszhou4tech@gmail.com> (drop the config-4.19 change. reword about the cause)
* malta: update kernel config-5.4Yousong Zhou2020-03-101-21/+29
| | | | | | | | With malta/be selected make kernel_menuconfig CONFIG_TARGET=subtarget_platform Signed-off-by: Yousong Zhou <yszhou4tech@gmail.com>
* malta: add kernel 5.4 configYousong Zhou2020-03-101-0/+336
| | | | | | Copied from config-4.19 Signed-off-by: Yousong Zhou <yszhou4tech@gmail.com>
* kernel: 5.4: move some kconfig options to genericYousong Zhou2020-03-1015-80/+9
| | | | | | | | | | | CONFIG_64BIT_TIME=y CONFIG_KASAN_STACK=1 CONFIG_UBSAN_ALIGNMENT=y CONFIG_UNIX_SCM=y CONFIG_DMA_DECLARE_COHERENT=y CONFIG_OF_RESERVED_MEM=y Signed-off-by: Yousong Zhou <yszhou4tech@gmail.com>