aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* kernel: bump 5.4 to 5.4.70John Audia2020-10-091-2/+2
| | | | | | | | | | | | All modifications made by update_kernel.sh Build system: x86_64 Build-tested: ipq806x/R7800, ath79/generic, bcm27xx/bcm2711 Run-tested: ipq806x/R7800 No dmesg regressions, everything functional Signed-off-by: John Audia <graysky@archlinux.us>
* ath79: drop redundant gpios on i2cAdrian Schmutzler2020-10-092-8/+0
| | | | | | | | | Since "sda-gpios" and "scl-gpios" are only available since kernel 4.19, a few devices have redundantly defined "gpios" to also support older kernels. Since we have nothing older than 4.19 now, we can remove the redundant definitions. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips: drop kernel version switchesAdrian Schmutzler2020-10-093-35/+2
| | | | | | | The ramips target only supports 5.4, so drop all kernel version switches for older kernels there. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* seclic: depends on libsepolDaniel Golle2020-10-091-0/+1
| | | | | | | Add missing dependency for target build of seclic which requires libsepol (just like the host build requires libsepol/host). Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* oxnas: fix qc_prep return in sata driver after kernel 5.4.69Adrian Schmutzler2020-10-091-1/+3
| | | | | | | | | | | | | | | | | | | | | | This fixes a regression after a kernel change in 5.4.69 [1] that led to build failure on oxnas/ox820: drivers/ata/sata_oxnas.c:2238:13: error: initialization of 'enum ata_completion_errors (*)(struct ata_queued_cmd *)' from incompatible pointer type 'void (*)(struct ata_queued_cmd *)' [-Werror=incompatible-pointer-types] .qc_prep = sata_oxnas_qc_prep, ^~~~~~~~~~~~~~~~~~ drivers/ata/sata_oxnas.c:2238:13: note: (near initialization for 'sata_oxnas_ops.qc_prep') Our local driver is changed the same way as prototyped in the kernel patch, i.e. return type is changed and AC_ERR_OK return value is added. [1] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=e11c83520cd04b813cd1748ee2a8f2c620e5f7e3 Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ipq40xx: 5.4: move AR40xx driver into filesRobert Marko2020-10-093-2466/+2460
| | | | | | | | | | | | There is no point in keeping the AR40xx driver as a patch as its not pending merge or backport. To allow for easier maintenance until DSA is ready move it into files like EDMA is. Signed-off-by: Robert Marko <robert.marko@sartura.hr> [combine with removal from patches-5.4] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* config: add option for dssp selinux policyDaniel Golle2020-10-091-1/+4
| | | | Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* selinux-policy: adds new packageDominick Grift2020-10-092-0/+55
| | | | Signed-off-by: Dominick Grift <dominick.grift@defensec.nl>
* secilc: adds new packageDominick Grift2020-10-091-0/+65
| | | | Signed-off-by: Dominick Grift <dominick.grift@defensec.nl>
* rt2x00: mt7620: differentiate based on SoC's CHIP_VERDaniel Golle2020-10-092-0/+547
| | | | | | | | | | | | | | | | | | | | | | | The vendor driver does things differently based on what it finds in the SoC's CHIP_VER register, which should tell whether this is MT7620N or MT7620A (PKG) and probably also the revision (VER) and most likely also something about the silicon implementer (ECO). Introduce codepaths just like the ones in the vendor driver to handle the different chips properly. Some of those paths are most likely dead code and left-overs from FPGA versions or early prototypes of the chip. It'd thus be great if people can post their kernel logs, at least the line telling the chip version and eco, so we know what's actually out there in the wild -- all I could find is [ 0.000000] SoC Type: Ralink MT7620A ver:2 eco:6 and [ 0.000000] SoC Type: Ralink MT7620N ver:2 eco:6 which would make things easier, as then we really just need to know whether it's MT7620N or MT7620A and not care about FPGA or prototypes with ver <= 1 and eco <= 2. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* kernel: clean up XATTR config symbolsPaul Spooren2020-10-0923-29/+4
| | | | | | | | | | | | | Extended attributes are required for overlayfs and have hence been long ago enabled for jffs2, but should be enabled unconditionally for all other filesystems which may potentially serve as overlayfs' upper directory. Previously it was inconsistently added in multiple targets. Add symbols to generic kernel config and remove all *_XATTR symbols from target configs. Signed-off-by: Paul Spooren <mail@aparcar.org> [keep things as they are for squashfs, improve commit message] Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* kernel: sort config-5.4 via kconfig.plPaul Spooren2020-10-091-26/+25
| | | | | | | The options were out of order which makes reviewing of changes harder. Sort it before applying an actual change. Signed-off-by: Paul Spooren <mail@aparcar.org>
* build, imagebuilder: Do not require compilersSven Roederer2020-10-091-0/+4
| | | | | | | | | | | | | The buildroot and SDK both require the compilers (gcc, g++) to be installed on the host system, however the ImageBuilder uses precompiled binaries. This patch changes the prerequirements checks to skip the checking for the compilers if running as ImageBuilder. A similar change has been made for libncurses-dev in 4a1a58a3e2d2. Signed-off-by: Sven Roederer <devel-sven@geroedel.de> Acked-by: Paul Spooren <mail@aparcar.org>
* lantiq: remove model name from LED labelsAdrian Schmutzler2020-10-08105-985/+906
| | | | | | | | | | | | | | | | Like in the previous patches for other targets, this will remove the "devicename" from LED labels in lantiq. The devicename is removed in DTS files and 01_leds, consolidation of definitions into DTSI files is done where (easily) possible, and migration scripts are updated. The DTS/DTSI consolidation is only performed for files-5.4. For lantiq,easy98020 some LED definitions have the form "devicename:function" without the color, so we need to implement explicit migration for that one. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ipq40xx: use upstream DTS files for IPQ4019/AP-DK04.1Adrian Schmutzler2020-10-073-202/+167
| | | | | | | | | | | | | | Upstream provides DTS(I) files for IPQ4019/AP-DK04.1, but we overwrite them with local versions so far. Remove the local files and use patches to be closer to upstream. We already do the same for IPQ40xx/AP-DK01.1-C1. Technically, this changes the compatible from "qcom,ipq4019" to "qcom,ipq4019-dk04.1-c1", but it has never been implemented correctly beforehand anyway. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ipq40xx: improve support for Edgecore ECW5211Sungbo Eo2020-10-075-39/+34
| | | | | | | | | | | | | | | | | | | This adds several stylistic and functional improvements of the recently added Edgecore ECW5211, especially: * Drop the local BDFs as those are already in the upstream under different names * Add SPDX tag to DTS * Add label MAC address * Move LED trigger to DTS * Remove unnecessary status="okay" * Disable unused SS USB phy as the USB port only supports USB 2.0 * Make uboot-env partition writable * Remove qcom,poll_required_dynamic property as the driver does not use it * Tidy up the device recipe Fixes: 4488b260a02e ("ipq40xx: add Edgecore ECW5211 support") Signed-off-by: Sungbo Eo <mans0n@gorani.run> Acked-by: Robert Marko <robert.marko@sartura.hr>
* ipq806x: remove model name from LED labelsAdrian Schmutzler2020-10-0726-211/+217
| | | | | | | | | | Like in the previous patches for ath79 and ramips, this will remove the "devicename" from LED labels in ipq806x. The devicename is removed in DTS files and 01_leds, and a migration script is added. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ipq40xx: remove model name from LED labelsAdrian Schmutzler2020-10-0740-218/+233
| | | | | | | | | | | Like in the previous patches for ath79 and ramips, this will remove the "devicename" from LED labels in ipq40xx. The devicename is removed in DTS files and 01_leds, and a migration script is added. While at it, also harmonize capitalization of wlan2G/wlan5G vs. wlan2g/wlan5g. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ath79: rename ubnt,acb-isp to ubnt,aircube-ispRoman Kuzmitskii2020-10-064-7/+8
| | | | | | | | | | | | Use the full model name for this device to make it easier to recognize for the users and in order to make it consistent with the other devices. While at it, fix sorting in 03_gpio_switches. Signed-off-by: Roman Kuzmitskii <damex.pp@icloud.com> [commit message facelift] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ppp: update to version 2.4.8.git-2020-10-03Hans Dedecker2020-10-051-3/+3
| | | | | | | 2937722 Enable IPv6 by default (#171) 6d39c65 pppd: Fix blank password usage Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
* uhttpd: update to latest Git HEADJo-Philipp Wich2020-10-041-3/+3
| | | | | | | | | | | | | 14a3cb4 ubus: fix legacy empty reply format 0f38b03 client: fix spurious keepalive connection timeouts 88ba2fa client: really close connection on timeout c186212 ubus: support GET method with CORS requests Fixes: FS#3369 Fixes: https://github.com/openwrt/luci/issues/4467 Fixes: https://github.com/openwrt/luci/issues/4470 Fixes: https://github.com/openwrt/luci/issues/4479 Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* toolchain/binutils: update to 2.35.1DENG Qingfang2020-10-046-7/+7
| | | | | | Update binutils 2.35 to 2.35.1 Signed-off-by: DENG Qingfang <dengqf6@mail2.sysu.edu.cn>
* ath79: rename TP-Link TL-WPA8630P v2 (EU) to v2.0 (EU)Adrian Schmutzler2020-10-046-13/+14
| | | | | | | Since we have a v2.1 (EU) with different partitioning now, rename the v2.0 to make the difference visible to the user more directly. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ath79: add support for TP-Link TL-WPA8630P (EU) v2.1Joe Mullally2020-10-0410-10/+91
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This adds support for the TP-Link TL-WPA8630P (EU) in its v2.1 version. The only unique aspect for the firmware compared to v2 layout is the partition layout. Note that while the EU version has different partitioning for v2.0 and v2.1, the v2.1 (AU) is supported by the v2-int image. If you plan to use this device, make sure you have a look at the Wiki page to check whether the device is supported and which image needs to be taken. Specifications -------------- - QCA9563 750MHz, 2.4GHz WiFi - QCA9888 5GHz WiFi - 8MiB SPI Flash - 128MiB RAM - 3 GBit Ports (QCA8337) - PLC (QCA7550) Installation ------------ Installation is possible from the OEM web interface. Make sure to install the latest OEM firmware first, so that the PLC firmware is at the latest version. However, please also check the Wiki page for hints according to altered partitioning between OEM firmware revisions. Notes ----- The OEM firmware has 0x620000 to 0x680000 unassigned, so we leave this empty as well. It is complicated enough already ... Signed-off-by: Joe Mullally <jwmullally@gmail.com> [improve partitions, use v2 DTSI, add entry in 02_network, rewrite and extend commit message] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* omap: update uboot to v2020.04Andre Heider2020-10-041-2/+2
| | | | | | | | | | Fixes the build error: /usr/bin/ld: scripts/dtc/dtc-parser.tab.o:(.bss+0x10): multiple definition of `yylloc'; scripts/dtc/dtc-lexer.lex.o:(.bss+0x0): first defined here collect2: error: ld returned 1 exit status Successfully tested on boneblack. Signed-off-by: Andre Heider <a.heider@gmail.com>
* ramips: fix logic level for DIR-645 buttonsDavid Bauer2020-10-031-2/+2
| | | | | | | | | | | The D-Link DIR-645 currently uses an incorrect logic level for its buttons. Correct them in order to prevent unintentional activation of failsafe mode. Reported-by: Perry Melange <isprotejesvalkata@gmail.com> Signed-off-by: David Bauer <mail@david-bauer.net>
* uboot-rockchip: add Rock Pi 4 supportMarty Jones2020-10-031-0/+11
| | | | | | Add support for the Raxda Rock Pi 4. Signed-off-by: Marty Jones <mj8263788@gmail.com>
* rockchip: add support for Radxa Rock Pi 4Marty Jones2020-10-031-0/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This adds basic support for Radxa Rock Pi 4 Specification: - RAM: 1 GB/ 2 GB/4 GB LPDDR4 - SoC: Rockchip RK3399 - CPU: 64bit hexa core processor Dual Cortex-A72, freqency 1.8Ghz with quad Cortex-A53, frequency 1.4Ghz - USB: USB 3.0 OTG x1 hardware switch for host/device switch, upper one USB 3.0 HOST x1 dedicated USB3.0 channel, lower one USB 2.0 HOST x2 - Ethernet: 1x GbE - Storage: eMMC module uSD card M.2 SSD - Wireless: 802.11 ac wifi Bluetooth 5.0 currently not supported firmware Installation ====================== gzip -d xxx.img.gz, then dd the .img to SD/eMMC ====================== Device Tested: ROCK PI 4 Model B v1.3 Signed-off-by: Marty Jones <mj8263788@gmail.com>
* linux-firmware: update to 20200918David Bauer2020-10-031-3/+3
| | | | | | | | | | | | | | | | | | | 00a84c5 linux-firmware: Update AMD SEV firmware 71338c2 Merge branch 'for-master' of https://github.com/CosmicPenguin/linux-firmware into main 07367b9 linux-firmware: Update firmware file for Intel Bluetooth AX200 1d1586a linux-firmware: Update firmware file for Intel Bluetooth AX201 28b333d linux-firmware: Update firmware file for Intel Bluetooth 9560 db30380 linux-firmware: Update firmware file for Intel Bluetooth 9260 eb3aa1f Mellanox: Add new mlxsw_spectrum firmware xx.2008.1310 ec88f05 mediatek: update MT7915 firmware to 20200819 a9993f8 brcm: Fix a stale symlink for RPi3 model b+ f48fec4 qcom: Add updated a5xx and a6xx microcode d5f9eea wl18xx: update firmware file 8.9.0.0.83 7a237c6 linux-firmware: mt7615: update firmware to 20200814 version 74bd44f amdgpu: add navi12 firmware from 20.30 b9f69cd amdgpu: update navi10 firmware for 20.30 Signed-off-by: David Bauer <mail@david-bauer.net>
* rockchip: enable Realtek PHY supportDavid Bauer2020-10-031-0/+1
| | | | | | | The NanoPi R2S features a Realtek Gigabit Ethernet PHY. Enable the Realtek specific PHY driver to correctly configure internal delays. Signed-off-by: David Bauer <mail@david-bauer.net>
* rockchip: fix NanoPi R2S PHY IDDavid Bauer2020-10-031-1/+1
| | | | | | | Fix the PHY ID for the NanoPi R2S PHY compatible to match the used PHY. The ID was wrong as I've accidentally picked the wrong upstream patch. Signed-off-by: David Bauer <mail@david-bauer.net>
* Revert "uboot-rockchip: update NanoPi R2S patches"David Bauer2020-10-034-191/+124
| | | | | | | | | This reverts commit bda6f6572be630bcf9a1c8a429e40d8a53033af5. This commit breaks the onboard ethernet on some units. Revert it for now. Signed-off-by: David Bauer <mail@david-bauer.net>
* kernel: bump 5.4 to 5.4.69John Audia2020-10-0271-203/+177
| | | | | | | | | | | | | | | | | | | | | | Seemingly unneeded based on new upstream code so manually deleted: layerscape: 820-usb-0007-usb-dwc3-gadget-increase-timeout-value-for-send-ep-c.patch Manually merged: generic-hack: 251-sound_kconfig.patch All other modifications made by update_kernel.sh Build system: x86_64 Build-tested: ipq806x/R7800, ath79/generic, bcm27xx/bcm2711 Run-tested: ipq806x/R7800, lantiq/Easybox 904 xDSL No dmesg regressions, everything functional Signed-off-by: John Audia <graysky@archlinux.us> [add lantiq test report, minor commit message clarification] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* layerscape: add layerscape's SATA driver packagePawel Dembicki2020-10-023-2/+25
| | | | | | | | | | | This patch intruduce SATA support for layerscape devices. Target specific package with ahci_qoriq driver was added to local modules.mk. Kmod package was added to default packages for devices with SATA interface. Signed-off-by: Pawel Dembicki <paweldembicki@gmail.com> Reviewed-by: Yangbo Lu <yangbo.lu@nxp.com>
* layerscape: add missing kmods for i2c peripherialsPawel Dembicki2020-10-021-6/+18
| | | | | | | | This patch adds kmod-hwmon-ina2xx kmod-hwmon-lm90 for boards, which have it installed. Signed-off-by: Pawel Dembicki <paweldembicki@gmail.com> Reviewed-by: Yangbo Lu <yangbo.lu@nxp.com>
* uboot-layerscape: fix LS1012A-FRDM fdt_high valuePawel Dembicki2020-10-022-2/+2
| | | | | | | | | | | | LS1012A-FRDM have configured wrong fdt_high value. That causes impossibility of booting. This patch fix it. Signed-off-by: Pawel Dembicki <paweldembicki@gmail.com> Reviewed-by: Yangbo Lu <yangbo.lu@nxp.com> [bump PKG_RELEASE] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips: remove set_wifi_led function in 01_ledsAdrian Schmutzler2020-10-026-77/+53
| | | | | | | | | | | | | | | | | | | While we mostly use the ucidef_set_led_* functions directly in 01_leds we still have the set_wifi_led function in parallel for several old devices. This is not only inconsistent with the other definitions, it also links to the wlan0 interface instead of using a phy trigger which would be independent of the interface name (and is used for all newer devices anyway). Apart from that, the standard names "wifi" and "wifi-led" are not very helpful in a world with different radio bands either. Thus, this patch removes the set_wifi_led function and puts the relevant commands into the cases explicitly. This makes the mechanism used more evident and will hopefully lead to some future improvements or at least prevent some copy-pasting of the old setups. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips: remove option to set WiFi LED via aliasesAdrian Schmutzler2020-10-027-21/+5
| | | | | | | | | | | | | In ramips, it's not common to use an alias for specifying the WiFi LED; actually only one device uses this mechanism (TL-WR841N v14). Particularly since the WiFi LEDs are typically distinguished between 2.4G and 5G etc. it is also not very useful for this target. Thus, this patch removes the setup lines for this mechanism and converts the TL-WR841N v14 to the normal setup. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips: remove model name from LED labelsAdrian Schmutzler2020-10-02379-3123/+1975
| | | | | | | | | | | | | | | | | Like in the previous patch for ath79 target, this will remove the "devicename" from LED labels in ramips as well. The devicename is removed in DTS files and 01_leds, consolidation of definitions into DTSI files is done where (easily) possible, and migration scripts are updated. For the latter, all existing definitions were actually just devicename migrations anyway. Therefore, those are removed and a common migration file is created in target base-files. This is actually another example of how the devicename removal makes things easier. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* base-files: allow exceptions when removing devicename from LEDsAdrian Schmutzler2020-10-022-3/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Without the model-based devicename for LEDs, there are still cases where a third component is required, typically when it refers to internal "devices" like phys etc. An example are the following two found on ramips: - rt2800soc-phy0::radio - rt2800pci-phy0::radio So far, the rt2800*-phy: prefixes would be removed by the devicename removal ("migration") script, and the configuration for these LEDs would be broken. To address this, this patch allows to add arguments to a call of remove_devicename_leds, which will be compared against the first part of the LED names/labels, and then be ignored by the routine, and thus not removed: remove_devicename_leds "rt2800soc-phy0" "rt2800pci-phy0" This mechanism is supposed to be used when a "devicename" applies to several devices. If only a single device is affected, it might be more effective to use a case statement and exclude the device from migration by that entirely. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* netfilter: ship nft_chain_nat on 5.1+ kernelsJo-Philipp Wich2020-10-021-5/+6
| | | | | | | | | | | | | | The former nft_chain_nat_ipv4 and nft_chain_nat_ipv6 modules have been merged into a common nft_chain_nat module starting with Linux 5.1. Ensure that this common module is shipped along with kmod-nft-nat on recent kernels. While we're at it, also apply version constraints to other nft modules that have been merged into the core with newer kernels. Ref: https://bugs.openwrt.org/index.php?do=details&task_id=2815#comment8016 Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* ath79: remove model name from LED labelsAdrian Schmutzler2020-10-02241-1487/+1334
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Currently, we request LED labels in OpenWrt to follow the scheme modelname:color:function However, specifying the modelname at the beginning is actually entirely useless for the devices we support in OpenWrt. On the contrary, having this part actually introduces inconvenience in several aspects: - We need to ensure/check consistency with the DTS compatible - We have various exceptions where not the model name is used, but the vendor name (like tp-link), which is hard to track and justify even for core-developers - Having model-based components will not allow to share identical LED definitions in DTSI files - The inconsistency in what's used for the model part complicates several scripts, e.g. board.d/01_leds or LED migrations from ar71xx where this was even more messy Apart from our needs, upstream has deprecated the label property entirely and introduced new properties to specify color and function properties separately. However, the implementation does not appear to be ready and probably won't become ready and/or match our requirements in the foreseeable future. However, the limitation of generic LEDs to color and function properties follows the same idea pointed out above. Generic LEDs will get names like "green:status" or "red:indicator" then, and if a "devicename" is prepended, it will be the one of an internal device, like "phy1:amber:status". With this patch, we move into the same direction, and just drop the boardname from the LED labels. This allows to consolidate a few definitions in DTSI files (will be much more on ramips), and to drop a few migrations compared to ar71xx that just changed the boardname. But mainly, it will liberate us from a completely useless subject to take care of for device support review and maintenance. To also drop the boardname from existing configurations, a simple migration routine is added unconditionally. Although this seems unfamiliar at first look, a quick check in kernel for the arm/arm64 dts files revealed that while 1033 lines have labels with three parts *:*:*, still 284 actually use a two-part labelling *:*, and thus is also acceptable and not even rare there. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* base-files: add function to remove devicename from LED labelsAdrian Schmutzler2020-10-022-1/+24
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Currently, we request LED labels in OpenWrt to follow the scheme modelname:color:function However, specifying the modelname at the beginning is actually entirely useless for the devices we support in OpenWrt. In patches subsequent to this one, we will thus remove the modelname from the label definitions on various targets. To migrate the existing definitions from older installations, a migration script needs to be deployed that does modelname:color:function -> color:function e.g. dir-789:green:status -> green:status This patch introduces two functions that do exactly that: For each entry in /etc/config/system, the routine will check whether two (or more) colons are present, and then remove everything up to (and including) the first colon. For now, this will be applied unconditionally, i.e. if the function is called for a device, all labels will be cut like this. However, for a future case of mixed three-part and two-part labels, it should not be too hard to provide a function argument with exceptions to the removal. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* lantiq: move dts-v1 statement to top-level DTSI filesAdrian Schmutzler2020-10-0171-139/+24
| | | | | | | | | | | | | | | | | | | The "/dts-v1/;" identifier is supposed to be present once at the top of a device tree file after the includes have been processed. In lantiq, we therefore requested to have in the DTS files so far, and omit it in the DTSI files. However, essentially the syntax of the parent SoC-based DTSI files already determines the DTS version, so putting it into the DTS files is just a useless repetition. Consequently, this patch puts the dts-v1 statement into the top-level SoC-based DTSI files, and removes all other occurences. Since the dts-v1 statement needs to be before any other definitions, this also moves the includes accordingly where necessary. Changes are applied to files-5.4 only, files-4.19 remains untouched. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* policycoreutils: add missing gettext dependencyPaul Spooren2020-10-011-2/+2
| | | | | | | Add missing build dependency to both host and target build. The `msgfmt` is required which is missing without gettext-full. Signed-off-by: Paul Spooren <mail@aparcar.org>
* ath79: ar8216: make switch register access atomicChuanhong Guo2020-09-301-0/+59
| | | | | | | | | | | | | | | | | | | reg accesses on integrated ar8229 sometimes fails. As a result, phy read got incorrect port status and wan link goes down and up mysteriously. After comparing ar8216 with the old driver, these local_irq_save/restore calls are the only meaningful differences I could find and it does fix the issue. The same changes were added in svn r26856 by Gabor Juhos: ar71xx: ag71xx: make switch register access atomic As I can't find the underlying problem either, this hack is broght back to fix the unstable link issue. This hack is only suitable for ath79 mdio and may easily break the driver on other platform. Limit it to ath79-only as a target patch. Fixes: FS#2216 Fixes: FS#3226 Signed-off-by: Chuanhong Guo <gch981213@gmail.com>
* refpolicy: fix path to setfiles and checkpolicyPaul Spooren2020-09-301-3/+2
| | | | | | | | Directly set path via MAKE vars instead of defning TESTTOOLS. This way setfiles, which is required by the ImageBuilder, ends up in /host/bin while checkpolicy can stay in hostpkg/bin. Signed-off-by: Paul Spooren <mail@aparcar.org>
* rockchip: rk3328: add compatible to NanoPi R2S ethernet PHYDavid Bauer2020-09-303-3/+28
| | | | | | | | This adds the compatible property to the NanoPi R2S ethernet PHY node. Otherwise, the PHY might not be probed, as the PHY ID reads all 0xff when it is still in reset. Signed-off-by: David Bauer <mail@david-bauer.net>
* uboot-rockchip: update NanoPi R2S patchesDavid Bauer2020-09-304-123/+191
| | | | | | | | Update the patches required for the NanoPi R2S to match the DTS accepted for upstream Linux. The U-Boot patch meanwhile is still pending upstream. Signed-off-by: David Bauer <mail@david-bauer.net>
* mac80211: add support for specifying a per-device scan listFelix Fietkau2020-09-292-0/+3
| | | | | | | This is useful to bring up multiple client mode interfaces on a single channel much faster without having to scan through a lot of channels Signed-off-by: Felix Fietkau <nbd@nbd.name>