aboutsummaryrefslogtreecommitdiffstats
path: root/target
Commit message (Collapse)AuthorAgeFilesLines
* generic: Kconfig: exit on unset symbolDavid Bauer2021-08-102-0/+22
| | | | | | | | | | | | | When a target configuration has unser Kconfig symbols, the build will fail when OpenWrt is compiled with V=s and stdin is connected to a tty. In case OpenWrt is compiled without either of these preconditions, the build will uscceed with the symbols in question being unset. Modify the kernel configuration in a way it fails on unset symbols regardless of the aformentioned preconditions. Signed-off-by: David Bauer <mail@david-bauer.net>
* generic: fix kernel panic on existing mac-address nodeDavid Bauer2021-08-102-16/+8
| | | | | | | | | | | | | Calling free for the OF property can result in a kernel panic, as the buffer in question might be referenced elsewhere. Also, it is not removed from the tree. Always allocate a new property and updating the tree with it fixes both issues. Fixes commit 91a52f22a13d ("treewide: backport support for nvmem on non platform devices") Signed-off-by: David Bauer <mail@david-bauer.net>
* omap: Remove EXT2 and EXT3 driver configHauke Mehrtens2021-08-091-4/+0
| | | | | | | | The EXT4 driver also takes care of EXT2 and EXT3 file systems. Activating the EXT2 driver kernel config options unlocked some other ext2 driver related options which OpenWrt did not take care of. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* layerscape: Fix multiple bugs in of_get_mac_address() changesHauke Mehrtens2021-08-0910-30/+24
| | | | | | | | | | | The change which backported the of_get_mac_address() change broke some patches in the layerscape target so the patches did not apply any more. This commit makes them apply again and also fixes some other problems related to this change. Fixes commit 91a52f22a13d ("treewide: backport support for nvmem on non platform devices") Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: Apply change to of_get_mac_address() to ks8851 tooHauke Mehrtens2021-08-091-0/+38
| | | | | | | | | The code from ks8851.c was moved to ks8851_common.c, so it was not backported. This broke the compile of the omap target which uses this driver. Fixes commit 91a52f22a13d ("treewide: backport support for nvmem on non platform devices") Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* mvebu: armada-37xx: add patch to forbid cpufreq for 1.2 GHzJosef Schlehofer2021-08-081-0/+39
| | | | | | | | | | | This patch is backported from linux-arm-kernel [1] to improve situation, when it was reported that 1.2 GHz variant is unstable with DFS. It waits to be accepted upstream, however, it waits for Marvell people to respond. [1] https://patchwork.kernel.org/project/linux-arm-kernel/patch/20210630225601.6372-1-kabel@kernel.org/ Fixes: 7b868fe04a89 ("Revert "mvebu: 5.4 fix DVFS caused random boot crashes"") Signed-off-by: Josef Schlehofer <pepe.schlehofer@gmail.com>
* Revert "mvebu: 5.10 fix DVFS caused random boot crashes"Josef Schlehofer2021-08-081-107/+0
| | | | | | | | | | | | | | | | | | | | | | | | | Based on the discussion on the mailing list [1], the patch which was reverted, it reverts only one patch without the subsequent ones. This leads to the SoC scaling issue not using a CPU parent clock, but it uses DDR clock. This is done for all variants, and it's wrong because commits (hacks) that were using the DDR clock are no longer in the mainline kernel. If someone has stability issues on 1.2 GHz, it should not affect all routers (1 GHz, 800 MHz) and it should be rather consulted with guys, who are trying to improve the situation in the kernel and not making the situation worse. There are two solutions in cases of instability: a) disable cpufreq b) underclock it up to 1 GHz This reverts commit 080a0b74e39d159eecf69c468debec42f28bf4d8. [1] https://lists.openwrt.org/pipermail/openwrt-devel/2021-June/035702.html Fixes: d37947681772 ("mvebu: armada-37xx: add patch to forbid cpufreq for 1.2 GHz") CC: Pali Rohár <pali@kernel.org> Signed-off-by: Josef Schlehofer <pepe.schlehofer@gmail.com>
* layerscape: armv8_64b: do not disable CONFIG_IP_ADVANCED_ROUTERMartin Schiller2021-08-081-1/+0
| | | | | | | | This option is needed e.g. to use strongswan for IPSec. BTW: This was the only target where this option was disabled. Signed-off-by: Martin Schiller <ms@dev.tdt.de>
* gemini: Add hdparm settingLinus Walleij2021-08-081-0/+14
| | | | | | | | This uses "hdparm" (if present) to get the harddisk into low power mode on NAS set-ups. Cc: Adrian Schmutzler <mail@adrianschmutzler.de> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
* mvebu: armada-37xx: add patch to forbid cpufreq for 1.2 GHzJosef Schlehofer2021-08-081-0/+39
| | | | | | | | | | This patch is backported from linux-arm-kernel [1] to improve situation, when it was reported that 1.2 GHz variant is unstable with DFS. It waits to be accepted upstream, however, it waits for Marvell people to respond. [1] https://patchwork.kernel.org/project/linux-arm-kernel/patch/20210630225601.6372-1-kabel@kernel.org/ Signed-off-by: Josef Schlehofer <pepe.schlehofer@gmail.com>
* Revert "mvebu: 5.4 fix DVFS caused random boot crashes"Josef Schlehofer2021-08-081-107/+0
| | | | | | | | | | | | | | | | | | | | | | | | Based on the discussion on the mailing list [1], the patch which was reverted, it reverts only one patch without the subsequent ones. This leads to the SoC scaling issue not using a CPU parent clock, but it uses DDR clock. This is done for all variants, and it's wrong because commits (hacks) that were using the DDR clock are no longer in the mainline kernel. If someone has stability issues on 1.2 GHz, it should not affect all routers (1 GHz, 800 MHz) and it should be rather consulted with guys, who are trying to improve the situation in the kernel and not making the situation worse. There are two solutions in cases of instability: a) disable cpufreq b) underclock it up to 1 GHz This reverts commit 080a0b74e39d159eecf69c468debec42f28bf4d8. [1] https://lists.openwrt.org/pipermail/openwrt-devel/2021-June/035702.html CC: Pali Rohár <pali@kernel.org> Signed-off-by: Josef Schlehofer <pepe.schlehofer@gmail.com>
* mvebu: Turris Omnia: use SFP module, if presentKlaus Kudielka2021-08-081-1/+16
| | | | | | | | | | | | Follow the recommendations stated in the Turris Omnia DTS for eth2: "In case SFP module is present, U-Boot has to enable the sfp node above, remove phy-handle property, and add managed = "in-band-status" property." The boot script is written in a way, that it works for all U-Boot versions deployed by the vendor so far (2015.10-rc2, 2019.07). Signed-off-by: Klaus Kudielka <klaus.kudielka@gmail.com>
* mvebu: backport Turris Omnia DTS changes to 5.4Klaus Kudielka2021-08-086-3/+249
| | | | | | | Kernel 5.4 receives a reduced set, just to make the SFP cage work. While we are at it, move the patches accepted upstream to the 0xx series. Signed-off-by: Klaus Kudielka <klaus.kudielka@gmail.com>
* mvebu: backport Turris Omnia DTS changes to 5.10Klaus Kudielka2021-08-086-4/+410
| | | | | | | Kernel 5.10 receives the complete set of improvements from 5.11/5.12. While we are at it, move the patches accepted upstream to the 0xx series. Signed-off-by: Klaus Kudielka <klaus.kudielka@gmail.com>
* ath79: fix the AR7{1,2}00 USB PHY patchesRui Salvaterra2021-08-082-4/+4
| | | | | | | PHY_SIMPLE is a bogus kconfig symbol, what we really need to select is GENERIC_PHY. Signed-off-by: Rui Salvaterra <rsalvaterra@gmail.com>
* kernel/generic: add CONFIG_KCSAN to the 5.10 kconfigRui Salvaterra2021-08-081-0/+1
| | | | | | | Add the missing CONFIG_KCSAN (disabled). Found while making kernel_oldconfig on an x86-64 subtarget. Signed-off-by: Rui Salvaterra <rsalvaterra@gmail.com>
* kernel: backport mdio_find_bus from 5.10.xDamien Mascord2021-08-082-1/+68
| | | | | | | | | | | | | | mdio-tools (https://github.com/wkz/mdio-tools) requires the use of mdio_find_bus, which is not present in 5.4.x. This patch backports the required change from 5.10.x to 5.4.x The original patch submission for this can be found at https://patchwork.ozlabs.org/project/netdev/patch/20200201074625.8698-2-jeremy.linton@arm.com/ Signed-off-by: Damien Mascord <tusker@tusker.org> [Add original patch description] Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: bump 5.4 to 5.4.138John Audia2021-08-082-5/+5
| | | | | | | | | | | | All patches automatically rebased. Build system: x86_64 Build-tested: ipq806x/R7800 Run-tested: ipq806x/R7800 No dmesg regressions, everything functional Signed-off-by: John Audia <graysky@archlinux.us>
* kernel: bump 5.10 to 5.10.55Rui Salvaterra2021-08-085-6/+6
| | | | | | No deleted or manually refreshed patches. Signed-off-by: Rui Salvaterra <rsalvaterra@gmail.com>
* mvebu: switch to generic sdcard upgrade methodStijn Tintel2021-08-075-101/+10
| | | | | | | Now that we have a generic sdcard upgrade method, which was copied from the mvebu platform method, we can switch mvebu to the generic method. Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* base-files: add generic sdcard upgrade methodStijn Tintel2021-08-071-0/+3
| | | | | | | | Add a generic sdcard upgrade method instead of duplicating code in yet another target, and add a feature flag to only install this upgrade method in targets that set this flag. Copied from mvebu. Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* kirkwood: import patch to fix build and refresh patchesDaniel Golle2021-08-0516-36/+158
| | | | | | | | | kirkwood build broke due to missing include needed for ETH_ALEN. Add patch (sent upstream as well) to address that. Refresh patches for 5.4 and 5.10. Fixes: 91a52f22a1 ("treewide: backport support for nvmem on non platform devices") Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* ramips: add missing label-mac-device for Xiaomi Mi Router 4A (100M)Fabian Bläse2021-08-051-0/+1
| | | | | | | As both the Mi Router 4A (100M) and the Mi Router 4C use the same label-mac-device, the alias can be moved to the shared dtsi. Signed-off-by: Fabian Bläse <fabian@blaese.de>
* realtek: fix syntax error introduced by previous commitDaniel Golle2021-08-051-1/+1
| | | | | | | | A superflus ')' character has slipped into commit 91a52f22a1. Remove it to fix build. Fixes: 91a52f22a1 ("treewide: backport support for nvmem on non platform devices") Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* generic: fix to few arguments to of_get_mac_addressDavid Bauer2021-08-051-13/+91
| | | | | | Fixes commit 91a52f22a13d ("treewide: backport support for nvmem on non platform devices") Signed-off-by: David Bauer <mail@david-bauer.net>
* mediatek: mt7622: enable HW RNGDavid Bauer2021-08-051-0/+2
| | | | | | | MT7622 provides are hardware RNG with upstream Linux driver. Enable compilation of this driver to make use of the hardware RNG. Signed-off-by: David Bauer <mail@david-bauer.net>
* ath79: add support for GL.iNet GL-X300BJohn Marrett2021-08-054-0/+154
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The GL-X300B is a industrial 4G LTE router based on the Qualcomm QCA9531 SoC. Specifications: - Qualcomm QCA9531 @ 650 MHz - 128 MB of RAM - 16 MB of SPI NOR FLASH - 2x 10/100 Mbps Ethernet - 2.4GHz 802.11b/g/n - 1x USB 2.0 (vbus driven by GPIO) - 4x LED, driven by GPIO - 1x button (reset) - 1x mini pci-e slot (vcc driven by GPIO) - RS-485 Serial Port (untested) Flash instructions: This firmware can be flashed using either sysupgrade from the GL.iNet firmware or the recovery console as follows: - Press and hold the reset button - Connect power to the router, wait five seconds - Manually configure 192.168.1.2/24 on your computer, connect to 192.168.1.1 - Upload the firmware image using the web interface RS-485 serial port is untested and may depend on the following commit in the GL.iNet repo: https://github.com/gl-inet/openwrt/commit/202e83a32ae308fbb70502b6dbe3bb0bf8b1fba9 MAC addresses as verified by OEM firmware: vendor OpenWrt address WAN eth0 label LAN eth1 label + 1 2g phy0 label + 2 The label MAC address was found in the art partition at 0x0 Based on vendor commit: https://github.com/gl-inet/openwrt/commit/16c5708b207eb76ff19a040dc973e560d3d8074b Signed-off-by: John Marrett <johnf@zioncluster.ca>
* generic: add missing Kconfig symbol ARM_SCMI_PROTOCOLHannu Nyman2021-08-051-0/+1
| | | | | | | | Add the missing ARM_SCMI_PROTOCOL symbol. Apparently it was exposed for 5.10.53 with a kernel dependency change. Missing symbol observed with mediatek/7622 E8450/RT3200 router. Signed-off-by: Hannu Nyman <hannu.nyman@iki.fi>
* generic: enable netlink ethtool interfaceDavid Bauer2021-08-051-1/+1
| | | | | | | The virtual cable tester depends on the netlink interface for ethtool. Thus, enable it in the generic kernel configuration. Signed-off-by: David Bauer <mail@david-bauer.net>
* treewide: backport support for nvmem on non platform devicesAnsuel Smith2021-08-0530-450/+3998
| | | | | | | | | | | | In the current state, nvmem cells are only detected on platform device. To quickly fix the problem, we register the affected problematic driver with the of_platform but that is more an hack than a real solution. Backport from net-next the required patch so that nvmem can work also with non-platform devices and rework our current patch. Drop the mediatek and dsa workaround and rework the ath10k patches. Rework every driver that use the of_get_mac_address api. Signed-off-by: Ansuel Smith <ansuelsmth@gmail.com>
* kernel: fix kernel 5.5 and 5.9 PCI DT regressionsRafał Miłecki2021-08-042-0/+122
| | | | | | This fixes PCI on bcm53xx. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* generic: add missing ARM64 crypto Kconfig symbolsDavid Bauer2021-07-311-0/+11
| | | | | | | | | bcm27xx-bcm2710 builds are stalling when compiled with V=s. Explitily disable these unset symbols to avoid stalling builds. Signed-off-by: David Bauer <mail@david-bauer.net>
* kernel: bump 5.4 to 5.4.136John Audia2021-07-3117-27/+27
| | | | | | | | | | | | All patches automatically rebased. Build system: x86_64 Build-tested: ipq806x/R7800 Run-tested: ipq806x/R7800 No dmesg regressions, everything functional Signed-off-by: John Audia <graysky@archlinux.us>
* kernel: bump 5.4 to 5.4.135John Audia2021-07-3127-62/+62
| | | | | | | | | | | | All patches automatically rebased. Build system: x86_64 Build-tested: ipq806x/R7800 Run-tested: ipq806x/R7800 No dmesg regressions, everything functional Signed-off-by: John Audia <graysky@archlinux.us>
* generic: add missing Kconfig symbolDavid Bauer2021-07-311-0/+2
| | | | | | Fixes build errors for sunxi as well as rockchip targets. Signed-off-by: David Bauer <mail@david-bauer.net>
* kernel: bump 5.10 to 5.10.54Rui Salvaterra2021-07-299-69/+20
| | | | | | | Deleted (upstreamed) patches: mediatek/patches-5.10/000-spi-fix-fifo.patch Signed-off-by: Rui Salvaterra <rsalvaterra@gmail.com>
* kernel: bump 5.10 to 5.10.53Rui Salvaterra2021-07-295-7/+7
| | | | | | No deleted or manually refreshed patches. Signed-off-by: Rui Salvaterra <rsalvaterra@gmail.com>
* generic: fix build warningDavid Bauer2021-07-296-14/+12
| | | | | | | | | Fixes a unused variable warning: drivers/of/of_net.c: In function 'of_get_mac_address_mtd': drivers/of/of_net.c:92:19: warning: unused variable 'prop' [-Wunused-variable] Signed-off-by: David Bauer <mail@david-bauer.net>
* mediatek: mt7623: import patch to fix msi warningNick Hainke2021-07-2910-18/+150
| | | | | | | | | | | | | | | | | | | | | | | | | | | The 1st generation MediaTek PCIe host bridge cannot handle Message Signaled Interrupts (MSIs). The core PCI code is not aware that MSI is not available. This results in warnings of the form: WARNING: CPU: 2 PID: 112 at include/linux/msi.h:219 pci_msi_setup_msi_irqs.constprop.8+0x64/0x6c Modules linked in: ahci(+) libahci libata sd_mod scsi_mod gpio_button_hotplug CPU: 2 PID: 112 Comm: kmodloader Not tainted 5.10.52 #0 Hardware name: Mediatek Cortex-A7 (Device Tree) Import patches that introduce the 'no_msi' attribute to signal missing MSI support to the core PCI. Refresh patches: - 000-spi-fix-fifo.patch - 330-mtk-bmt-support.patch - 510-net-mediatek-add-flow-offload-for-mt7623.patch - 601-PCI-mediatek-Use-regmap-to-get-shared-pcie-cfg-base.patch - 610-pcie-mediatek-fix-clearing-interrupt-status.patch - 700-net-ethernet-mtk_eth_soc-add-support-for-coherent-DM.patch - 710-pci-pcie-mediatek-add-support-for-coherent-DMA.patch Signed-off-by: Nick Hainke <vincent@systemli.org>
* bcm53xx: refresh kernel 5.10 configRafał Miłecki2021-07-291-76/+12
| | | | Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* bcm53xx: add testing support for kernel 5.10Rafał Miłecki2021-07-2932-1/+2357
| | | | | | | | | | | | | | | | It still requires fixing PCIe support: [ 6.644699] pcie_iproc_bcma bcma0:7: host bridge /axi@18000000/pcie@12000 ranges: [ 6.652217] pcie_iproc_bcma bcma0:7: No bus range found for /axi@18000000/pcie@12000, using [bus 00-ff] [ 6.661833] OF: /axi@18000000/pcie@12000: Missing device_type [ 6.667622] pcie_iproc_bcma: probe of bcma0:7 failed with error -12 [ 6.673985] pcie_iproc_bcma bcma0:8: host bridge /axi@18000000/pcie@13000 ranges: [ 6.681514] pcie_iproc_bcma bcma0:8: No bus range found for /axi@18000000/pcie@13000, using [bus 00-ff] [ 6.691137] pcie_iproc_bcma: probe of bcma0:8 failed with error -12 [ 6.697522] pcie_iproc_bcma bcma0:9: host bridge /axi@18000000/pcie@14000 ranges: [ 6.705048] pcie_iproc_bcma bcma0:9: No bus range found for /axi@18000000/pcie@14000, using [bus 00-ff] [ 6.714669] pcie_iproc_bcma: probe of bcma0:9 failed with error -12 Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* kernel: fix bgmac compilation in kernel 5.10Rafał Miłecki2021-07-291-1/+1
| | | | | | | It's required since upstream kernel commit 4bdc0d676a64 ("remove ioremap_nocache and devm_ioremap_nocache"). Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* generic: fix compile-error for non-mtd platformsDavid Bauer2021-07-296-14/+16
| | | | | | Fixes commit cd39aba402ea ("generic: write back netdev MAC-address to device-tree") Signed-off-by: David Bauer <mail@david-bauer.net>
* generic: write back netdev MAC-address to device-treeDavid Bauer2021-07-296-54/+112
| | | | | | | | | | | | The label-mac logic relies on the mac-address property of a netdev devices of-node. However, the mac address can also be stored as a different property or read from e.g. an mtd device. Create this node when reading a mac-address from OF if it does not already exist and copy the mac-address used for the device to this property. This way, the MAC address can be accessed using procfs. Signed-off-by: David Bauer <mail@david-bauer.net>
* ath79: fix JT-OR750i switch LED assignmentDavid Bauer2021-07-281-2/+2
| | | | | | | The LEDs for LAN1 and LAN3 were swapped. Link on port 1 would illuminate the LED on port 3 and vice versa. Signed-off-by: David Bauer <mail@david-bauer.net>
* ath79: enable missing pinmux for JT-OR750iDavid Bauer2021-07-281-0/+3
| | | | | | | Without explicit configuration of these pins the ethernet as well as status LED of the device do not work correctly. Signed-off-by: David Bauer <mail@david-bauer.net>
* Revert "generic: add mac-address property for NVMEM mac addresses"David Bauer2021-07-282-118/+0
| | | | | | | | | | | | | | This reverts commit b30924873062be47250e6b872347461c8221688d. This commit could create a property without allocated memory, breaking subsequent reads over a nodes property. Also, the mac-address-increment was not applied when reading from nvmem. Revert this commit for now, which breaks the label-mac-address logic. Possibly, traversing the device-tree from the netdev side is easier anyways. Signed-off-by: David Bauer <mail@david-bauer.net>
* ath79: add support for Joy-IT JT-OR750iVincent Wiemann2021-07-285-0/+153
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Specifications: * QCA9531, 16 MiB flash (Winbond W25Q128JVSQ), 128 MiB RAM * 802.11n 2T2R (external antennas) * QCA9887, 802.11ac 1T1R (connected with diplexer to one of the antennas) * 3x 10/100 LAN, 1x 10/100 WAN * UART header with pinout printed on PCB Installation: * The device comes with a bootloader installed only * The bootloader offers DHCP and is reachable at http://10.123.123.1 * Accept the agreement and flash sysupgrade.bin * Use Firefox if flashing does not work TFTP recovery with static IP: * Rename sysupgrade.bin to jt-or750i_firmware.bin * Offer it via TFTP server at 192.168.0.66 * Keep the reset button pressed for 4 seconds after connecting power TFTP recovery with dynamic IP: * Rename sysupgrade.bin to jt-or750i_firmware.bin * Offer it via TFTP server with a DHCP server running at the same address * Keep the reset button pressed for 6 seconds after connecting power Co-authored-by: Sebastian Schaper <openwrt@sebastianschaper.net> Signed-off-by: Vincent Wiemann <vincent.wiemann@ironai.com>
* mediatek: Fix Fidelix-FM35X1GA patchHauke Mehrtens2021-07-251-2/+2
| | | | | | | | This patch did not apply cleanly any more after support for the XTX flash was added to the generic patches. Fixes: 92012dd8677a ("kernel: Add support for XTX XT26G02A SPI NAND") Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* mvebu: limit mvneta tx queue workaround to 32 bit SoCTomasz Maciej Nowak2021-07-252-4/+12
| | | | | | | | | | | | This patch has been carried since introduction throughout every kernel major bump and no one has tested if the later kernels improved the situation. The Armada 3720 SoC can only process GbE interrupts on Core 0 and this is already limited in all stable kernels, so ditch this workaround for 64 bit SoCs. Ref: https://git.kernel.org/torvalds/c/cf9bf871280d Signed-off-by: Tomasz Maciej Nowak <tmn505@gmail.com>
generated by cgit v1.2.3 (git 2.25.1) at 2024-08-08 15:48:31 +0000