sync 9/8 #151
Merged
sync 9/8 #151
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
While discussions are still ongoing, update the block NVMEM provider patchset to the level submitted upstream to allow testing and validation. Link: https://patchwork.kernel.org/project/linux-block/list/?series=875202 Signed-off-by: Daniel Golle <[email protected]>
68c8a4f system-linux: re-apply ethtool on phy attachment 890929b wireless: add support for defining wifi interfaces via procd service data b57e40b wireless: use blobmsg_parse_attr 7a6532f proto-shell: add proto property for skipping device config 33ec3da CMake: bump the minimum required CMake version to 3.5 Signed-off-by: Daniel Golle <[email protected]>
CI says patches need to be refreshed, so do so. Fixes: 6bb334c ("mediatek: fix u-boot env layout NVMEM definitions") Link: openwrt#16051 Signed-off-by: Robert Marko <[email protected]>
Let's start wide tests 6.6 kernel. Signed-off-by: Pawel Dembicki <[email protected]> Link: openwrt#16037 Signed-off-by: Robert Marko <[email protected]>
Layerscape was switched to 6.6 kernel. Now is time to remove 6.1 support. Signed-off-by: Pawel Dembicki <[email protected]> Link: openwrt#16037 Signed-off-by: Robert Marko <[email protected]>
Replace downstream RealTek PHY patches with backported ones. Signed-off-by: Álvaro Fernández Rojas <[email protected]>
This reverts commit f444dea. It seems that some devices using GPIO WDT have really short WDT timeouts and when using module_platform_driver registration it happens too late and thus WDT will timeout and reset the board. So, for now lets return the postcore_initcall hack for now. Fixes: f444dea ("ath79: remove GPIO driver earlier registration hack") Signed-off-by: Joan Moreau <[email protected]> Link: openwrt#16035 Signed-off-by: Robert Marko <[email protected]>
This target doesn't actually use NAND. Signed-off-by: Brian Norris <[email protected]> Link: openwrt#16001 Signed-off-by: Robert Marko <[email protected]>
This backports patches dt-bindings: firmware: add cznic,turris-omnia-mcu binding platform: cznic: Add preliminary support for Turris Omnia MCU platform: cznic: turris-omnia-mcu: Add support for MCU connected GPIOs platform: cznic: turris-omnia-mcu: Add support for poweroff and wakeup platform: cznic: turris-omnia-mcu: Add support for MCU watchdog platform: cznic: turris-omnia-mcu: Add support for MCU provided TRNG ARM: dts: turris-omnia: Add MCU system-controller node ARM: dts: turris-omnia: Add GPIO key node for front button platform: cznic: turris-omnia-mcu: Depend on OF platform: cznic: turris-omnia-mcu: Depend on WATCHDOG platform: cznic: turris-omnia-mcu: fix Kconfig dependencies that will be released in 6.11 into mvebu/patches-6.6. Signed-off-by: Marek Behún <[email protected]> Link: openwrt#13799 Signed-off-by: Robert Marko <[email protected]>
Handle the KEY_VENDOR key in gpio-button-hotplug driver. This is used by Turris Omnia. Signed-off-by: Marek Behún <[email protected]> Link: openwrt#13799 Signed-off-by: Robert Marko <[email protected]>
Add support for the MCU driver on CZ.NIC's Turris Omnia. This adds the ability to do a true board poweroff, and to configure various features (for example the user may configure that after poweroff, the router should automatically wake up at a specific time). Signed-off-by: Marek Mojík <[email protected]> Signed-off-by: Marek Behún <[email protected]> Link: openwrt#13799 Signed-off-by: Robert Marko <[email protected]>
Add a new package, omnia-mcu-firmware, containing firmware binaries for the microcontroller on the Turris Omnia router. Signed-off-by: Marek Mojík <[email protected]> Signed-off-by: Marek Behún <[email protected]> Link: openwrt#13799 Signed-off-by: Robert Marko <[email protected]>
Add a new utility, omnia-mcutool, which main purpose is to upgrade the firmware on the microcontroller on the Turris Omnia router. Depends on omnia-mcu-firmware, and the upgrade process is pretty simple: omnia-mcutool --upgrade Besides firmware upgrade, the utility can be used to show and configure various firmware settings. Signed-off-by: Marek Mojík <[email protected]> Signed-off-by: Marek Behún <[email protected]> Link: openwrt#13799 Signed-off-by: Robert Marko <[email protected]>
This patch backports fixes for a security vulnerability impacting the hostapd implementation of SAE H2E. As upgrading hostapd would require more testing, the second mitigation step which involves backporting several patches was adopted as outlined in the official advisory[1]. An explanation of the impact of the vulnerability is provided from the advisory[1]: This vulnerability allows the attacker to downgrade the negotiated group to another enabled group if both the AP and STA have enabled SAE H2E and multiple groups. It should be noted that the H2E option is not enabled by default and the attack is not applicable to the default option, i.e., hunting-and-pecking, since it does not have any downgrade protection for group negotiation. In addition, the default configuration for enabled SAE groups in hostapd is to enable only a single group, so the vulnerability is not applicable unless hostapd has been explicitly configured to enable more groups for SAE. [1]: https://w1.fi/security/2024-2/sae-h2h-and-incomplete-downgrade-protection-for-group-negotiation.txt Signed-off-by: Rany Hany <[email protected]> Link: openwrt#16042 Signed-off-by: Hauke Mehrtens <[email protected]>
Switch to Linux kernel version 6.6. Signed-off-by: Mieczyslaw Nalewaj <[email protected]> Link: openwrt#16030 Signed-off-by: Robert Marko <[email protected]>
Drop config for Linux 6.1. Signed-off-by: Mieczyslaw Nalewaj <[email protected]> Link: openwrt#16030 Signed-off-by: Robert Marko <[email protected]>
Enabling KERNEL_DEBUG_INFO_BTF and KERNEL_KPROBE_EVENTS on 6.6 exposes CONFIG_PROBE_EVENTS_BTF_ARGS in the kernel config. Add a build option for it to fix build failures with KERNEL_DEBUG_INFO_BTF and KERNEL_KPROBE_EVENTS enabled on targets using the 6.6 kernel. Signed-off-by: Stijn Tintel <[email protected]>
Use realtek,extif property instead of realtek,extif0 and realtek,extif1 by extending it with the cpu_port parameter. The extif number is automatically calculated based on cpu_port. Signed-off-by: Mieczyslaw Nalewaj <[email protected]> Link: openwrt#15749 Signed-off-by: Hauke Mehrtens <[email protected]>
Remove the rlvid analysis because for the rtl8367b family chips supported by the driver (rtl8367rb and rtl8367r-vb), rlvid is always equal to 1. So the code for rlvid equal to 0 is completely unnecessary. Signed-off-by: Mieczyslaw Nalewaj <[email protected]> Link: openwrt#15749 Signed-off-by: Hauke Mehrtens <[email protected]>
Store the chip type in smi->rtl8367b_chip Signed-off-by: Mieczyslaw Nalewaj <[email protected]> Link: openwrt#15749 Signed-off-by: Hauke Mehrtens <[email protected]>
Use realtek,extif property instead of realtek,extif0 to extif2 by extending it with the cpu_port parameter. The extif number is automatically calculated based on cpu_port. Signed-off-by: Mieczyslaw Nalewaj <[email protected]> Link: openwrt#15749 Signed-off-by: Hauke Mehrtens <[email protected]>
6.6.44 introduced breakage complaining about missing mtd_test.ko for some targets. Signed-off-by: John Audia <[email protected]> Link: openwrt#16061 Signed-off-by: Hauke Mehrtens <[email protected]>
Changelog: https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.44 Removed upstreamed: rockchip/patches-6.6/044-v6.11-arm64-dts-rockchip-Add-sdmmc-related-properties-on-r.patch[1] rockchip/patches-6.6/045-v6.11-arm64-dts-rockchip-Add-pinctrl-for-UART0-to-rk3308-r.patch[2] rockchip/patches-6.6/046-v6.11-arm64-dts-rockchip-Add-mdio-and-ethernet-phy-nodes-t.patch[3] rockchip/patches-6.6/048-v6.11-arm64-dts-rockchip-Update-WIFi-BT-related-nodes-on-r.patch[4] rockchip/patches-6.6/310-PCI-dw-rockchip-Fix-initial-PERST-GPIO-value.patch[5] Manually rebased: bcm27xx/patches-6.6/950-0526-mfd-Add-rp1-driver.patch ramips/patches-6.6/810-uvc-add-iPassion-iP2970-support.patch All other patches automatically rebased. 1. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v6.6.44&id=96155dc8c99e76a0e58932ca5f88148a37af3617 2. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v6.6.44&id=30ee9e5ecc5fd6854a1690ab11e6e6b4851ac9ab 3. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v6.6.44&id=0c4c1b7daf23bccf0da5b65b3cd5b32bfa5a5af4 4. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v6.6.44&id=a86a5685675834732789df202e73153db59d8dcc 5. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v6.6.44&id=a30211c6704899de0616ac0f97601122d899c86d Build system: x86/64 Build-tested: x86/64/AMD Cezanne Run-tested: x86/64/AMD Cezanne Signed-off-by: John Audia <[email protected]> Link: openwrt#16061 Signed-off-by: Hauke Mehrtens <[email protected]>
fixes: ath11k: fix peer addition/deletion error on sta band migration: d673cb6fe6c03b2be157cc6c5db40481828d282d the fix for sta band migration raises a new bug which causes the wifi firmware to crash if you switch between 2 bssid's on the same band. this is usually caused since the firmware observes 2 stations with the same bss Signed-off-by: Sebastian Gottschall <[email protected]>
Bump omnia-mcutool to 0.3-rc3: * The `--upgrade` option will now work even if MCU is in bootloader (for example if previous upgrade was aborted). * On boards with GD32 MCUs, `omnia-mcutool` will now refuse to upgrade application firmware to version lower than 4.1 if bootloader version is 2.0 (the original for first batch of boards with GD32 MCUs) since these versions of application and bootloader are not compatible. If user already upgraded to such a combination, an upgrade of bootloader firmware is required. The `--upgrade` option will inform about this and will automatically upgrade bootloader firmware if the `--force` option is given. (Note that version 4.1 of the MCU firmware was will be released soon, once it is properly tested.) * Various other improvements. Signed-off-by: Marek Behún <[email protected]> Link: openwrt#16086 Signed-off-by: Robert Marko <[email protected]>
Compilation of mtd_test.ko should be added only for kernel 6.6 or above. Fixes 26df88a ("kernel: Add kmod-mfd-test") Signed-off-by: Mieczyslaw Nalewaj <[email protected]> Link: openwrt#16085 Signed-off-by: Robert Marko <[email protected]>
Move v6.11 backported bmips CBR patches from bmips target to generic. Signed-off-by: Álvaro Fernández Rojas <[email protected]>
This adds auto-configuration of network ports on Dell EMC Edge620 (x86) product. It is similar in specs/features to some of the Sophos x86-based appliances, but: 1. Serial console terminal is built in and requires just the micro-USB cable 2. Comes with both MMC (16Gb) and SSD (256Gb) installed 3. Comes with 6 ethernet ports all 6 are functional when no SFP is used 4. Comes with two SFP cages and not one, like some of revision 3 Sophos products 5. Unlike Sophos devices, there are no non-wireless models of Edge 620, it comes with Qualcomm Atheros QCA9880 radio These devices can be now found both second-hand and new at online marketplaces below (sometimes well below) US $100, I believe they make great candidates for running OpenWrt. The ethernet network ports on the case are marked GE1 thru to GE6 with the following mapping once booted into OpenWrt: ``` GE1: eth2: pci0000:00/0000:00:0b.0/0000:02:00.2 GE2: eth3: pci0000:00/0000:00:0b.0/0000:02:00.3 GE3: eth0: pci0000:00/0000:00:0b.0/0000:02:00.0 GE4: eth1: pci0000:00/0000:00:0b.0/0000:02:00.1 GE5: eth7: pci0000:00/0000:00:17.0/0000:07:00.1 GE6: eth6: pci0000:00/0000:00:17.0/0000:07:00.0 ``` Dell's instructions for [standard configuration](https://infohub.delltechnologies.com/en-us/l/dell-emc-edge-620-advanced-activation-guide/dell-emc-sd-wan-edge-620-standard-configuration/) recommend using GE3, GE4, GE5, or GE6 for WAN, I've selected the GE6 as the sole WAN port under OpenWrt with the rest of ethernet ports assigned to LAN. Please merge before 24.xx is forked and if possible, cherry-pick for 23.05 if there's no ETA for 24.xx forking. PS. @Hurricos I'm struggling with ixgbe mappings on Sophos devices which use very similar hardware to Dell EMC, so even tho I know the sys paths for ethernet ports, I'd prefer to do a separate commit to properly map ethernet ports to match the case markings for this device at some point later. Signed-off-by: Stan Grishin <[email protected]>
Initially APK would sign packages and package index and verify signatures individually. With the latest change, all packages inside a trusted index are automatically trusted. This is important within the OpenWrt eco-system since signing the index happens on another machine than the package creation. Signed-off-by: Paul Spooren <[email protected]>
The patches were generated from the RPi repo with the following command: git format-patch v6.6.44..rpi-6.6.y Signed-off-by: Álvaro Fernández Rojas <[email protected]>
Signed-off-by: Sean Khan <[email protected]>
There was logic that was initially included in the coconut branch of QSDK for older mac80211 NSS implementation. It was brought over to address an issue with ath10k where during heavy traffic, AP would trigger `failed to increase tx pending count: -16, dropping`. The issue was actually caused by `skb_recyler` malforming some packets. Disabling `skb_recyler` fixed the error, and therefore the logic regarding `skb_queue_len(&local->pending[q]) >= 1000` can be reverted to match what is currently upstream with QSDK. Alsi refreshed remaning patches after rebase. Signed-off-by: Sean Khan <[email protected]>
Signed-off-by: Sean Khan <[email protected]>
Every 100 milliseconds, the station sends an "association request" and the AP adds the peer and the AP responds to the station with an "association response". But "association response" takes time to reach the station. Because of this, the station sends another "association request" to the AP. In the second associate request, the AP removes the peer and re-adds the station. Meanwhile, "association response" is reached to station and station sends "QoS NULL" frame to AP. The moment the station sends a QoS NULL frame to the ap, the peer on the AP is deleted and the AP sends a de-authentication to the station. To fix this issue, increased the assoc timeout period from 100 milli- seconds to 500 milli seconds. Signed-off-by: Sean Khan <[email protected]>
There is an issue when enabling thermal support on newer ath11k firmware. TX/RX rates are being limited, often times 50% of client's HE capabilities. The issue stems from a mismatch in WMI API structure. The range to throttle is currently "-100°C" to "150°C", this essentially means "always" throttle. Integrate patch from dd-wrt which adds missing WMI structures and proper thermal ranges for IPQ5018, IPQ807x, and QCN9000. Patch-by: Sebastian Gottschall <[email protected]> Signed-off-by: Sean Khan <[email protected]>
Signed-off-by: qosmio <[email protected]>
Signed-off-by: Sean Khan <[email protected]>
github-actions
bot
added
target/qualcommax
kernel
core packages
target/ath79
target/bcm27xx
target/ipq40xx
target/mediatek
target/ramips
target/rockchip
build/scripts/tools
target/bcm47xx
target/mvebu
target/lantiq
target/layerscape
target/x86
target/zynq
target/mpc85xx
target/apm821xx
target/sunxi
target/bmips
target/archs38
labels
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Thanks for your contribution to OpenWrt!
To help keep the codebase consistent and readable,
and to help people review your contribution,
we ask you to follow the rules you find in the wiki at this link
https://openwrt.org/submitting-patches
Please remove this message before posting the pull request.