sync 10/5 #117
Merged
sync 10/5 #117
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
To fix issue openwrt#15304 Correct br-lan ports 1-4 so that phy-handle matches reg nr not port label. Fixes: eb13076 ("mediatek: fix DTS defining mt7530 switch phys but not referencing them") Signed-off-by: Magnus Lindström <[email protected]>
The way to register the switch MDIO bus and PHYs on the bus in upstream Linux is more strict and requires each PHY to explicitely state the interrupt instead of assuming it in case the 'interrupts' property in DT is missing. Add missing interrupts for the PHYs of the build-in 4x1GE switch of the MT7988 SoC. Fixes: 4354b34 ("generic: 6.6: sync mt7530 DSA driver with upstream") Signed-off-by: Daniel Golle <[email protected]>
The 'nandbiterrs' tool is useful to find out of bit error correction of NAND is working as expected by deliberately introducing bit errors and telling up to which number they can be corrected. Enable build of the testing tools and package the 'nandbiterrs' tool as part of the nand-utils package. Signed-off-by: Daniel Golle <[email protected]>
cfe137be068a uci: remove incorrectly documentated reorder() parameter e8d78a26da0c lib: introduce socket library a0ad1d127ae6 build: fix symbol and library detection 674f65ee551d jsdoc: disable default module titles a33d16a86493 socket: rework error handling e2b81d869222 uloop: add documentation 953f36c96e8a socket: make socket.send() accept non-string data f211d5ac666f ubus: fix uc_ubus_have_uloop for eloop+uloop combination 0662de64bd1f socket: add AF_PACKET socket type support b594ff8a2841 socket: remove leftover debug code 0d823e702bfe socket: fix addrinfo() with omitted service argument Signed-off-by: Jo-Philipp Wich <[email protected]>
Currently, a lot of boards are still not using the existing label to reference the watchdog node, so lets rectify this. Link: openwrt#15415 Signed-off-by: Robert Marko <[email protected]>
Currently, a lot of boards are still not using the existing label to reference the prng node, so lets rectify this. Link: openwrt#15415 Signed-off-by: Robert Marko <[email protected]>
Currently, a lot of boards are still not using the existing label to reference the crypto node, so lets rectify this. Link: openwrt#15415 Signed-off-by: Robert Marko <[email protected]>
WPJ419 is still manually defining dma nodes(And even some labels), so lets convert it to use the existing upstream labels for DMA nodes. Link: openwrt#15415 Signed-off-by: Robert Marko <[email protected]>
This device does not have NAND enabled at all and NAND is the only consumer of QPIC BAM DMA, so drop the node. Link: openwrt#15415 Signed-off-by: Robert Marko <[email protected]>
Some boards are still defininig UART nodes under soc instead of using the existing upstream labels to reference them so convert them. Link: openwrt#15415 Signed-off-by: Robert Marko <[email protected]>
Some boards are still defininig I2C nodes under soc instead of using the existing upstream labels to reference them so convert them. Link: openwrt#15415 Signed-off-by: Robert Marko <[email protected]>
Some boards are still defining MDIO nodes under soc instead of using the existing upstream labels to reference them so convert them. Link: openwrt#15415 Signed-off-by: Robert Marko <[email protected]>
WPJ419 is still manually defining PCIe node, so lets convert it to use the existing upstream labels for PCIe node and while we are here use the -gpios suffix instead. Link: openwrt#15415 Signed-off-by: Robert Marko <[email protected]>
WPJ419 is still manually defining pinctrl node, so lets convert it to use the existing upstream labels for pinctrl node. Link: openwrt#15415 Signed-off-by: Robert Marko <[email protected]>
WPJ419 is still manually defining SPI node, so lets convert it to use the existing upstream labels for SPI node. Link: openwrt#15415 Signed-off-by: Robert Marko <[email protected]>
Switch to Linux kernel version 6.6 and drop configs, files and patches for Linux 6.1. Signed-off-by: Tianling Shen <[email protected]>
New: - mold is now up to 10% faster when linking very large, debug info-enabled executables such as Blender (~1.8 GiB) or Clang (~3.8 GiB), thanks to several improvements we've made to the string merging algorithm. (53ebcd8, d714301, 40f6b17, c9faf3d) - -z start-stop-visibility=hidden is now supported so that linker-synthesized __start_<section-name> and __stop_<section-name> symbols can be completely hidden from other ELF modules. Previously, only -z start-stop-visibility=protected was supported. (99a5b15) - -Bsymbolic-non-weak and -Bsymbolic-non-weak-functions options are now supported for compatibility with LLVM lld. Just like lld, these options control which symbols are exported as dynamic symbols. -Bsymbolic-non-weak makes the linker to export only weak symbols, whereas -Bsymbolic-non-weak-functions makes it to export only weak function symbols. (7d17aa8) Bug fixes and compatibility improvements: - Previously, if a linker script contains a newline character in the beginning four bytes of a file, it was not recognized as a linker script by mold. Now, mold allows newlines at the beginning of a file. (ea054cc) - Under rare circumstances, the INPUT linker script command may have found a different file than GNU ld would. Now, mold's behavior aligns with GNU ld's. (163975d) - Previously, the --repro option produced corrupted tar files. Now the bug has been fixed. (32c4a09) - mold generally guarantees that its output is reproducible, meaning that if you run the linker with the exact same command line options and input files, the output is guaranteed to be bit-for-bit identical to the previous outputs. However, under rare circumstances, it might produce different output due to a bug. It's reported that this nondeterminism caused random crashes for some programs (openwrt#1247). This bug has been fixed. (6463a7c) - mold no longer sets the address of the .text section as the entry point address if --entry option is not given, just like LLVM lld. (020b1a7) - [RISC-V] __global_pointer$ symbol is now exported from executables as required by the processor-specific ABI. (3df7c8e) - [ARM32] --long-plt option is now recognized as known option by mold. mold ignores the option, though, because the PLTs generated by our linker is always long. (d432e98) Release Notes: https://github.com/rui314/mold/releases/tag/v2.31.0 Signed-off-by: Sean Khan <[email protected]> Link: openwrt#15403 Signed-off-by: Robert Marko <[email protected]>
…q806x Backport patch merged upstream for rgmii-id support in stmmac-ipq806x. This is needed for some device that directly connets PHY to the gmac port and require rgmii-id phy-modes. Signed-off-by: Christian Marangi <[email protected]>
- update dropbear to latest stable 2024.85; for the changes see https://matt.ucc.asn.au/dropbear/CHANGES - drop cherry-picked patches (merged in release 2024.84) - refresh remaining patches Tested-by: Stijn Segers <[email protected]> Signed-off-by: Konstantin Demin <[email protected]>
don't mention SHA1 in order to not confuse users - SHA1 support is already disabled (except RSA-SHA1 signagures). ref: openwrt#15281 Signed-off-by: Konstantin Demin <[email protected]>
Continuation of commit 8b66f1a. Set the switch address on the MDIO bus to 31. This is required for all boards currently working with the mt7530 DSA driver. Fixes: openwrt#15419 Signed-off-by: Mieczyslaw Nalewaj <[email protected]>
Rename from mt7621_dlink_dir-xx60-a1.dtsi to mt7621_dlink_dir_nand_128m.dtsi and associated group name when creating the mt7621.mk image Co-authored-by: Alan Luck <[email protected]> Signed-off-by: Mieczyslaw Nalewaj <[email protected]>
Abandoning the label and using the function/color syntax for some dlink dir series routers: dir-1960-a1, dir-2660-a1, dir-2640-a1, dir-3040-a1 and dir-3060-a1 Signed-off-by: Mieczyslaw Nalewaj <[email protected]>
Setting the LED name and abandoning the label and using the function/color syntax for some TP-Link Archer series routers: Archer C2 v1, Archer C20 v1, Archer C20i and Archer C50 v1 Signed-off-by: Mieczyslaw Nalewaj <[email protected]>
Hardware Specification: SoC: Mediatek MT7621DAT (MIPS1004Kc 880 MHz, dual core) RAM: 128 MB Storage: 128 MB NAND flash Ethernet: 5x 10/100/1000 Mbps LAN1,LAN2,LAN3,LAN4 & WAN Wireless: 2.4GHz: Mediatek MT7603EN up to 300Mbps (802.11b/g/n MIMO 2x2) Wireless: 5GHz: Mediatek MT7615N up to 1733Mbps (802.11n/ac MU-MIMO 4x4) LEDs: Power (white & amber), Internet (white & amber) LEDs: 2.4G (White), 5Ghz (White) Buttons: WPS, Reset MAC Table Label xx:xx:xx:xx:xx:EB LAN xx:xx:xx:xx:xx:EB 2.4Ghz xx:xx:xx:xx:xx:EC 5Ghz xx:xx:xx:xx:xx:ED WAN xx:xx:xx:xx:xx:EE Flash instructions: D-Link normal OEM firmware update page 1. upload OpenWRT factory.bin like any D-Link upgrade image D-Link Recovery GUI: 1. Push and hold reset button (on the bottom of the device) until power led starts flashing (about 10 secs or so) while plugging in the power cable. 2. Give it ~30 seconds, to boot the recovery mode GUI 3. Connect your client computer to LAN1 of the device 4. Set your client IP address manually to 192.168.0.2 / 255.255.255.0 5. Call the recovery page for the device at http://192.168.0.1/ 6. Use the provided emergency web GUI to upload the recovery.bin to the device Firefox on Windows in a Private Window (incognito) works me Internet Explorer mode in Microsoft Edge works for others seems to not work in Linux or virtual machine on Linux for most some see success using 'curl -v -i -F "[email protected]" 192.168.0.1' Thanks to @frkca and @rodneyrod for testing and pushing for its creation Signed-off-by: Alan Luck <[email protected]>
Hardware: - SoC: MediaTek MT7981B - CPU: 2x 1.3 GHz Cortex-A53 - Flash: 128 MiB SPI NAND - RAM: 512 MiB - WLAN: 2.4 GHz, 5 GHz (MediaTek MT7976CN, 802.11ax) - Ethernet: 1x 10/100/1000/2500 Mbps RTL8221B WAN, 1x10/100/1000 Mbps MT7981 LAN - USB 3.0 port - Buttons: 1 Reset button, 1 slider button - LEDs: 1x Red, 1x White - Serial console: internal test points, 115200 8n1 - Power: 5 VDC, 3 A MAC addresses: +---------+-------------------+-----------+ | | MAC | Algorithm | +---------+-------------------+-----------+ | WAN | 80:af:ca:xx:xx:x1 | label+1 | | LAN | 80:af:ca:xx:xx:x0 | label | | WLAN 2g | 80:af:ca:xx:xx:x0 | label | | WLAN 5g | 82:af:ca:xx:xx:x0 | | +---------+-------------------+-----------+ Installation: The installation must be done via TFTP by disassembling the router. On other occasions Cudy has distributed intermediate firmware to make installation easier, and so I recommend checking the Wiki for this device if there is a more convenient solution than the one below. To install using TFTP: 1. Connect to UART. 2. With the router off, press the RESET button. While the router is turning on, the button should continue to be pressed for at least 5 seconds. 3. A u-boot shell will automatically open. 4. Connect to LAN and set your IP to 192.168.1.88/24. Configure a TFTP server and an OpenWrt initramfs-kernel.bin firmware file. 5. Run these steps in u-boot using the name of your file. setenv bootfile initramfs-kernel.bin tftpboot bootm 6. If you can reach LuCI or SSH now, just use the sysupgrade image with the 'Keep settings' option turned off. Signed-off-by: Luis Mita <[email protected]>
Initialize fwnode instead of the deprecated of_node. Signed-off-by: Shiji Yang <[email protected]>
The upcoming 6.6 kernel will introduce a new upstream generic "gpio-latch" driver. It will conflict with the downstream MikroTik GPIO latch driver. Let's rename it to avoid any potential issues. Signed-off-by: Shiji Yang <[email protected]>
This is preparation for 6.6 kernel support. Renaming files allows us to better track their git history. Signed-off-by: Shiji Yang <[email protected]>
Copy patches and kernel configs from kernel 6.6 to restore the default 6.1 kernel support files. Signed-off-by: Shiji Yang <[email protected]>
Implementing the updating of firmware initiated dynamic MU-EDCA parameters in Beacon IE. Firmware routinely checks its clients and updates its MU-EDCA values every 3 seconds. Firmware is tuning MU-EDCA parameters to improve performance. As part of this process, the firmware informs host about new MU-EDCA values utilizing WMI_MUEDCA_PARAMS_CONFIG_EVENTID. FW expectation is that host will update MU-EDCA parameters in the Beacon IE.
not needed for NSS offload and helps save some memory
Leave it set to '0', as it will kernel panic with 2K skb patch. This flag was incorrectly assumed to save memory on 1G platforms. ath11k_nss: remove leftover max_tx_ring it was not removed when applying patch to replace it with 'max_tx_ring = DP_TCL_NUM_RING_MAX +1' ath11k_nss: Import bugfix patches ath11k_nss: Experimental build for IPQ6018 This will require setting the correct `ATH11K_MEM_PROFILE_XXX` for your platform. Setting it to value lower/higher than physically available will cause NULL virtual address kernel panics. I believe this setting was not originally meant to reduce memory footprint of 1G+ platforms, but to account for platforms that were 512M or less. Will require tweaking to allow for the old behvaior on 1G+ IPQ807x, while still saving memory for platforms <= 512M.
QSDK NSS builds utilize skbuff recycling for better handling of memory.
On a Dynalink DL-WRX36 (pbuf script should be set to 'auto') a significant drop in
memory usage was observed as well consistent sustained RX/TX speeds.
BEFORE:
echo 3 >! /proc/sys/vm/drop_caches
free -m
total used free shared buff/cache available
Mem: 867 338 547 90 101 528
Swap: 0 0 0
AFTER:
total used free shared buff/cache available
Mem: 867 242 594 1 81 624
Swap: 0 0 0
NOTE:
For 512MB platforms, users need to test with the following scenarios,
as the patch `999-233-ath11k-Disable-rx_header-tlv-for-2K-SKB.patch` is
really only testable on platforms with 512M or less RAM.
1.) Explicitly setting 'ATH11K_MEM_PROFILE_512M' on and see if system
crashes on boot.
2.) Explicitly setting 'ATH11K_MEM_PROFILE_1G'
3.) Remove patches
999-233-ath11k-Disable-rx_header-tlv-for-2K-SKB.patch
999-311-ath11k-configure-nss-thread-priority-during-pdev_ini.patch
And re-test with #1 and #2
It was incorrectly assumed that setting a 512M for 1G platforms would save
memory, instead it needs to be explicitly set to know proper memory
regions, otherwise it would cause fw crash.
ath11k_nss: fix typo in 512M memory profile
ath11k_nss: remove SFE patch 718-e-mac80211-Deliver-the-frame-to-driver-tx-ops-directly
It is not relevant to NSS builds and only meant for SFE.
ath11k_nss: remove unecessary patches
Color collision should be left on by default, as it's a primary feature
of 802.11AX.
ath11k_nss: fix spacing
ath11k_nss: Remove unnecessary TKIP bloat
Remove TKIP patches that are not being used as 99% of folks are running
modern encryption (AES-CCMP,SAE,etc).
ath11k_nss: parameterize DP_RXDMA_REFILL_RING_SIZE memory profile
ath11k_nss: Remove SFE related code
Cleanup SFE (shortcut fe) related code as we're not using it on NSS
ath11k_nss: idr, ampdu, and skb headroom check optimizations
ath11k_nss: get valid last_rate for rx_bitrate from cpu stats
ath11k_nss: Fix BCCA counter for EMA
Currently BCCA counter is updated to FW via csa counter offs and
beacon with new countdown is updated for every beacon tx completion event.
For EMA, all EMA beacons are updated in one shot, and counter update for
every tx event will mess up the actual sequence of countdown sent over the air.
Allow FW to update the countdown till 1 and finalize the color
change.
ath11k_nss: Fix compile for TRACE feature
The performance of Qualcomm Crypto Engine is 10x slower than kernel based encryption via ARMv8 crypto extensions. Rather than building it into the kernel allow users to select it as module which can be tested with other HW based crypto APIs via cryptodev-linux.
Since SKB recycler was merged into main nss-wifi branch, it is not necessary to manually tinker with pbuf script. Memory is now properly managed between NSS driver allocating/deallocating SKBs. For optimal wifi performance, especially upload, it is advised to leave the script to 'auto'. Users who use sysupgrade should manually set the uci config '/etc/config/pbuf' as it will not overwrite existing configuration.
This will now be the default NSS branch, and will cover both kernel 6.1 and 6.6 related changes going forward. qualcommax: NSS: fix up 'nss_region'
Symbols for crypto, ktls, netfilter are removed from from being compiled into the kernel and instead left up to the user to compile as modules, as is the case upstream. Other unused qca features were also removed as they don't apply to ipq807x/6018 and are not upstream. Common symbols between 6.1/6.6 that are required for NSS related features have been consolidated into 'config-default'. There is an average 300kb of savings in the final kernel image as well decreased compile time. qualcommax: NSS: consolidate patches and align with 6.1 Update nss-cfi to kernel 6.6
Disable software input output translation lookaside buffer (swiotlb) as it wastes memory on low memory platforms (512m or less) qualcommax: only disable swiotlb for platforms <= 512M Disabling swiotlb is only required for platforms with 512M or less to save 64mb.
Signed-off-by: Sean Khan <[email protected]>
In ath11k_dp_rx_msdu_coalesce(), rxcb is fetched from skb and bool is_continuation is part of rxcb. Currently, after freeing the skb, the rxcb->is_continuation accessed again which is wrong since the memory is already freed. Hence fix the issue by locally defining bool is_continuation from rxcb, so that after freeing skb also we can use is_continuation. Signed-off-by: Sean Khan <[email protected]>
NSS offload feature should be available for all IPQ807x/IPQ817x targets. * Arcadyan AW1000 * CMCC RM2-6 * Linksys MX4200 V1/V2 * Linksys MX5300 * Sagemcom Fast 5285 Spectrum SAXV1V1S * Yuncore AX880 * ZBT Z800AX * ZTE MF269 Signed-off-by: Sean Khan <[email protected]>
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.