qualcommax: ipq50xx: use ascii-env driver to set mac address for Linksys MX devices
The ascii-env driver enables reading name pair values from nand in ascii layout. So, let's pick up and set the mac address accordingly.
Signed-off-by: George Moussalem <george.moussalem@outlook.com> Link: https://github.com/openwrt/openwrt/pull/18029 Signed-off-by: Robert Marko <robimarko@gmail.com> (commit: eacc4d8)
qualcommax: ipq50xx: Linksys MX remove superfluous properties and fix indentation
On the ipq50xx platform, the internal GE PHY at phy address 7 on mdio0 must be enabled as it's used to detect the virtual switch in qca-ssdk. This is a platform wide condition and is therefore part of the dtsi. However, by enabling the mdio0 bus in board-specific dts files, the ge_phy is implicitly enabled. So, let's remove the superfluous status property in the dts files for Linksys MX2000 and MX5500.
While at it, remove the redundant phy-mode property as it's set to sgmii by default in the ipq5018-ess.dtsi file and fix indentation in the firmware property of the q5v6_wcss node.
Signed-off-by: George Moussalem <george.moussalem@outlook.com> Link: https://github.com/openwrt/openwrt/pull/18029 Signed-off-by: Robert Marko <robimarko@gmail.com> (commit: b790989)
Signed-off-by: John Audia <therealgraysky@proton.me> Link: https://github.com/openwrt/openwrt/pull/18000 Signed-off-by: Robert Marko <robimarko@gmail.com> (commit: 57b0304)
Since alpinelinux/apk-tools@460d62ee743c, relative paths are no longer accepted in repositories file.
Add local repository in APK command instead to fix this issue.
Fixes: 83d2d21904e0 ("apk: update to Git HEAD (2025-02-08)") Fixes: https://github.com/openwrt/openwrt/issues/18032 Signed-off-by: Kuan-Yi Li <kyli@abysm.org> Link: https://github.com/openwrt/openwrt/pull/18048 Signed-off-by: Robert Marko <robimarko@gmail.com> (commit: 6936dea)
By switching to the new RTL8231 driver in commit b7af54d5c18c ("realtek: Simple conversions to RTL8231 MFD driver"), the bootloader state of the RTL8231's pins is now maintained. As the bootloader de-asserts the PoE enable signal, this means PoE output is no longer available.
Add a gpio-hog with high output, restoring the line value from when the pin was configured (by default) as an input with a pull-up resistor. This will hard-enable the PoE output, but the individual ports can still be administratively disabled by realtek-poe or a similar tool.
Since the update to kernel 6.1, a warning like this appears in the kernel log:
[ 49.773953] ------------[ cut here ]------------ [ 49.773998] WARNING: CPU: 3 PID: 2349 at target-arm_cortex-a7+neon-vfpv4_musl_eabi/linux-ipq40xx_generic/dsl_cpe_mei-ugw_8.5.2.10/src/drv_mei_cpe_msg_process.c:3570 MEI_IoctlCmdMsgWrite+0x290/0x2c8 [drv_mei_cpe] [ 49.777670] memcpy: detected field-spanning write (size 4) of single field "pDestPtr" at target-arm_cortex-a7+neon-vfpv4_musl_eabi/linux-ipq40xx_generic/dsl_cpe_mei-ugw_8.5.2.10/src/drv_mei_cpe_msg_process.c:3570 (size 2) ... [ 50.087078] ---[ end trace 0000000000000000 ]---
The variable "pDestPtr" points to the field "header.index" in a CMV_STD_MESSAGE_T struct (header is a CMV_STD_MESSAGE_HEADER_T struct). The offending code intentionally copies data beyond this field, which is followed by "header.length" and "payload".
To fix this, change the assignment of "pDestPtr" to use the pointer to the message plus the offset of the "header.index" field. This way, the compiler knows about the size and thus the false positive warning disappears.
While at it, also adjust all places where similar code is used to copy from a CMV_STD_MESSAGE_T struct.
Also mark all related structs as packed, because the code (and the driver in general) seems to rely on that anyway.
ltq-vdsl-vr9-mei: avoid unnecessary usage of unsafe_memcpy
Commit 7bc487c12eef ("kernel: ltq-vdsl-vr9-mei: fix warning about field-spanning write") patched the driver to use unsafe_memcpy in MEI_IoctlCmdMsgWrite.
However, this is not actually necessary. The assignment of the variable "pDestPtr" can be modified so that the compiler knows about the correct size. This way, the check in the fortified memcpy works correctly.
While at it, also adjust all places where similar code is used to copy from a CMV_STD_MESSAGE_T struct.
Also mark all related structs as packed, because the code (and the driver in general) seems to rely on that anyway.
ltq-vdsl-vr11: add option for L3 request without retry on failure
This allows to attempt an orderly shutdown via L3 request while avoiding excessive delay in the failure case (up to 6 seconds with the currently hard-coded 3 attempts).
ltq-vdsl-vr11-app: exit more quickly if orderly shutdown fails
On exit, the app tries to do an orderly shutdown of the DSL connection before it is stopped forcibly. Since the driver does 3 attempts with a timeout of 2 seconds each, this might take about 6 seconds in the worst case.
This is problematic on sysupgrade, because any process that doesn't exit within 4 seconds is killed. This means that the DSL connection might not be stopped at all before the actual system upgrade begins.
To avoid this, use the newly added option in the driver to not retry the L3 request on failure.
3dcc957 three issues: 434bad8 /new_root related 04d18a5 README armsr combined-efi 506d8c1 /efi is not a thing in armsr combined-efi c0db1ed efivarfs remove these filecons 4eb35b7 adds efivars noseclabelfs for armsr combined-efi bbc6a6b adds /dev/ttyS3 to tty serialtermdev 1467206 README local logins 6ae3185 rename eficapsulemiscnodedev d43ded0 rename to vportserialtermdev a47d2f8 fixes virtio port serialtermdev 03aec70 blockmount: make it a bit more robust 70f1ed3 hotplugcall not sure what config triggers this 3338764 boarddetect: i was expecting this d97548a deal with /dev/tty and /dev/vcs c6ba4a5 adds virtio block device d03e216 adds virtio vport serialtermdev for qemu guest agent 2dc0291 validatefirmwareimage: allow getattr of *all* dev chr files fdfb3a7 adds /dev/efi_capsule_loader for armsr combined target b129fb9 validatefirmwareimage ordering b5e81b4 validatefirmwareimage clean up 0932dc5 README typo fixes a1f88f0 README fix e6c68be README typo fixes a232c21 hvcloginserialtermdev: macro not used d7edd95 support /usr/local and update README c0d2947 validatefirmwareimage comment 7dbc9b3 validatefirmwareimage: allow find to getattr of dev.except char f647175 platformtmpfile: elaborate a bit in comment 52f32c1 reintroduce misc.cil 320d77f validatefirmwareimage: /lib/upgrade/platform.sh 365fc65 deal with /efi for combined images 183b412 adds hvc logserialtermdev 20cd42a sshdsysagent: limited support for legacy scp -O with firmware images 1ccee8d validatefirmwareimages: some events related to "combined" images 9b47fc3 jshn reads /dev/urandom f86def7 adds /tmp/log/apk.log f1247b3 these are relative to the current namespace 32c0cc8 hotplugcall qemu virtio-console-helper 5cc41f5 uclient-fetch for manually downloading sysupgrade related c8140bd cgi-io creates firmware and backup atomically edf517b factoryreset deal with firstboot compatibility f5116b5 pppd: redundant, is implied with shell client type 86be72c updates README 8c08ca1 luci-mod-system: a bit of speculation here 417f4a5 adds /dev/autofs 1ed537c misc.cil: remove 01d014a selinuxsecfile: be more specific 53fca71 rename blockd module b4c9b15 ttyloginserialtermdev: ordering 016c3c1 sysagent traversal of /root is enough d0d7c91 hotplugcall: net/00-sysctl 2821746 adds ttyAMA0 and some incomplete rules for board-detect
Allows us to drop multiple upstreamed patches: package/network/utils/iproute2/patches/013-endian.h.patch package/network/utils/iproute2/patches/014-basename.patch package/network/utils/iproute2/patches/015-limits.h.patch package/network/utils/iproute2/patches/016-limits.h.patch package/network/utils/iproute2/patches/017-linux-limits.patch package/network/utils/iproute2/patches/018-linux-limits.patch
Link: https://github.com/openwrt/openwrt/pull/18067 Signed-off-by: Robert Marko <robimarko@gmail.com> (commit: cb5fb84)
Signed-off-by: Shiji Yang <yangshiji66@qq.com> Link: https://github.com/openwrt/openwrt/pull/18064 Signed-off-by: Robert Marko <robimarko@gmail.com> (commit: ce67f08)
The serious liblzma backdoor vulnerability (CVE-2024-3094) has been fixed since v5.6.2. It's time to bump this tool to the latest version. This patch also added a new GitHub package URL.
realtek: ONTi ONT-S508CL-8S is a relabeled XikeStor SKS8300-8X
Both hardware and firmware of these devices appears identical except for the manufacturers logo and device name. The documented XikeStor SKS8300-8X installation method is verified to work on the ONTi ONT-S508CL-8S using Openwrt images made for the XikeStor SKS8300-8X. This includes the OEM boot loader magic password phrases.
kernel: modules: bluetooth: separating UART and USB drivers
Not all devices need Bluetooth UART and USB drivers to be installed together. Three separate drivers have been created: - kmod-bluetooth - kmod-hci-uart - kmod-btusb
This removes -static compile option. The -static option tells GCC to link this statically with the libc, which we do not want in OpenWrt. We want to link everything dynamically to the libc. This fixes a compile problem with glibc.
b43aeb5 wireless-regdb: assert and correct maximum bandwidth within frequency difference 68588bf wireless-regdb: Update regulatory info for Syria (SY) for 2020 0dda57e wireless-regdb: Update regulatory info for Moldova (MD) on 6GHz for 2022 b19ab0b wireless-regdb: Update regulatory info for Azerbaijan (AZ) on 6GHz for 2024 f67f40d wireless-regdb: Update regulatory info for Oman (OM) bd70876 wireless-regdb: Update regulatory rules for Armenia (AM) on 2.4 and 5 GHz 6c7cbcc wireless-regdb: Permit 320 MHz bandwidth in 6 GHz band in ETSI/CEPT f9f6b30 wireless-regdb: Update regulatory rules for Austria (AT) 39b47ea wireless-regdb: Update regulatory info for Cayman Islands (KY) for 2024 3dd7ceb wireless-regdb: allow NO-INDOOR flag in db.txt 4d754a1 wireless-regdb: Update regulatory rules for Iran (IR) on both 2.4 and 5Ghz for 2021 8c8308a wireless-regdb: Update frequency range with NO-INDOOR for Oman (OM) c2f11e2 wireless-regdb: update regulatory database based on preceding changes
![[Jenkins]](/jenkins/static/f09d6917/images/svgs/logo.svg){kind=logo}
