aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* ramips: 5.10: refresh configsIlya Lipnitskiy2021-03-066-28/+28
| | | | | | | | Run-tested on Ubiquiti EdgeRouter X. Compile tested on all other subtargets. Signed-off-by: Ilya Lipnitskiy <ilya.lipnitskiy@gmail.com>
* ramips: 5.10: port and refresh patches, ralink drvIlya Lipnitskiy2021-03-0634-201/+333
| | | | | | | | | | | | | | | | | | | Enable testing kernel. Fix compile errors by using new kernel APIs. Fix fuzz by manually editing patches to ensure the code goes in the right place. For 721-NET-no-auto-carrier-off-support.patch, revert upstream commit a307593a6 to keep the OpenWrt ralink driver operational. Add mt7621-pci-phy patch to select REGMAP_MMIO as discussed in PR #3693 and #3952. Run automatic quilt refresh on the rest. Signed-off-by: Ilya Lipnitskiy <ilya.lipnitskiy@gmail.com>
* ramips: 5.10: rename patches to follow guideIlya Lipnitskiy2021-03-0636-0/+0
| | | | | | | | | Rename patches to follow the 3-digit classification from the OpenWrt Developer Guide. https://openwrt.org/docs/guide-developer/build-system/use-patches-with-buildsystem#naming_patches Signed-off-by: Ilya Lipnitskiy <ilya.lipnitskiy@gmail.com>
* ramips: 5.10: delete upstreamed patchesIlya Lipnitskiy2021-03-0629-2440/+0
| | | | | | | | 0098-disable_cm.patch is not needed because upstream fixed CM handling. The rest are straightforward removals of upstreamed patches. Signed-off-by: Ilya Lipnitskiy <ilya.lipnitskiy@gmail.com>
* ramips: 5.10: copy patches from 5.4Ilya Lipnitskiy2021-03-0667-0/+8783
| | | | | | Strict copy, no changes made. Signed-off-by: Ilya Lipnitskiy <ilya.lipnitskiy@gmail.com>
* ramips: copy config-5.4 to config-5.10Ilya Lipnitskiy2021-03-066-0/+1202
| | | | | | Strict copy, no changes made. Signed-off-by: Ilya Lipnitskiy <ilya.lipnitskiy@gmail.com>
* Revert "ramips: add support for kernel 5.10"Adrian Schmutzler2021-03-0651-7679/+2
| | | | | | | | | This reverts commit b4aad29a1d7ad77d67073c1c54b28c429c64ed9b. This was accidentally folded into a single commit. Remove it and apply it properly again. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* kernel: fix kmod-usb3 on platforms without PCIDaniel Golle2021-03-061-3/+6
| | | | | | | | | | | | | Partially restore the wild-card matching for kmod-usb3 modules to fix build on platforms without PCI which otherwise file, as seen on buildbot: ERROR: module '[...]/linux-5.4.102/drivers/usb/host/xhci-pci.ko' is missing. modules/usb.mk:1675: recipe for target '[...]/kmod-usb3_5.4.102-1_mips_mips32.ipk' failed Fixes: 7bda2e9aba ("kernel: fix kmod-usb3 dependencies") Fixes: be23f9818a ("apm821xx: add support for kernel 5.10") Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* apm821xx, mt7621, oxnas, rockchip, zynq: remove PLUGIN_HOSTCCIlya Lipnitskiy2021-03-066-6/+0
| | | | | | This config symbol should not be defined in target configs. Signed-off-by: Ilya Lipnitskiy <ilya.lipnitskiy@gmail.com>
* kernel: generic: filter out CONFIG_PLUGIN_HOSTCCIlya Lipnitskiy2021-03-063-4/+3
| | | | | | | | | | | | It appears to be an automatic Kconfig symbol that varies depending on the host platform. There is no need to define it in target configs, so filter it out. Also sort config-filter entries alphabetically. Cc: Adrian Schmutzler <mail@adrianschmutzler.de> Cc: Felix Fietkau <nbd@nbd.name> Signed-off-by: Ilya Lipnitskiy <ilya.lipnitskiy@gmail.com>
* arm-trusted-firmware-mediatek: prune now uneeded declarationsDaniel Golle2021-03-061-7/+0
| | | | | | | Remove unneeded delcarations form package Makefile now that everything comes from github.com/mtk-openwrt upstream. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* kernel: fix kmod-usb3 dependenciesIlya Lipnitskiy2021-03-061-20/+62
| | | | | | | | | | | | | | | | | | Adding CONFIG_USB_XHCI_PCI_RENESAS to KCONFIG made it so it was set for all targets that included kmod-usb3, not just the intended apm821xx/nand. xhci-pci has a dependency on xhci-pci-renesas if CONFIG_USB_XHCI_PCI_RENESAS is set, breaking kmod-usb3 builds on Linux 5.10 on all other targets. Rework the dependencies by breaking out xhci-hcd, xhci-mtk, and xhci-pci-renesas into new hidden kernel modules and setting kmod-usb3 dependencies properly. Tested by building mt7621 and apm821xx/nand with kmod-usb3 on Linux 5.10 Fixes: be23f981 ("apm821xx: add support for kernel 5.10") Cc: Christian Lamparter <chunkeey@gmail.com> Signed-off-by: Ilya Lipnitskiy <ilya.lipnitskiy@gmail.com>
* arm-trusted-firmware-mediatek: don't select DDR3_FLYBY for 1ddrDaniel Golle2021-03-051-10/+6
| | | | | | | DDR3_FLYBY has accidentally been set also for the 1-chip variant which lead to broken, unbootable images. Fix that. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* ramips: add support for kernel 5.10Ilya Lipnitskiy2021-03-0551-2/+7679
| | | | | | | | | | | | | | | | | | | | | | | | | Enable testing kernel. Delete upstreamed patches: 0098-disable_cm.patch can be dropped, upstream fixed CM handling. Fix compile errors by using new kernel APIs. Fix fuzz by manually editing patches to ensure the code goes in the right place. For 721-NET-no-auto-carrier-off-support.patch, revert upstream commit a307593a6 to keep the OpenWrt ralink driver operational. Add mt7621-pci-phy patch to select REGMAP_MMIO as discussed in PR #3693 and #3952. Rename patches to follow the 3-digit classification from the OpenWrt Developer Guide. Run automatic quilt refresh. Signed-off-by: Ilya Lipnitskiy <ilya.lipnitskiy@gmail.com>
* ramips: 5.4: refresh configsIlya Lipnitskiy2021-03-056-274/+17
| | | | | | Automatic refresh by running make kernel_oldconfig on each target. Signed-off-by: Ilya Lipnitskiy <ilya.lipnitskiy@gmail.com>
* apm821xx: add support for kernel 5.10 for testingChristian Lamparter2021-03-0515-2/+731
| | | | | | | | | | | | This patch copies over refreshed patches from 5.4. - dropped crypto patches (they got upstreamed) - dropped renesas USB 3 firmware loader (they got upstreamed) - NAND now needs extra device-properties for ECC settings. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* mediatek: mt7622: bpi-r64: allow MAC addresses to be inheritedDaniel Golle2021-03-053-6/+14
| | | | Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* uboot-mediatek: improve BPi-R64 supportDaniel Golle2021-03-052-6/+14
| | | | | | | | * allow MAC address from U-Boot env to be inhertied * allow eMMC installation to succeed also without recovery present on the SD Card. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* kernel: bump 5.10 to 5.10.20Rui Salvaterra2021-03-0527-1105/+59
| | | | | | | | | | | | | | | | | | | | | | | | Also add a new kconfig symbol (CONFIG_KCMP) to the generic config, disabling the SYS_kcmp syscall (it was split from CONFIG_CHECKPOINT_RESTORE, which is disabled by default, so the previous behaviour is kept). Removed (upstreamed) patches: 070-net-icmp-pass-zeroed-opts-from-icmp-v6-_ndo_send-bef.patch 081-wireguard-device-do-not-generate-ICMP-for-non-IP-pac.patch 082-wireguard-queueing-get-rid-of-per-peer-ring-buffers.patch 083-wireguard-kconfig-use-arm-chacha-even-with-no-neon.patch 830-v5.12-0002-usb-serial-option-update-interface-mapping-for-ZTE-P685M.patch Manually rebased patches: 313-helios4-dts-status-led-alias.patch 104-powerpc-mpc85xx-change-P2020RDB-dts-file-for-OpenWRT.patch Run tested: ath79 (TL-WDR3600) mvebu (Turris Omnia) Signed-off-by: Rui Salvaterra <rsalvaterra@gmail.com>
* arm-trusted-firmware-mediatek: update to ATF 2.4 (2021-02-25)Daniel Golle2021-03-053-61/+30
| | | | | | | | | | | | | | | | | | | | All necessary blobs are now contained in the upstream repository, no more wild replacing of blobs needed. This new version also contains new storage drivers for (SPI-)NAND which already comes with support for FM35Q1GA, so that patch can be dropped as well. Tested on: * Bananapi BPi-R64 - sdmmc-2ddr - emmc-2ddr * Linksys E8450 - snand-1ddr All works fine (booting Bananapi BPi-R64 from SD Card does NOT require a signed image, so patch arm-trusted-firmware-mediatek to allow doing that). Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* build: use config-1 instead of config@1 as defaultRobert Marko2021-03-052-2/+2
| | | | | | | | | | U-boot will reject all nodes with @ since commit: https://gitlab.denx.de/u-boot/u-boot/-/commit/79af75f7776fc20b0d7eb6afe1e27c00fdb4b9b4 This will cause the OpenWrt images to fail booting, to rectify use the config-1 as default. Signed-off-by: Robert Marko <robert.marko@sartura.hr>
* scripts: mkits.sh: replace @ with - in nodesRobert Marko2021-03-051-8/+8
| | | | | | | | | | | | | | | U-boot will reject the nodes with @ for the address since commit: https://gitlab.denx.de/u-boot/u-boot/-/commit/79af75f7776fc20b0d7eb6afe1e27c00fdb4b9b4 This in turn will cause the failure to boot with OpenWrt generated images. So, to rectify that simply replace @ with -. Signed-off-by: Daniel Golle <daniel@makrotopia.org> (cover also newly added rootfs@1 and initrd@1 nodes) Signed-off-by: Robert Marko <robert.marko@sartura.hr>
* bcm4908: prepare to support TP-Link Archer C2300 V1Rafał Miłecki2021-03-055-0/+239
| | | | | | | | | | It's a BCM4906 based device (2 CPU cores). It has 512 MiB of RAM, 4 LAN ports, 1 WAN port, 2 USB ports, NAND flash. WiFi unknown at this point. Flashing is possible using CFE only, proper image will be worked on later. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* bcm63xx-cfe: update to the latest masterRafał Miłecki2021-03-051-3/+3
| | | | | | d035016 tp-link: rename to tplink to match DT vendor prefix Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* kernel/modules: fix CDC NCM dependenciesRui Salvaterra2021-03-051-1/+1
| | | | | | CDC NCM support only depends on CDC Ethernet with Linux 5.10. Fix thusly. Signed-off-by: Rui Salvaterra <rsalvaterra@gmail.com>
* generic: config-5.10: add missing symbolsIlya Lipnitskiy2021-03-051-0/+7
| | | | | | Add symbols missing after latest crypto.mk and WireGuard changes. Signed-off-by: Ilya Lipnitskiy <ilya.lipnitskiy@gmail.com>
* kernel: backport GCC 10 usbip build fix for 5.4Rui Salvaterra2021-03-051-0/+33
| | | | | | | | | | | | | From the original commit message: "With GCC 10, building usbip triggers error for multiple definition of 'udev_context', in: - libsrc/vhci_driver.c:18 and - libsrc/usbip_host_common.c:27. Declare as extern the definition in libsrc/usbip_host_common.c." Signed-off-by: Rui Salvaterra <rsalvaterra@gmail.com>
* kernel: remove symbols from 5.10 no longer present on upstreamLuis Araneda2021-03-051-2/+0
| | | | | | | | | | REFCOUNT_FULL was removed for linux 5.5: commit fb041bb7c0a9 (locking/refcount: Consolidate implementations of refcount_t) COMMON_CLK_VERSATILE was removed on linux 5.8: commit 5f55f1fb187d (clk: versatile: Fix kconfig dependency on COMMON_CLK_VERSATILE) Signed-off-by: Luis Araneda <luaraneda@gmail.com>
* bcm63xx: rename upstreamed patchSieng Piaw Liew2021-03-052-6/+12
| | | | | | | | | Patch to fix kernel panic was recently accepted upstream so rename patch and add acked lines to reflect that. Signed-off-by: Sieng Piaw Liew <liew.s.piaw@gmail.com> (add the same patch for v5.10) Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* kernel: b53: update the BCM5365 UID in the fixupDaniel González Cabanelas2021-03-051-2/+2
| | | | | | | | | | The BCM5365 UID was updated in the driver, but we should also update it in the fixup. Fixes: cbcac4fde8ba ("kernel: b53: update the BCM5365 UID") Signed-off-by: Daniel González Cabanelas <dgcbueu@gmail.com> (Ammend commit description, add Fixes tag) Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm27xx: bcm2711: disable HW_RANDOM_BCM2835Álvaro Fernández Rojas2021-03-051-1/+0
| | | | | | This driver is only present on BCM2708, BCM2709 and BCM2710. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* rssileds: use new application led trigger backendFlorian Eckert2021-03-052-0/+5
| | | | | | | | | | | | | | | | | This will use the new application led trigger backend. For now this is the only package that uses leds trigger in user space to configure the kernel led triggers. The callback script only emmits a message for now, so that this LED is now managed by the rssileds service. Until now a generic warning was emitted that this LED trigger is not supported. But that is not true. -> Skipping trigger 'rssileds' for led '<name>' due to missing kernel module I think this callback should be changed in the future to restart the service. Signed-off-by: Florian Eckert <fe@dev.tdt.de>
* base-files: add new application led trigger backendFlorian Eckert2021-03-051-4/+5
| | | | | | | | | | | | | | | | | For now we have only kernel LED trigger support. With this change it is now possible to use application triggers. If we configure a LED with a non kernel trigger, then we check on every restart and boot of the LED service if we have this trigger as an application in "/usr/libexec/led-trigger". If this file with the name is found, then we execute this to init the LED. Possible use cases are: - Start/Stop/Restart an application led trigger service for this led - Init a LED that is configured by a hotplug script (VPN tunnel established) Signed-off-by: Florian Eckert <fe@dev.tdt.de>
* ramips: rename mtk-hsdma to hsdma-mt7621Ilya Lipnitskiy2021-03-041-2/+2
| | | | | | | | | | | | Follows upstream rename: https://lore.kernel.org/driverdev-devel/20210130034507.2115280-1-ilya.lipnitskiy@gmail.com/ Fixes ramips builds on 5.4.102 Cc: John Audia <graysky@archlinux.us> Cc: David Bauer <mail@david-bauer.net> Cc: Petr Štetiar <ynezz@true.cz> Signed-off-by: Ilya Lipnitskiy <ilya.lipnitskiy@gmail.com>
* bcm63xx-cfe: update to the latest masterRafał Miłecki2021-03-051-3/+3
| | | | | | | 3fb6f1c tp-link: c2300-v1: add cferam file 79f9578 sercomm: vox-2.5: add cferam file Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* fstools: fix build with glibcDaniel Golle2021-03-051-3/+3
| | | | | | | | stropts.h is unavailable under glibc (and unneeded when building against glibc). Include it only if not building against glibc. Reported-by: @DazzyWalkman Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* ipq40xx: net: phy: qca807x: fix GPIO driverRobert Marko2021-03-051-0/+1
| | | | | | | | | | | While rebasing into setting bits instead of magic values, I accidentally forgot to actually set the force bit. Without it using the pins as GPIO-s did not actually work. Fixes: b5c93ed ("ipq40xx: add Qualcomm QCA807x driver") Signed-off-by: Robert Marko <robert.marko@sartura.hr>
* ath79: enable AT803X PHY for kernel 5.10David Bauer2021-03-051-0/+1
| | | | | | | The config symbol for the AT803x device driver was lost when adding kernel 5.10. Signed-off-by: David Bauer <mail@david-bauer.net>
* ath79: replace chipselect workaround with a proper patchDavid Bauer2021-03-052-31/+89
| | | | | | | | | | | Debugging the SPI CS issue with kernel 5.10 resulted in a better understanding for the root cause and a proper patch with a better explanation. Exchange the old hack patch with a more efficient (and upstreamable) solution. Signed-off-by: David Bauer <mail@david-bauer.net>
* arm-trusted-firmware-mediatek: don't try to install absent filesDaniel Golle2021-03-041-6/+0
| | | | | | | | Don't try to install files which no longer exist Since {e,sd}mmc are now produced by ptgen they have been removed. Fixes: 5a3562cd1d ("arm-trusted-firmware-mediatek: remove {e,sd}mmc headers") Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* kernel-5.4: bump to 5.4.102 and refresh patchesJason A. Donenfeld2021-03-0499-617/+94
| | | | | | | | | | | | | | 5.4.102 backported a lot of stuff that our WireGuard backport already did, in addition to other patches we had, so those patches were removed from that part of the series. In the process other patches were refreshed or reworked to account for upstream changes. This commit involved `update_kernel.sh -v -u 5.4`. Cc: John Audia <graysky@archlinux.us> Cc: David Bauer <mail@david-bauer.net> Cc: Petr Štetiar <ynezz@true.cz> Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
* mediatek: mt7622: check firmware metadataDaniel Golle2021-03-042-1/+2
| | | | | | | | | | All mt7622 devices except for the UBI-variant of the mt7622-rfb1 carry metadata appended to the sysupgrade image. Add it for the mt7622-rfb1-ubi as well and check it on sysupgrade to avoid accidentally flashing firmware for the wrong device (or variant or future DEVICE_COMPAT_VERSION). Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* feeds.conf.default: remove freifunk feedPerry Melange2021-03-031-1/+0
| | | | | | | | | | | | | | | | | | | The freifunk feed is being removed becasue a) it is an external project and the OpenWrt team does not have access to it. b) upon original addition of the feed, there was only a very weak tendency for the addition. c) there is a general lack of interest in the freifunk repo to review and/or merge pull requests. d) as far as can be found, all projects which use the freifunk feed have their own make system and self-maintained feeds list. They do not use the feeds.conf.default from the openwrt repo. more information can be read at the following links: http://lists.openwrt.org/pipermail/openwrt-devel/2021-February/033807.html https://github.com/freifunk/openwrt-packages/issues/37 Signed-off-by: Perry Melange <isprotejesvalkata@gmail.com>
* build: add which command to build requirementsPetr Štetiar2021-03-032-1/+4
| | | | | | | | | | | | | | | | | | | `which` utility is not shipped by default for example on recent Arch Linux and then any steps relying on its presence fails, like for example following Python3 prereq build check: $ python3 --version Python 3.9.1 $ make /bin/sh: line 1: which: command not found ... Checking 'python3'... failed. So make `which` utility host build requirement. References: PR#3820 FS#3525 Signed-off-by: Petr Štetiar <ynezz@true.cz>
* Revert "build: replace which with Bash command built-in"Clemens Fruhwirth2021-03-033-4/+4
| | | | | | | | | | | This reverts commit c7aec47e5e3a3ff7b5fdaa11cd1e62cae6746acb. The original commit replaces 'which' with 'command'. Sadly most of them are not equivalent and for 'which -a', there is no easy replacements that would not reimplement PATH parsing logic. Hence revert. Keeping a dependency on which is absolutely fine. Signed-off-by: Clemens Fruhwirth <clemens@endorphin.org>
* build: fix checks for GCC11Petr Štetiar2021-03-031-4/+4
| | | | | | | Fedora 34 already uses GCC11. Reported-by: Marcin Juszkiewicz <marcin-openwrt@juszkiewicz.com.pl> Signed-off-by: Petr Štetiar <ynezz@true.cz>
* build: make GCC version 6+ minimal host build requirementPetr Štetiar2021-03-032-8/+8
| | | | | | | | Currently minimal GNU supported GCC version is 7 (from May 2, 2017), buildbots are using default GCC version 6 on Debian 9 (old stable), current Debian stable has GCC version 8.3.0. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* kernel: generic: add further missing symbolsPetr Štetiar2021-03-031-0/+24
| | | | | | | | Compile testing i.mx6 with ALL_KMODS=y, PACKAGE_perf=y and bunch of tracing/probing symbols has unveiled bunch of missing config options so add them. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* imx6: add 5.10 as testing kernelPetr Štetiar2021-03-031-1/+1
| | | | | | So anyone interested can help with testing. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* imx6: refresh kernel config with 5.10 symbolsPetr Štetiar2021-03-031-4/+37
| | | | | | | | | | | | Just by running `make kernel_oldconfig` and unsetting following options manually as those cores are cortex-a7 based and thus irrelevant for the currently default cortex-a9 used cores. CONFIG_CLK_IMX6SL is not set CONFIG_CLK_IMX6SX is not set CONFIG_CLK_IMX6UL is not set Signed-off-by: Petr Štetiar <ynezz@true.cz>
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-08 08:17:05 +0000