[pull] master from openwrt:master #990
Open
Conversation
This file contains hidden or 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
Hardware (common): - RK3568 SoC - 2/4GB LPDDR4 - 1x HDMI Type A - 3.5mm jack with mic - 1x PCIE 2.0 WiFi slot - 1x USB 3.0, 2x USB 2.0 - 2x 2.5GbE RTL8125B Ethernet - MicroSD card slot / eMMC 32GB Additions to HINLINK H68K: - 2x 1GbE RTL8211F/YT8531 Ethernet Installation: Use dd or balenaEtcher to flash the firmware. Signed-off-by: Chukun Pan <amadeus@jmu.edu.cn> Link: #21270 Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
38804f59fbb9 ci: add ath12k BDF-s d28bc0724dc6 ipq8074: add TCL LINKHUB HH500V BDF 8e1fb2f59893 ipq6018:add TP-Link EAP620 HD v3 BDF Add board file for TP-Link EAP620 HD v3. bdwlan_US.bin sourced from EAP620 HD(US)_V3_1.4.4 Build 20250718 stock firmware. Signed-off-by: Robert Marko <robimarko@gmail.com>
Reading the PHY ID to assign a PHY config is currently simple. For C45 two MDIO reads of a hardcoded MMD are done to get the standard PHY ID registers. MMD 31 (MMD_VEND2) is used for that purpose, assuming there will be a valid PHY ID stored in this MMD in all cases. However, with Aquantia AQR813 there's at least one example for which this isn't true. This PHY returns 0 for the PHY ID in MMD_VEND2, instead MMD_VEND1 would have the correct ID. Enhance reading the PHY by accessing a common set of MMDs of which most PHY at least implement one and have a valid PHY ID in. To keep overhead low, do not scan all MMDs. As soon as a valid PHY ID is found, exit and use that. This is similar to the kernel logic, jsut reduced to fewer MMDs. Also handle possible errors coming from MDIO reads to avoid reading garbage. While at it, move reading the PHY ID to a separate function to not pollute the poll fixup retrievel function. Signed-off-by: Jonas Jelonek <jelonek.jonas@gmail.com> Link: #21515 Signed-off-by: Robert Marko <robert.marko@sartura.hr>
Apply the PHY polling configuration for RTL931x too, as previously implemented for RTL930x. This is needed for several PHYs on that platform to function properly. Add another flag called 'force_res' to the phy_info struct which is for RTL931x only. The SDK mentions this as a flag to force polling the Realtek proprietary PHY status resolution register. Effectively, this changes the polling to proprietary format instead of standard format, and sets an enable bit in another private polling register field. Signed-off-by: Jonas Jelonek <jelonek.jonas@gmail.com> Link: #21515 Signed-off-by: Robert Marko <robert.marko@sartura.hr>
Add a PHY ID for Aquantia AQR813 which is an Octa-PHY found in some Realtek switches. Add another PHY ID for another revision of AQR113C, also found in some Realtek switches. Signed-off-by: Jonas Jelonek <jelonek.jonas@gmail.com> Link: #21515 Signed-off-by: Robert Marko <robert.marko@sartura.hr>
This patch was manually edited but not refreshed. Fixes: 794b4de ("uboot-mediatek: add 8g check to bpi-r4 environment for bl2") Fixes: 46ee520 ("uboot-mediatek: add command for getting size of ram") Signed-off-by: Shiji Yang <yangshiji66@outlook.com> Link: #21693 Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
Compilation currently spits this message: WARNING: modpost: vmlinux: section mismatch in reference: rtl83xx_sw_probe+0x6a4 (section: .text.rtl83xx_sw_probe) -> rtl83xx_setup_qos (section: .init.text) That means that we have a "normal" function caller (can be called during the whole uptime) and a "initialization" function callee (only available during init. Fix this and directly fix the unwanted family checks. Fixes: a91c3ab ("realtek: dsa: avoid use-after-free") Signed-off-by: Markus Stockhausen <markus.stockhausen@gmx.de> Link: #21690 Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
Update the econet-eth driver to a new version which is of sufficient quality that it is realistic to think about upstreaming. This version is now NAPI based, collects stats, downloads without dropped packets anymore, has debugfs introspection, and can be unloaded and reloaded (providing the reset controller is present). PR #21545 is recommended but not required, without this the ethernet driver will log a warning on startup because it can't get the resets and it will be impossible to unload and reload the driver without a reboot. However, the PoC driver was not capable of reloading so this is not a regression. Signed-off-by: Caleb James DeLisle <cjd@cjdns.fr> Link: #21557 Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
Specifications:
* SoC: Qualcomm IPQ6018/AP-CP03-C1 (64-bit Quad-core Arm Cortex-A53 @ 1.2 GHz)
* RAM: 2x Zentel A3T4GF40BBF-HP (1 GiB DDR3-1866 (13-13-13))
* Serial Port: 1v8 TTL 115200n8
* Wi-Fi: Qualcomm QCN5022 (802.11ax/b/g/n)
* Wi-Fi: Qualcomm QCN5052 (802.11ac/ax/n)
* Ethernet: RTL8211FS (10/100/1000BASE-T)
* Flash: GigaDevice PSR1GA30DT (128 MiB)
* LEDs: 1x Blue Status (GPIO 35 Active High)
* Buttons: 1x Reset (GPIO 9 Active Low)
* FCCID: 2AXJ4EAP620HDV3
* UART: 4-pin unpopulated header by the J1 footprint
Installation Instructions (Serial+TFTP):
1. Locate the J1 footprint which contains 4 unpopulated pins
where starting from the arrow, the pins are TX, RX, VCC and GND
respectively.
2. Connect a 1v8 TTL port to the 4 pins. Ensure RX and TX are crossed
over.
3. Copy openwrt-qualcommax-ipq60xx-tplink_eap620-hd-v3-initramfs-uImage.itb
to your TFTP server.
4. Power up the AP and hold Ctrl+B in the serial console (115200n8) until autoboot is halted.
5. Run the following commands in the U-boot prompt:
IPQ6018# setenv serverip <TFTP server addr>
IPQ6018# setenv ipaddr <addr of the AP>
IPQ6018# tftpboot 0x44000000 openwrt-qualcommax-ipq60xx-tplink_eap620-hd-v3-initramfs-uImage.itb
IPQ6018# bootm 0x44000000
You may need to type Ctrl+C and Enter before running these commands
to clear invisible characters from the buffer.
6. Run the following command in a terminal to copy the sysupgrade image
to be installed (check IP address):
$ scp -O openwrt-qualcommax-ipq60xx-tplink_eap620-hd-v3-squashfs-sysupgrade.bin root@192.168.1.1:/tmp/
7. Activate the OpenWrt serial console and run the following commands:
# cd /tmp
# sysupgrade -n openwrt-qualcommax-ipq60xx-tplink_eap620-hd-v3-squashfs-sysupgrade.bin
8. The AP will reboot and OpenWrt will be successfully installed.
Installation Instructions (Web UI method):
1. Set up the device using the vendor's web UI. Navigate to
Management->SSH and enable the "SSH Login" checkbox. Select "Save".
2. Connect to the machine via SSH:
$ ssh -o hostkeyalgorithms=ssh-rsa <ip_of_device>
3. Disable signature verification:
$ cliclientd stopcs
4. Rename the "-web-ui-factory" image to something less than 63
characters, maintaining the ".bin" suffix.
5. Go to System -> Firmware Update.
Under "New Firmware File", click "Browse" and select the image.
Select "Update" and confirm by clicking "OK".
6. If the update fails, the web UI should show an error message.
Otherwise, the device should reboot into OpenWrt.
Device support followed from EAP620HD v2 and eap6xx-outdoor for DTS.
Links: #18227
Signed-off-by: John Christoforidis <github@yanny.dev>
Link: #21467
Signed-off-by: Robert Marko <robimarko@gmail.com>
The Raidsonic devices do not use a 2048k kernel "Kern" partition like the Storlink reference designs. Instead it uses a 3072k partition to fit a slightly larger kernel. Sadly the current OpenWrt Gemini kernel is still bigger than 3072k so we need to make use of the Ramdisk partition as well. Create a special "copy-kernel" version that can deal with the Raidsonic 3072k kernels. Tested on the Raidsonic IB-4220-B booting kernel v6.12.66. Fix a copy/paste error in the image generation makefile while we are at it. Link: #21686 Signed-off-by: Linus Walleij <linusw@kernel.org>
5a13d875ac71 dhcpv6: set static defines for DHCPv6 option header size 9857adb8ac99 dhcpv6-ia: switch case refactor in dhcpv6_handle_ias() 3cbbea830ddd netlink: clean up sockets, close files 13ef483716a5 dhcpv4: de-escalate error logging to debug openwrt/odhcpd@3fda5f8...13ef483 Signed-off-by: Paweł Owoc <frut3k7@gmail.com> Link: #21636 Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
Switchdev driver used by microchipsw supports DCB and has not storage constraints, so enable kernel and driver DCB support by default. Signed-off-by: Robert Marko <robert.marko@sartura.hr>
Now that DCB is enabled by default, it makes sense to include it on lan969x. While we are here, lets include ip-bridge as these devices are switches and the Busybox applet does not expose enough functionality. These devices have no space constraints. Signed-off-by: Robert Marko <robert.marko@sartura.hr>
This commit enables PoE output on port 1 of the Meraki MR30H if the device is powered via 802.3at PoE. No PoE output is enabled if the device is powered via 802.3af PoE, as there is insufficient power. Signed-off-by: Hal Martin <hal.martin@gmail.com> Link: #20645 Signed-off-by: Robert Marko <robimarko@gmail.com>
Add two missing $$ in the factory image build pipeline for MR6350 Signed-off-by: Zeyu Dong <dzy201415@gmail.com> Link: #21682 Signed-off-by: Robert Marko <robimarko@gmail.com>
No one has looked into the firmware based RTL8218B initializations
for a long time. Instead the basic setup sequences have evolved
so that they can start the RTL8218B PHY from scratch. See
19bc6e8 ("realtek: phy: add basic RTL8218B setup")
4fa90d8 ("realtek: phy: enhance RTL8218B initialization")
Drop the legacy coding.
Signed-off-by: Markus Stockhausen <markus.stockhausen@gmx.de>
Link: #21679
Signed-off-by: Robert Marko <robimarko@gmail.com>
There are some code pieces that determine the SoC version of the running system. For RTL83xx it reads out the registers, for RTL93xx it simply uses a constant value. Without any consumer of this data drop it. Signed-off-by: Markus Stockhausen <markus.stockhausen@gmx.de> Link: #21684 Signed-off-by: Robert Marko <robimarko@gmail.com>
Align the functions with rest of driver. Signed-off-by: Markus Stockhausen <markus.stockhausen@gmx.de> Link: #21685 Signed-off-by: Robert Marko <robimarko@gmail.com>
Align the functions with rest of driver. Signed-off-by: Markus Stockhausen <markus.stockhausen@gmx.de> Link: #21685 Signed-off-by: Robert Marko <robimarko@gmail.com>
The GPIO expander is connected via I2C, thus the can_sleep flag has to be set to true. This fixes spurious "scheduling while atomic" bugs in the kernel ringbuffer. Signed-off-by: Milan Krstic <milan.krstic@gmail.com> Link: #19182 Signed-off-by: Robert Marko <robimarko@gmail.com>
The BOOTCONFIG partition is used by Qualcomm's boot chain to store metadata about the device's startup configuration. It contains info such as versioning, configuration flags, primary boot partition, and more. Newer devices with dual boot partitions not only store the active boot partition in a U-boot variable but also in partition info in the BOOTCONFIG partition. As such, add library functions to set and toggle the active boot partition. Signed-off-by: Milan Krstic <milan.krstic@gmail.com> Link: #19182 Signed-off-by: Robert Marko <robimarko@gmail.com>
TCL LINKHUB HH500V also known as Vodafone Gigacube B157 is a dual band 802.11ax 5G NR CPE with an FXS port. Specifications: * SoC: Qualcomm IPQ8072A * RAM: 1024 MB * NAND flash: 256MB NAND (MT29F2G08ABBGAH4) * NOR flash: 64MB NOR (MX25U25635F) - only in some variants * WiFi 5G: Qualcomm QCN5054 * WiFi 2.4G: Qualcomm QCN5024 * Ethernet 2.5G: Qualcomm QCA8081 * Ethernet 1G: Qualcomm QCA8075 * Modem: GosunCn GM800 (Qualcomm Snapdragon X55) * SIM: 1 nano-SIM card slot * Buttons: Power, Reset, WPS * LEDs: Power (B/R), WiFi (B), 4G (B/Y/R), 5G (B/Y/R) * VoIP: 1 FXS RJ11 port (not supported in OpenWrt) * Power: 12V, 3A UART serial console: * 115200,8N1,1.8V * Three unmarked test points next to QJ2012A: +---------+ | QJ2012A | +---------+ o TX o GND o RX o o o Installation via OEM firmware: * Use the following process to obtain root ssh access https://forum.openwrt.org/t/150371/24 * Connect using root with no password on port 42000 * Optionally for serial bootloader access run : fw_setenv bootdelay=3 * SCP factory.bin to /tmp * Run: sysupgrade -n /tmp/factory.bin Installation via serial console and OEM firmware:: * Use console to access OEM firmware shell * Proceed with SCP & sysupgrade as described above Other notes: * This device uses active partition rotation * Some versions (TCL branded?) have a NOR chip in addition to NAND * The above is supported by u-boot patching DT partitions * DT patching does NOT occur on tftpboot/bootm * Modem is detected as foxconn-sdx55 by kernel (same VID/PID) * This works OK-ish and should be improved if we can get OEM modem details Signed-off-by: Milan Krstic <milan.krstic@gmail.com> Link: #19182 Signed-off-by: Robert Marko <robimarko@gmail.com>
Setup for DSA QOS on RTL839x accesses unitialized memory. For some
reason the handover of the priv structure was realized via global
intermediate variable switch_priv. During refactoring for adbb9a6
("realtek: dsa: rtl83xx: fix init section mismatch") this was not
noticed. Since then RTL839x devices crash during startup.
Fix this by using standard handover via function parameters.
Fixes: adbb9a6 ("realtek: dsa: rtl83xx: fix init section mismatch")
Signed-off-by: Markus Stockhausen <markus.stockhausen@gmx.de>
Link: #21703
Signed-off-by: Robert Marko <robimarko@gmail.com>
Add netifd_loglevel to /etc/config/network: config globals 'globals' option netifd_loglevel '1' The netifd's default value is 2. Signed-off-by: Peter Meiser <peter.meiser@gmx.com> Link: #19737 Signed-off-by: Robert Marko <robimarko@gmail.com>
Use the correct syntax for array element assignment Signed-off-by: Felix Fietkau <nbd@nbd.name>
Mikrotik RBM33G has got a USB-A port and mPCIe slots with USB 3.0 and USB 2.0 interfaces in use. The MediaTek MT7621 SoC has got an xHCI to provide these interfaces. Therefore, enable kmod-usb3 to support them. Fixes: 5684d08 ("ramips: Add support for Mikrotik RouterBOARD RBM33g") Signed-off-by: Chester A. Unal <chester.a.unal@arinc9.com>
Currently, for targets that use the CONFIG_TARGET_ROOTFS_TARGZ a single rootfs tarball is generated for the subtarget based of $(TARGET_DIR). However, this means that it does not respect DEVICE_PACKAGES like other rootfs images. So, lets augment CONFIG_TARGET_ROOTFS_TARGZ by adding a proper targz fstype so that per device rootfs is generated under lock. This is required so that devices that use custom sysupgrade archives like Methode devices, can actually include a per device rootfs so when building for multiple devices and with CONFIG_TARGET_PER_DEVICE_ROOTFS set the built image actually includes the listed DEVICE_PACKAGES. Signed-off-by: Robert Marko <robert.marko@sartura.hr>
Use the added support for generating per device targz rootfs so that images generated for Methode devices when CONFIG_TARGET_MULTI_PROFILE and CONFIG_TARGET_PER_DEVICE_ROOTFS are set, we actually get the targz rootfs that respects DEVICE_PACKAGES. Currently, buildbot generated images have no networking, LM75 nor I2C working, as the generated images do not include required kmods that are listed in DEVICE_PACKAGES. While at it, there is no need for tar to run in verbose mode. Fixes: 7dff6a8 ("mvebu: uDPU: add sysupgrade support") Signed-off-by: Robert Marko <robert.marko@sartura.hr>
7e5b324 instance: check length of names when creating cgroups 014f94c procd: jail/cgroups: fix OOB write in cgroups_apply() e08cdc8 hotplug-dispatch: fix filter disallowing setting PATH afa4391 service instance: Improve handling of watchdog config changes 52c64d2 service instance: Fix overwriting of watchdog linked list members 96c827f coldplug: fix missing header include 6b10c71 hotplug-dispatch: fix missing header include 58d7aaa initd/coldplug: create /dev/null before running udevtrigger 64f97ff hotplug-dispatch: redirect output to /dev/null c4e9859 hotplug-dispatch: use stat if d_type is DT_UNKNOWN bafdfff system: fix arguments validation in ubus handler Signed-off-by: Daniel Golle <daniel@makrotopia.org>
Upstream solution came with 6.4. Seems quilt refreshed it to the extent that it basically gets applied twice. Signed-off-by: Rosen Penev <rosenp@gmail.com> Link: #21954 Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
patch netlink headers for netifd PSE support & fix PSE backports for PSE Prio The 626-* patches are backporting net PSE-PD from linux 6.18 to 6.12. The 627-02 is a nearly verbatim copy of the upstream commit. The 6.12-01 patches the auto generated ethtool_netlink_generated header. The 6.12 build tools do not have the build system feature for generating the correct netlink headers related to the backports. Signed-off-by: Carlo Szelinsky <github@szelinsky.de> Link: #21926 Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
There is a missing tab in one of the cases of MAC address configuration. Signed-off-by: Jan Hoffmann <jan@3e8.eu> Link: #21644 Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
The MAC address assignment for XikeStor SKS8300-8T and SKS8300-12E2T2X is semantically identical to the first case, so let's combine them. Signed-off-by: Jan Hoffmann <jan@3e8.eu> Link: #21644 Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
Currently, the 02_network script always configures MAC addresses for each individual LAN port unless "lan_mac_start" is set to "skip". This behaviour can be unexpected, and is also somewhat broken, as it even continues to do so when "lan_mac_start" is empty. Change it to only do the configuration if "lan_mac_start" is non-empty, and also remove the fallback to "lan_mac", making this more obvious and less error-prone. Signed-off-by: Jan Hoffmann <jan@3e8.eu> Link: #21644 Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
Explicitly specify all devices where the MAC address is configured based on the U-Boot environment. This change makes it clearer which devices use this method. Also makes things simpler for any future devices which handle MAC address configuration entirely via device tree. Signed-off-by: Jan Hoffmann <jan@3e8.eu> Link: #21644 Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
Only configure the eth0 MAC address when it is not already done in the device tree. To do this, create a new variable "eth0_mac". Also avoid setting "label_mac" for devices already having it defined in the device tree. Signed-off-by: Jan Hoffmann <jan@3e8.eu> Link: #21644 Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
This reverts commit 66a7e04. Doing so makes the u-boot unable to find the node for this pcie controller and disable it on mx60, resulting boot failure, as reported in #21649 . If we keep on treating mx60 and mx60w the same target, we might have to endure the warning which 66a7e04 wants to eliminate. Signed-off-by: Edward Chow <equu@openmail.cc> Link: #21941 Signed-off-by: Robert Marko <robert.marko@sartura.hr>
On the kirkwood target, packages would frequently fail to install with APKE_ADB_SCHEMA, APKE_ADB_BLOCK, and/or segfaults. The culprit was unaligned access leading to bogus values being read out of memory on these particular ARMv5 CPUs. Pull in the relevant upstream fixes to address this. Fixes: #21307 Link: https://gitlab.alpinelinux.org/alpine/apk-tools/-/merge_requests/391 Link: https://gitlab.alpinelinux.org/alpine/apk-tools/-/merge_requests/392 Signed-off-by: Matt Merhar <mattmerhar@protonmail.com> Link: #21958 Signed-off-by: Robert Marko <robert.marko@sartura.hr>
These devices share the same "compatible" in device tree causing some incompatibilities (sysupgrades, ASU profile identification), assign a unique "compatible" and "model" to each variant. Context: Commit [1] added each variant's dts compatible to the SUPPORTED_DEVICES field of the other variant to make easy sysupgrades between these physically indistinguishable devices variants possible. But there were found three issues which does not allow this: - the sysupgrade's stricter check still used in some sysupgrade paths(this check is being replaced(and redundant) with the newer fwtool's SUPPORTED_DEVICES check using the info in images METADATA), this check will fail when sysupgrading from a different board_name(compatible dts) that the image was created for (image profile name).[2] - ASU needs unique "dts compatible" to identify the devices profile. - and an ASU's profile identification limitation when several devices from a common target share SUPPORTED_DEVICES entries.[3] There is a proposal for these issues but not yet implemented [4][3]. Until these issues are fixed we won't allow "easy" sysupgrades between these two device variants. Commit [5] avoided the ASU profile identification limitation but missed the required two unique dts compatibles in order to make the two variants fully work, although not allowing easy sysupgrade between them. [1]: 8d30e07 [2]: sysupgrade stricter check #20566 (comment) [3]: ASU proposal openwrt/asu#1533 [4]: allow easy sysupgrade proposal #20947 [5]: b71f466 Fixes: b71f466 ("mediatek: filogic: fix supported_devices list for gl-mt2500") Fixes: 8d30e07 ("mediatek: filogic: fix for new GL.iNet GL-MT2500/GL-MT2500A hardware revision") Fixes: #20566 Fixes: openwrt/asu#1525 Signed-off-by: Mario Andrés Pérez <mapb_@outlook.com> Link: #21842 Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
Backport PPP patches accepted upstream. Manually rebased: - target/linux/ipq40xx/patches-6.12/999-atm-mpoa-intel-dsl-phy-support.patch Signed-off-by: Qingfang Deng <dqfext@gmail.com> Link: #21892 Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
Convert the malta target from the legacy Image/BuildKernel and Image/Build pattern to the modern Device macro system. This is the last target still using the legacy pattern. The Device macro system automatically generates per-image JSON metadata files which get aggregated into profiles.json, enabling firmware selector and other tooling support for all malta subtargets (be, le, be64, le64). The kernel ELF is produced via KERNEL_NAME := vmlinux.elf (matching octeon), uImage artifacts are built using the standard Build/lzma, Build/gzip and Build/uImage commands with the existing load address 0x80100000, and rootfs images use append-rootfs with optional gzip compression. The device is named 'generic' following the convention used by other virtual/emulated targets (x86, armsr, octeon). Signed-off-by: Paul Spooren <mail@aparcar.org>
Update the default kernel path in start_qemu_malta() to match the new image naming scheme after the malta target was converted to the Device macro system with device name 'generic'. Signed-off-by: Paul Spooren <mail@aparcar.org>
Bootlog has the following line: mt798x-wmac 18000000.wifi: missing precal data, size=403472 It is because precal was not included in the previous NVMEM conversion. Fix this by adding it to the common dtsi. Fixes: dbc2923 ("mediatek: filogic: convert Acer Predator W6 to use NVMEM framework") Signed-off-by: Zhi-Jun You <hujy652@protonmail.com> Link: #21894 Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
Bootlog has the following line: mt7915e 0000:01:00.0: missing precal data, size=403472 It is because precal was not included in the previous NVMEM conversion. Fix this by adding it to the common dts. Fixes: dbc2923 ("mediatek: filogic: convert Acer Predator W6 to use NVMEM framework") Signed-off-by: Zhi-Jun You <hujy652@protonmail.com> Link: #21894 Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
Bootlog has the following line: mt7915e 0000:01:00.0: missing precal data, size=403472 It is because precal was not included in the previous NVMEM conversion. Fix this by adding it to the dts. Fixes: dbc2923 ("mediatek: filogic: convert Acer Predator W6 to use NVMEM framework") Signed-off-by: Zhi-Jun You <hujy652@protonmail.com> Link: #21894 Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
Add the required patches in order to backport cake-mq from Linux 7.0. Many thanks to Toke Høiland-Jørgensen for providing the git trees with backports for both 6.12 and 6.18. Signed-off-by: Rui Salvaterra <rsalvaterra@gmail.com> Link: #21964 Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
Add two patches backported from iproute2-next. Signed-off-by: Rui Salvaterra <rsalvaterra@gmail.com> Link: #21964 Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
Add a patch that avoids including <stddef.h> in BPF headers, fixing
build failures on OpenWrt toolchains where the header is unavailable:
In file included from xdpfilt_dny_udp.c:10:
In file included from ./xdpfilt_prog.h:24:
../lib/../headers/xdp/parsing_helpers.h:18:10: fatal error: 'stddef.h' file not found
18 | #include <stddef.h>
| ^~~~~~~~~~
1 error generated.
make[5]: *** [../lib/common.mk:111: xdpfilt_dny_udp.o] Error 1
make[4]: *** [Makefile:40: xdp-filter] Error 2
Link: #21972
Signed-off-by: Nick Hainke <vincent@systemli.org>
Add support for the TP-Link EAP683-LR, an AX6000 Ceiling Mount WiFi 6 AP. Hardware: * SoC: MediaTek MT7896AV * RAM: 1GiB DDR4 (Samsung K4A8G165WC-BCTD) * Flash: 128MiB SPI-NAND (ESMT F50L1G41LB) * Ethernet: 1x 10/100/1000/2500 Mbps PoE-PD (MaxLinear GPY211C) * WiFi: MT7976AN/MT7976GN 2.4/5GHz 4T4R * LEDS: 3x blue connected to a single GPIO line * Buttons: 1x reset * BLE/Thread/Zigbee: CC2652 Stock firmware uses a random MAC address for ethernet, label MAC for 2.4 and label MAC + for 5GHz. Installation via bootloader: * Solder JST??? connector on J255, alternatively solder wires on the TP13-TP15 pads. Pinout: TP13: TX, TP14: RX, TP15: GND, TP16: VCC. The pins for J255 are in the same order. * Interrupt boot process by repeatedly pressing Ctrl+b during boot * In the boot menu, select U-Boot console * Ensure the U-Boot environment variable "tp_boot_idx" is not set: # setenv tp_boot_idx # saveenv * Boot the OpenWrt initramfs: # tftpboot openwrt-mediatek-filogic-tplink_eap683-lr-initramfs-kernel.bin # bootm * copy openwrt-mediatek-filogic-tplink_eap683-lr-squashfs-sysupgrade.bin to /tmp and install it using sysupgrade Flashing via OEM firmware is currently not supported. The tplink-safeloader utility does not recognize the OEM firmware: DEBUG: can not find fwuphdr Firmware image partitions: base size name Segmentation fault (core dumped) To revert to the OEM firmware, you can set the U-Boot environment variable "tp_boot_idx" to 1 via bootloader, or using fw_setenv via OpenWrt. This should result in booting from the ubi1 partition, which OpenWrt should not touch. Then use the web interface to upgrade firmware: System > Firmware Update. The OEM firmware uses 0x800000 for the runtime_backup partition size. This causes the following warning: mtd: partition "runtime_backup" extends beyond the end of device "nmbm_spim_nand" -- size truncated to 0x600000 This is due to the NMBM reserved blocks. Use 0x600000 in our DTS. Thanks to init Lab's user890104, who soldered jumper wires on the TTL pads for me so I could have serial console. My soldering skills just aren't good enough to pull that off without risk damaging things. Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
The TP-Link EAP683-UR is identical to the EAP683-LR. Add it as ALT0 variant. Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
ZTE MF833U1 is a LTE dongle that expose a cdc_ether interface for data link
and WebUI for management. It handles all the "modem" functionalities
internally and does not expose any serial interface. Instead it acts like a
"router in a stick".
It initially enumerates as a USB mass-storage device and does not bind any
network driver, so no netdev is created until a modeswitch is performed.
The test is done on Cudy TR3000 256MB v1.0 running OpenWrt 24.10.5 with an
unit targeting Chinese market:
- Hardware Version: MF883U1_V1.0.0
- Software Version: BD_MF883U1V1.0.0B06
- CMIT ID: 2019CP2106
There are report online that the device have different variants that have
different behavior across different firmware, HW revisions or SKUs.
Before the switch:
```
root@OpenWrt:~# lsusb -t
/: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci-mtk/1p, 480M
|__ Port 001: Dev 003, If 0, Class=[unknown], Driver=[none], 480M
root@OpenWrt:~# lsusb Bus 001 Device 001: ID 1d6b:0002 Linux 6.6.119
xhci-hcd xHCI Host Controller Bus 001 Device 004: ID 19d2:1705
DEMO,Incorporated DEMO Mobile Boardband Bus 002 Device 001: ID 1d6b:0003
Linux 6.6.119 xhci-hcd xHCI Host Controller ```
After the switch:
```
root@OpenWrt:~# lsusb -t
/: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci-mtk/1p, 480M
|__ Port 001: Dev 003, If 0, Class=[unknown], Driver=cdc_ether, 480M
|__ Port 001: Dev 003, If 1, Class=[unknown], Driver=cdc_ether, 480M
|__ Port 001: Dev 003, If 2, Class=[unknown], Driver=[none], 480M
/: Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci-mtk/1p, 20000M/x2
root@OpenWrt:~# lsusb Bus 001 Device 001: ID 1d6b:0002 Linux 6.6.119
xhci-hcd xHCI Host Controller Bus 001 Device 003: ID 19d2:1706
DEMO,Incorporated DEMO Mobile Boardband Bus 002 Device 001: ID 1d6b:0003
Linux 6.6.119 xhci-hcd xHCI Host Controller ```
The following kernel debug log is presented:
``` cdc_ether 1-1:1.0 eth2: register 'cdc_ether' at usb-11200000.usb-1, ZTE
CDC Ethernet Device, 34:4b:50:00:00:00 ```
Signed-off-by: Zihao Diao <hi@ericdiao.com>
Link: #21867
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
RTL83xx uses the BMCR and ADVERTISE registers like RTL93xx to configure in-band auto-negotiation. Split out the common parts as a new generic implementation and use it for RTL83xx. RTL93xx retains its own variant of set_autoneg to support XSGMII, but calls into the generic version for all other modes. Tested 1000Base-X auto-negotiation on HPE 1920-8G (RTL8380). Also tested HPE 1920-24G (RTL8382) and HPE-1920-48G (RTL8393) to make sure this does not affect PHY ports. Signed-off-by: Jan Hoffmann <jan@3e8.eu> Link: #21934 Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
There is now an implementation of .set_autoneg and .restart_autoneg for all variants. Remove the helper function which checks for it, and just call the operation directly. Signed-off-by: Jan Hoffmann <jan@3e8.eu> Link: #21934 Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
Refresh the patches to make them apply cleanly again. Fixes: 105eb9c ("kernel: add cake-mq support") Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
20 participants
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.
See Commits and Changes for more details.
Created by
pull[bot]
Can you help keep this open source service alive? 💖 Please sponsor : )