openwrt/staging/linusw.git
3 weeks agomac80211: ath9k: replace qca,led-sources master
Rosen Penev [Wed, 14 May 2025 19:59:33 +0000 (12:59 -0700)]
mac80211: ath9k: replace qca,led-sources

Upstream seems to be using led-sources instead of custom properties.

Code mostly taken from mt76.

Changed all(few) users of qca,led_pin to use the new format.

Signed-off-by: Rosen Penev <[email protected]>
Link: https://github.com/openwrt/openwrt/pull/18805
Signed-off-by: Robert Marko <[email protected]>
3 weeks agoadb: Switch to mbedtls
Antti Seppälä [Fri, 16 May 2025 17:18:54 +0000 (20:18 +0300)]
adb: Switch to mbedtls

Currently adb uses libopenssl for certain authentication tasks between
the host and the target device such as certificate generation, hashing,
base64 encoding and pki signatures.

Add a patch to use functionalities available in mbedtls instead.

Also switch package makefile and dependency to libmbedtls and drop
patches and references to lib{crypto,openssl} as they are no longer
required.

This conserves considerable amount of space on the device as openwrt
ships with libmbedtls by default.

Signed-off-by: Antti Seppälä <[email protected]>
Link: https://github.com/openwrt/openwrt/pull/18819
Signed-off-by: Robert Marko <[email protected]>
3 weeks agorealtek: relocate mips cpc probing
Markus Stockhausen [Fri, 23 May 2025 17:21:28 +0000 (13:21 -0400)]
realtek: relocate mips cpc probing

The MIPS CPC (Cluster Power Controller) is setup during boot and can take
its configuration from the devicetree. This is currently not possible
because the cpc probing happens before dt initialization. Call order
during startup is:

setup_arch()
  prom_init() <- our function
    mips_cpc_probe()
    smp_stuff()
  arch_mem_init()
    device_tree_init() <- our function
      unflatten_and_copy_device_tree()

To avoid ugly hacking and support a clean devicetree relocate the cps/smp
stuff to device_tree_init(). This is basically the same location as in
generic mips initialization.

Signed-off-by: Markus Stockhausen <[email protected]>
Signed-off-by: Sebastian Gottschall <[email protected]>
Link: https://github.com/openwrt/openwrt/pull/18888
Signed-off-by: Robert Marko <[email protected]>
3 weeks agorealtek: take over boot command line patch into driver
Markus Stockhausen [Tue, 20 May 2025 15:11:24 +0000 (11:11 -0400)]
realtek: take over boot command line patch into driver

Make it easier to upgrade the kernel in the future. For this remove
the 320-harden-fw_init_cmdline.patch and add the logic into the
startup sequence at the right place.

Signed-off-by: Markus Stockhausen <[email protected]>
Link: https://github.com/openwrt/openwrt/pull/18853
Signed-off-by: Robert Marko <[email protected]>
3 weeks agotoolchain: gcc: update GCC14 to 14.3
Shiji Yang [Fri, 23 May 2025 13:09:01 +0000 (21:09 +0800)]
toolchain: gcc: update GCC14 to 14.3

Remove upstreamed patches:
- 020-MIPS-Include-missing-mips16.S-in-libgcc-lib1funcs.S.patch
- 021-Reuse-scratch-registers-generated-by-LRA.patch

All other patches are automatically refreshed.

Signed-off-by: Shiji Yang <[email protected]>
Link: https://github.com/openwrt/openwrt/pull/18891
Signed-off-by: Robert Marko <[email protected]>
3 weeks agomxs: drop 6.6 support
Zoltan HERPAI [Sat, 24 May 2025 10:40:05 +0000 (12:40 +0200)]
mxs: drop 6.6 support

Drop configs for Linux 6.6.

Signed-off-by: Zoltan HERPAI <[email protected]>
3 weeks agomxs: use kernel 6.12 by default
Zoltan HERPAI [Sat, 24 May 2025 10:39:19 +0000 (12:39 +0200)]
mxs: use kernel 6.12 by default

Switch to Linux kernel version 6.12.

Signed-off-by: Zoltan HERPAI <[email protected]>
3 weeks agoath79: enable 6.12 testing kernel
Shiji Yang [Wed, 30 Apr 2025 16:39:34 +0000 (00:39 +0800)]
ath79: enable 6.12 testing kernel

The 6.12 testing kernel for ath79 target is ready now.

Tested on AR9344 (ath79/nand) and QCA9531 (ath79/generic).

Signed-off-by: Shiji Yang <[email protected]>
3 weeks agoath79: irqchip/ath79-misc: fix missing prototypes warnings
Shiji Yang [Wed, 30 Apr 2025 18:36:47 +0000 (02:36 +0800)]
ath79: irqchip/ath79-misc: fix missing prototypes warnings

The newly introduced patch fixes the compilation warning for
kernel module irq-ath79-misc.

Signed-off-by: Shiji Yang <[email protected]>
3 weeks agoath79: refresh 6.12 kernel config files
Shiji Yang [Wed, 30 Apr 2025 16:39:19 +0000 (00:39 +0800)]
ath79: refresh 6.12 kernel config files

All kernel symbols are automatically refreshed by
`make kernel_oldconfig CONFIG_TARGET=target` and
`make kernel_oldconfig CONFIG_TARGET=subtarget`.

Signed-off-by: Shiji Yang <[email protected]>
3 weeks agoath79: refresh 6.12 kernel patches
Shiji Yang [Wed, 30 Apr 2025 16:38:19 +0000 (00:38 +0800)]
ath79: refresh 6.12 kernel patches

Remove upstreamed:
001-v6.11-gpio-ath79-convert-to-dynamic-GPIO-base-allocation.patch [1]

Manually rebased:
341-wifi-ath9k-obtain-system-gpios.patch
900-unaligned_access_hacks.patch

[1] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-6.12.y&id=9a473c2a093e0d1c466bf86073230e2c8b658977
Signed-off-by: Shiji Yang <[email protected]>
3 weeks agoath79: restore kernel 6.6 config files and patches
Shiji Yang [Wed, 30 Apr 2025 16:37:21 +0000 (00:37 +0800)]
ath79: restore kernel 6.6 config files and patches

Copy patches and kernel configs from 6.12 kernel to restore the
default 6.6 kernel support files.

Signed-off-by: Shiji Yang <[email protected]>
3 weeks agoath79: rename patchset and kernel configs to 6.12
Shiji Yang [Wed, 30 Apr 2025 16:35:20 +0000 (00:35 +0800)]
ath79: rename patchset and kernel configs to 6.12

This is a preparation for 6.12 kernel support. It can help us
track the files history by using the Git tool.

Signed-off-by: Shiji Yang <[email protected]>
3 weeks agoath79: refresh kernel symbol configs
Shiji Yang [Wed, 30 Apr 2025 16:33:41 +0000 (00:33 +0800)]
ath79: refresh kernel symbol configs

Manually move the common NVMEM Kconfig symbols to the shared
config file and disable them for the mikrotik subtarget. Other
changes are automatically completed by `make kernel_oldconfig`.
This is a preparation for introducing the 6.12 kernel support.

Signed-off-by: Shiji Yang <[email protected]>
3 weeks agod1: drop 6.6 support
Zoltan HERPAI [Sat, 24 May 2025 10:44:01 +0000 (10:44 +0000)]
d1: drop 6.6 support

Drop configs and patches for Linux 6.6.

Signed-off-by: Zoltan HERPAI <[email protected]>
3 weeks agod1: use kernel 6.12 by default
Zoltan HERPAI [Sat, 24 May 2025 10:43:39 +0000 (10:43 +0000)]
d1: use kernel 6.12 by default

Switch to Linux kernel version 6.12.

Signed-off-by: Zoltan HERPAI <[email protected]>
3 weeks agoimage: only filter out images when ImageBuilder is used
Robert Marko [Sat, 24 May 2025 10:20:54 +0000 (12:20 +0200)]
image: only filter out images when ImageBuilder is used

Currently, we are filtering out images if DEFAULT:=n or BROKEN:=y are set,
so if you are building from scratch and want to build custom images that
are stripped down to fit, you must edit the image recipe or its just
filtered out.

So, to allow this behaviour when building from scratch as we can assume
that person doing that knows what they are attempting to do lets just limit
the filtering to ImageBuilder.

Fixes: f060615a78e5 ("image: respect DEFAULT and BROKEN when Default profile is selected")
Signed-off-by: Robert Marko <[email protected]>
3 weeks agorealtek: prepare RTL931x for full SMP support
Markus Stockhausen [Fri, 23 May 2025 17:46:09 +0000 (13:46 -0400)]
realtek: prepare RTL931x for full SMP support

RTL931x devices are dual core with two threads each. That is a total
of 4 VPEs (CPUs) in the kernel. Adapt the kernel config for that.

Signed-off-by: Markus Stockhausen <[email protected]>
Signed-off-by: Sebastian Gottschall <[email protected]>
Link: https://github.com/openwrt/openwrt/pull/18889
Signed-off-by: Robert Marko <[email protected]>
3 weeks agointel-microcode: update to 20250512
John Audia [Wed, 21 May 2025 13:32:50 +0000 (09:32 -0400)]
intel-microcode: update to 20250512

Debian Changelogs from 20250512:
  * New upstream microcode datafile 20250512
    - Mitigations for INTEL-SA-01153 (ITS: Indirect Target Selection):
      CVE-2024-28956: Processor may incompletely mitigate Branch Target
      Injection due to indirect branch predictions that are not fully
      constrained by eIBRS nor by the IBPB barrier.  Part of the "Training
      Solo" set of vulnerabilities.
    - Mitigations for INTEL-SA-01244:
      CVE-2025-20103: Insufficient resource pool in the core management
      mechanism for some Intel Processors may allow an authenticated user
      to potentially enable denial of service via local access.
      CVE-2025-20054: Uncaught exception in the core management mechanism
      for some Intel Processors may allow an authenticated user to
      potentially enable denial of service via local access.
    - Mitigations for INTEL-SA-01247:
      CVE-2024-43420, CVE-2025-20623: Exposure of sensitive information
      caused by shared microarchitectural predictor state that influences
      transient execution for some Intel Atom and some Intel Core
      processors (10th Generation) may allow an authenticated user to
      potentially enable information disclosure via local access.
      CVE-2024-45332 (Branch Privilege Injection): Exposure of sensitive
      information caused by shared microarchitectural predictor state that
      influences transient execution in the indirect branch predictors for
      some Intel Processors may allow an authenticated user to potentially
      enable information disclosure via local access.
    - Mitigations for INTEL-SA-01322:
      CVE-2025-24495 (Training Solo): Incorrect initialization of resource
      in the branch prediction unit for some Intel Core Ultra Processors
      may allow an authenticated user to potentially enable information
      disclosure via local access (IBPB bypass)
      CVE-2025-20012 (Training Solo): Incorrect behavior order for some
      Intel Core Ultra Processors may allow an unauthenticated user to
      potentially enable information disclosure via physical access.
    - Improved fix for the Vmin Shift Instability for the Intel Core 13th
      and 14th gen processors under low-activity scenarios (sig 0xb0671).
      This microcode update is supposed to be delivered as a system
      firmware update, but according to Intel it should be effective when
      loaded by the operating system if the system firmware has revision
      0x12e.
    - Fixes for unspecified functional issues on several processor models
  * New microcodes or new extended signatures:
    sig 0x000a06d1, pf_mask 0x95, 2025-02-07, rev 0x10003a2, size 1664000
    sig 0x000a06d1, pf_mask 0x20, 2025-02-07, rev 0xa0000d1, size 1635328
    sig 0x000b0650, pf_mask 0x80, 2025-03-18, rev 0x000a, size 136192
    sig 0x000b06d1, pf_mask 0x80, 2025-03-18, rev 0x011f, size 79872
    sig 0x000c0662, pf_mask 0x82, 2025-03-20, rev 0x0118, size 90112
    sig 0x000c06a2, pf_mask 0x82, 2025-03-20, rev 0x0118
    sig 0x000c0652, pf_mask 0x82, 2025-03-20, rev 0x0118
    sig 0x000c0664, pf_mask 0x82, 2025-03-20, rev 0x0118
  * Updated microcodes:
    sig 0x00050657, pf_mask 0xbf, 2024-12-12, rev 0x5003901, size 39936
    sig 0x0005065b, pf_mask 0xbf, 2024-12-12, rev 0x7002b01, size 30720
    sig 0x000606a6, pf_mask 0x87, 2025-01-07, rev 0xd000404, size 309248
    sig 0x000606c1, pf_mask 0x10, 2025-01-07, rev 0x10002d0, size 300032
    sig 0x000706a8, pf_mask 0x01, 2024-12-05, rev 0x0026, size 76800
    sig 0x000706e5, pf_mask 0x80, 2025-01-07, rev 0x00ca, size 115712
    sig 0x000806c1, pf_mask 0x80, 2024-12-01, rev 0x00bc, size 112640
    sig 0x000806c2, pf_mask 0xc2, 2024-12-01, rev 0x003c, size 99328
    sig 0x000806d1, pf_mask 0xc2, 2024-12-11, rev 0x0056, size 105472
    sig 0x000806ec, pf_mask 0x94, 2024-11-17, rev 0x0100, size 106496
    sig 0x000806f8, pf_mask 0x87, 2025-01-28, rev 0x2b000639, size 591872
    sig 0x000806f7, pf_mask 0x87, 2025-01-28, rev 0x2b000639
    sig 0x000806f6, pf_mask 0x87, 2025-01-28, rev 0x2b000639
    sig 0x000806f5, pf_mask 0x87, 2025-01-28, rev 0x2b000639
    sig 0x000806f4, pf_mask 0x87, 2025-01-28, rev 0x2b000639
    sig 0x000806f8, pf_mask 0x10, 2025-01-28, rev 0x2c0003f7, size 624640
    sig 0x000806f6, pf_mask 0x10, 2025-01-28, rev 0x2c0003f7
    sig 0x000806f5, pf_mask 0x10, 2025-01-28, rev 0x2c0003f7
    sig 0x000806f4, pf_mask 0x10, 2025-01-28, rev 0x2c0003f7
    sig 0x00090672, pf_mask 0x07, 2024-12-12, rev 0x003a, size 226304
    sig 0x00090675, pf_mask 0x07, 2024-12-12, rev 0x003a
    sig 0x000b06f2, pf_mask 0x07, 2024-12-12, rev 0x003a
    sig 0x000b06f5, pf_mask 0x07, 2024-12-12, rev 0x003a
    sig 0x000b06f6, pf_mask 0x07, 2024-12-12, rev 0x003a
    sig 0x000b06f7, pf_mask 0x07, 2024-12-12, rev 0x003a
    sig 0x000906a3, pf_mask 0x80, 2024-12-12, rev 0x0437, size 224256
    sig 0x000906a4, pf_mask 0x80, 2024-12-12, rev 0x0437
    sig 0x000906a4, pf_mask 0x40, 2024-12-06, rev 0x000a, size 119808
    sig 0x000906ed, pf_mask 0x22, 2024-11-14, rev 0x0104, size 106496
    sig 0x000a0652, pf_mask 0x20, 2024-11-14, rev 0x0100, size 97280
    sig 0x000a0653, pf_mask 0x22, 2024-11-14, rev 0x0100, size 98304
    sig 0x000a0655, pf_mask 0x22, 2024-11-14, rev 0x0100, size 97280
    sig 0x000a0660, pf_mask 0x80, 2024-11-14, rev 0x0102, size 98304
    sig 0x000a0661, pf_mask 0x80, 2024-11-14, rev 0x0100, size 97280
    sig 0x000a0671, pf_mask 0x02, 2024-12-01, rev 0x0064, size 108544
    sig 0x000a06a4, pf_mask 0xe6, 2025-02-13, rev 0x0024, size 140288
    sig 0x000a06f3, pf_mask 0x01, 2025-02-10, rev 0x3000341, size 1542144
    sig 0x000b0671, pf_mask 0x32, 2025-03-17, rev 0x012f, size 219136
    sig 0x000b0674, pf_mask 0x32, 2025-03-17, rev 0x012f
    sig 0x000b06a2, pf_mask 0xe0, 2025-01-15, rev 0x4128, size 224256
    sig 0x000b06a3, pf_mask 0xe0, 2025-01-15, rev 0x4128
    sig 0x000b06a8, pf_mask 0xe0, 2025-01-15, rev 0x4128
    sig 0x000b06e0, pf_mask 0x19, 2024-12-06, rev 0x001d, size 139264
    sig 0x000c06f2, pf_mask 0x87, 2025-03-14, rev 0x210002a9, size 563200
    sig 0x000c06f1, pf_mask 0x87, 2025-03-14, rev 0x210002a9
  * Removed microcodes (ES/QS steppings):
    sig 0x00050656, pf_mask 0xbf, 2023-07-28, rev 0x4003605, size 38912
    sig 0x000c06f1, pf_mask 0x87, 2025-03-14, rev 0x210002a9 [EXCLUDED]

Build system: x86/64
Build-tested: x86/64
Run-tested: x86/64

Signed-off-by: John Audia <[email protected]>
Link: https://github.com/openwrt/openwrt/pull/18869
Signed-off-by: Robert Marko <[email protected]>
3 weeks agoqualcommax: ipq50xx: backport upstreamed patches for IPQ5018 tsens support
George Moussalem [Fri, 23 May 2025 10:13:21 +0000 (14:13 +0400)]
qualcommax: ipq50xx: backport upstreamed patches for IPQ5018 tsens support

Use upstreamed v6.16 patches for IPQ5018 tsens support.

Signed-off-by: George Moussalem <[email protected]>
Link: https://github.com/openwrt/openwrt/pull/18884
Signed-off-by: Robert Marko <[email protected]>
3 weeks agoqualcommax: ipq50xx: backport upstreamed patches for IPQ5018 TCSR support
George Moussalem [Fri, 23 May 2025 08:23:57 +0000 (12:23 +0400)]
qualcommax: ipq50xx: backport upstreamed patches for IPQ5018 TCSR support

Use upstreamed v6.16 patch for IPQ5018 TCSR support and setting the
download mode.

Signed-off-by: George Moussalem <[email protected]>
Link: https://github.com/openwrt/openwrt/pull/18884
Signed-off-by: Robert Marko <[email protected]>
3 weeks agoqualcommax: ipq50xx: backport upstreamed patches for IPQ5018 PCIe support
George Moussalem [Fri, 23 May 2025 07:30:35 +0000 (11:30 +0400)]
qualcommax: ipq50xx: backport upstreamed patches for IPQ5018 PCIe support

Use upstreamed patches for IPQ5018 PCIe support, including patches for
phy and controller drivers and dts nodes.

Signed-off-by: George Moussalem <[email protected]>
Link: https://github.com/openwrt/openwrt/pull/18884
Signed-off-by: Robert Marko <[email protected]>
3 weeks agotools/mold: remove static only dependencies
Rosen Penev [Tue, 20 May 2025 22:06:33 +0000 (15:06 -0700)]
tools/mold: remove static only dependencies

It seems that MOLD_MOSTLY_STATIC was required before to avoid packaging
every single dependency. But nowadays, mold uses whatever dependency it
can find and builds its own if it cannot.

Saves a small amount of compilation time.

Signed-off-by: Rosen Penev <[email protected]>
Link: https://github.com/openwrt/openwrt/pull/18881
Signed-off-by: Robert Marko <[email protected]>
3 weeks agotools/mpfr: update to 4.22
Rosen Penev [Tue, 20 May 2025 22:49:55 +0000 (15:49 -0700)]
tools/mpfr: update to 4.22

Refresh patches.

Signed-off-by: Rosen Penev <[email protected]>
Link: https://github.com/openwrt/openwrt/pull/18857
Signed-off-by: Robert Marko <[email protected]>
3 weeks agomac80211: brcm: update RPi brcmfmac patches
Álvaro Fernández Rojas [Fri, 23 May 2025 09:22:37 +0000 (11:22 +0200)]
mac80211: brcm: update RPi brcmfmac patches

- Reorganize brcmfmac patches.
- Drop outdated RPi brcmfmac patches.
- Add RPi 6.12 brcmfmac patches with "rpi-6.12" name tag (excluding SAE).

Signed-off-by: Álvaro Fernández Rojas <[email protected]>
3 weeks agoqualcommax: 6.6: remove completely
Robert Marko [Fri, 23 May 2025 12:14:29 +0000 (14:14 +0200)]
qualcommax: 6.6: remove completely

Remove all 6.6 only patches, config etc.

Signed-off-by: Robert Marko <[email protected]>
3 weeks agoqualcommax: import pending fix for multiple conf
Robert Marko [Fri, 23 May 2025 12:10:50 +0000 (14:10 +0200)]
qualcommax: import pending fix for multiple conf

Importing upstream multiple conf patches broke UNIPHY2 TX clock parenting
and thus no traffic could pass via it.

Import pending fix by Christian that fixes this[1].

[1] https://patchwork.kernel.org/project/linux-arm-msm/patch/20250522202600[email protected]/

Fixes: cc50cac8a0fd ("qualcommax: use upstreamed multiple conf clock patches")
Signed-off-by: Robert Marko <[email protected]>
3 weeks agorealtek: fix MAC_FORCE_MODE_CTRL register for RTL931x
Markus Stockhausen [Wed, 21 May 2025 06:17:13 +0000 (02:17 -0400)]
realtek: fix MAC_FORCE_MODE_CTRL register for RTL931x

Ports will not work as expected on the RTL931x devices. This comes
from a typo in the address. Fixed according to the documentation:
https://svanheule.net/realtek/mango/register/mac_force_mode_ctrl

Signed-off-by: Markus Stockhausen <[email protected]>
Signed-off-by: Sebastian Gottschall <[email protected]>
Link: https://github.com/openwrt/openwrt/pull/18864
Signed-off-by: Robert Marko <[email protected]>
3 weeks agotools: add cmake dependency to bzip2
Rosen Penev [Tue, 20 May 2025 21:52:18 +0000 (14:52 -0700)]
tools: add cmake dependency to bzip2

It's using cmake.mk so it needs CMake to build.

Signed-off-by: Rosen Penev <[email protected]>
Link: https://github.com/openwrt/openwrt/pull/18880
Signed-off-by: Robert Marko <[email protected]>
3 weeks agosifiveu: add 6.12 kernel as testing
Zoltan HERPAI [Fri, 2 May 2025 13:31:58 +0000 (15:31 +0200)]
sifiveu: add 6.12 kernel as testing

Allow selecting 6.12 as testing kernel on sifiveu.

Runtime-tested:
 - HiFive Unleashed (FU540)
 - HiFive Unmatched (FU740)

Signed-off-by: Zoltan HERPAI <[email protected]>
3 weeks agosifiveu: 6.12: drop upstreamed patches and refresh remaining ones
Zoltan HERPAI [Sat, 3 May 2025 19:48:21 +0000 (21:48 +0200)]
sifiveu: 6.12: drop upstreamed patches and refresh remaining ones

Drop upstreamed patches from 6.12 and refresh remaining ones.

Signed-off-by: Zoltan HERPAI <[email protected]>
3 weeks agosifiveu: refresh 6.12 kernel config
Zoltan HERPAI [Fri, 2 May 2025 13:31:30 +0000 (15:31 +0200)]
sifiveu: refresh 6.12 kernel config

Refresh kernel config for 6.12.

Signed-off-by: Zoltan HERPAI <[email protected]>
3 weeks agokernel/sifiveu: Restore kernel files for v6.6
Zoltan HERPAI [Wed, 30 Apr 2025 20:36:54 +0000 (20:36 +0000)]
kernel/sifiveu: Restore kernel files for v6.6

This is an automatically generated commit which aids following Kernel patch
history, as git will see the move and copy as a rename thus defeating the
purpose.

For the original discussion see:
https://lists.openwrt.org/pipermail/openwrt-devel/2023-October/041673.html

Signed-off-by: Zoltan HERPAI <[email protected]>
3 weeks agokernel/sifiveu: Create kernel files for v6.12 (from v6.6)
Zoltan HERPAI [Wed, 30 Apr 2025 20:36:54 +0000 (20:36 +0000)]
kernel/sifiveu: Create kernel files for v6.12 (from v6.6)

This is an automatically generated commit.

When doing `git bisect`, consider `git bisect --skip`.

Signed-off-by: Zoltan HERPAI <[email protected]>
3 weeks agobcm27xx: drop README patches
Álvaro Fernández Rojas [Fri, 23 May 2025 08:36:21 +0000 (10:36 +0200)]
bcm27xx: drop README patches

This patches are useless for us and can be removed.

Signed-off-by: Álvaro Fernández Rojas <[email protected]>
3 weeks agotools/elftosb: fix compilation with C++17
Rosen Penev [Wed, 21 May 2025 01:17:32 +0000 (18:17 -0700)]
tools/elftosb: fix compilation with C++17

Newer GCC and Clang default to C++17, which does not support register.
Just remove it.

Signed-off-by: Rosen Penev <[email protected]>
Link: https://github.com/openwrt/openwrt/pull/18859
Signed-off-by: Hauke Mehrtens <[email protected]>
3 weeks agouboot-bcm4908: fix build with GCC14
Shiji Yang [Sun, 18 May 2025 11:29:30 +0000 (19:29 +0800)]
uboot-bcm4908: fix build with GCC14

A lot of warnings were treated as errors after the default compiler
switched to GCC14. It's hard to fix them one by one, and this u-boot
is not maintained by upstream, so let's just silence these warnings.

Signed-off-by: Shiji Yang <[email protected]>
Link: https://github.com/openwrt/openwrt/pull/18833
Signed-off-by: Hauke Mehrtens <[email protected]>
3 weeks agokernel: bump 6.12 to 6.12.30
Mieczyslaw Nalewaj [Thu, 22 May 2025 14:29:22 +0000 (16:29 +0200)]
kernel: bump 6.12 to 6.12.30

Changelog: https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.12.30

All patches automatically rebased.

Signed-off-by: Mieczyslaw Nalewaj <[email protected]>
Link: https://github.com/openwrt/openwrt/pull/18877
Signed-off-by: Hauke Mehrtens <[email protected]>
3 weeks agouboot-mvebu: update to version 2025.04
Stefan Kalscheuer [Thu, 10 Apr 2025 16:00:37 +0000 (18:00 +0200)]
uboot-mvebu: update to version 2025.04

Update package to the latest stable version. All patches automatically
refreshed.

Signed-off-by: Stefan Kalscheuer <[email protected]>
Link: https://github.com/openwrt/openwrt/pull/17813
Signed-off-by: Hauke Mehrtens <[email protected]>
3 weeks agorealtek: fix mdio parent/child locking issues
Markus Stockhausen [Sat, 17 May 2025 06:22:09 +0000 (02:22 -0400)]
realtek: fix mdio parent/child locking issues

Since the early beginning of the Realtek DSA driver there is an uncovered
locking issue between the standard (parent) mdio bus and the DSA (child)
mdio bus. This comes from the fact that the DSA bus simply links to the
parent read and write functions and calls them directly. This leads to
the following lock issue.

- Child bus calls phy_read/write functions and uses its internal lock
- Parent bus calls phy_read/write functions and uses its internal lock

It becomes clear that critical section can be accessed twice without
knowing that a operation from the other bus is currently active. This
can lead to critical malfunctions because the mdio driver needs a lot of
internal magic to get page selection done right. Effects are:

- The original page is lost after a phy_write/read_paged() call
- dmesg like "Realtek RTL8218B (external) rtl838x slave mii-0:00:
  Expected external RTL8218B, found PHY-ID 6b23"

Other DSA drivers simply use the read/write functions from the parent bus
and thus avoid locking issues. Do it the same way.

Fixes: 2b88563ee5aafd9 ("realtek: update the tree to the latest refactored version")
Signed-off-by: Markus Stockhausen <[email protected]>
Link: https://github.com/openwrt/openwrt/pull/18824
Signed-off-by: Robert Marko <[email protected]>
3 weeks agotools/quilt: update to 0.69
Rosen Penev [Tue, 20 May 2025 22:53:26 +0000 (15:53 -0700)]
tools/quilt: update to 0.69

Refresh patches.

Signed-off-by: Rosen Penev <[email protected]>
Link: https://github.com/openwrt/openwrt/pull/18858
Signed-off-by: Robert Marko <[email protected]>
3 weeks agoboot: uboot-armsr: update to U-Boot 2025.04
Mathew McBride [Tue, 20 May 2025 03:40:07 +0000 (13:40 +1000)]
boot: uboot-armsr: update to U-Boot 2025.04

This U-Boot version is used to generate a 'reference'
U-Boot binary for QEMU's 'virt' machine on both
armv7 and armv8.

It has not been updated since EFI support was merged
into the then-armvirt target, so we should bring it up
to the latest version.

The 'mkeficapsule' tool is disabled due to a host-side
dependency on GnuTLS.

Signed-off-by: Mathew McBride <[email protected]>
Link: https://github.com/openwrt/openwrt/pull/18862
Signed-off-by: Robert Marko <[email protected]>
3 weeks agoramips: fix wrg-header image recipe
Shiji Yang [Sun, 18 May 2025 12:42:19 +0000 (20:42 +0800)]
ramips: fix wrg-header image recipe

Before generating the factory image, check if the input file
exists. Fix the build error when sysupgrade image is too big:

[mkwrgimg] *** error: stat failed on /builder/shared-workdir/build/build_dir/target-mipsel_24kc_musl/linux-ramips_rt288x/tmp/openwrt-ramips-rt288x-airlink101_ar670w-squashfs-factory.bin, No such file or directory

Signed-off-by: Shiji Yang <[email protected]>
Link: https://github.com/openwrt/openwrt/pull/18836
Signed-off-by: Robert Marko <[email protected]>
3 weeks agod1: add 6.12 kernel as testing
Zoltan HERPAI [Mon, 5 May 2025 21:24:15 +0000 (23:24 +0200)]
d1: add 6.12 kernel as testing

Allow selecting 6.12 as testing kernel on d1.

Runtime-tested:
 - Nezha D1

Signed-off-by: Zoltan HERPAI <[email protected]>
3 weeks agod1: 6.12: refresh kernel config
Zoltan HERPAI [Mon, 5 May 2025 21:23:55 +0000 (23:23 +0200)]
d1: 6.12: refresh kernel config

Refresh kernel config.

Signed-off-by: Zoltan HERPAI <[email protected]>
3 weeks agod1: 6.12: remove upstreamed patches and refresh remaining ones
Zoltan HERPAI [Mon, 5 May 2025 20:14:18 +0000 (22:14 +0200)]
d1: 6.12: remove upstreamed patches and refresh remaining ones

Remove patches that have been upstreamed or dropped, and refresh
the remaining ones as required.

Signed-off-by: Zoltan HERPAI <[email protected]>
3 weeks agokernel/d1: Restore kernel files for v6.6
Zoltan HERPAI [Sat, 3 May 2025 22:29:54 +0000 (00:29 +0200)]
kernel/d1: Restore kernel files for v6.6

This is an automatically generated commit which aids following Kernel patch
history, as git will see the move and copy as a rename thus defeating the
purpose.

For the original discussion see:
https://lists.openwrt.org/pipermail/openwrt-devel/2023-October/041673.html

Signed-off-by: Zoltan HERPAI <[email protected]>
3 weeks agokernel/d1: Create kernel files for v6.12 (from v6.6)
Zoltan HERPAI [Sat, 3 May 2025 22:29:54 +0000 (00:29 +0200)]
kernel/d1: Create kernel files for v6.12 (from v6.6)

This is an automatically generated commit.

When doing `git bisect`, consider `git bisect --skip`.

Signed-off-by: Zoltan HERPAI <[email protected]>
3 weeks agogeneric: backport upstream v6.16 Realtek PHY patches
Álvaro Fernández Rojas [Thu, 22 May 2025 08:43:00 +0000 (10:43 +0200)]
generic: backport upstream v6.16 Realtek PHY patches

83d962316128 net: phy: realtek: add RTL8127-internal PHY
708686132ba0 net: phy: realtek: Add support for PHY LEDs on RTL8211E
be1cc96ddf82 net: phy: realtek: use __set_bit() in rtl8211f_led_hw_control_get()
8c4d0172657c net: phy: realtek: Group RTL82* macro definitions
12d40df259e3 net: phy: realtek: add RTL8211F register defines
7c6fa3ffd265 net: phy: realtek: Clean up RTL821x ExtPage access
f3b265358b91 net: phy: realtek: remove unsed RTL821x_PHYSR* macros
7840e4d6f48a net: phy: realtek: Add support for WOL magic packet on RTL8211F

Signed-off-by: Álvaro Fernández Rojas <[email protected]>
3 weeks agogeneric: backport upstream v6.16 r8169 patches
Álvaro Fernández Rojas [Thu, 22 May 2025 08:39:47 +0000 (10:39 +0200)]
generic: backport upstream v6.16 r8169 patches

f24f7b2f3af9 r8169: add support for RTL8127A
4f51e7d370a0 r8169: merge chip versions 52 and 53 (RTL8117)
f372ef6ed5a6 r8169: merge chip versions 64 and 65 (RTL8125D)
4dec0702b862 r8169: merge chip versions 70 and 71 (RTL8126A)
b7ed5d5a78fc r8169: use pci_prepare_to_sleep in rtl_shutdown
fe733618b27a r8169: add RTL_GIGA_MAC_VER_LAST to facilitate adding support for new chip versions
2b065c098c37 r8169: refactor chip version detection
0c49baf099ba r8169: add helper rtl8125_phy_param
8c40d99e5f43 r8169: add helper rtl_csi_mod for accessing extended config space

Signed-off-by: Álvaro Fernández Rojas <[email protected]>
3 weeks agoath79: remove platform_device_id from drivers
Rosen Penev [Sun, 18 May 2025 01:44:05 +0000 (18:44 -0700)]
ath79: remove platform_device_id from drivers

This was needed while ar71xx was in tree. This is no longer the case.
Not only that, these have already been converted to OF.

Signed-off-by: Rosen Penev <[email protected]>
Link: https://github.com/openwrt/openwrt/pull/18860
Signed-off-by: Robert Marko <[email protected]>
3 weeks agomxs: add 6.12 kernel as testing
Zoltan HERPAI [Fri, 2 May 2025 13:16:59 +0000 (15:16 +0200)]
mxs: add 6.12 kernel as testing

Allow selecting 6.12 as testing kernel on mxs.

Runtime-tested:
 - Olinuxino Micro

Signed-off-by: Zoltan HERPAI <[email protected]>
3 weeks agomxs: refresh config for 6.12
Zoltan HERPAI [Fri, 2 May 2025 13:16:18 +0000 (15:16 +0200)]
mxs: refresh config for 6.12

Refresh kernel config for 6.12.

Signed-off-by: Zoltan HERPAI <[email protected]>
3 weeks agokernel/mxs: Restore kernel files for v6.6
Zoltan HERPAI [Wed, 30 Apr 2025 14:05:42 +0000 (14:05 +0000)]
kernel/mxs: Restore kernel files for v6.6

This is an automatically generated commit which aids following Kernel patch
history, as git will see the move and copy as a rename thus defeating the
purpose.

For the original discussion see:
https://lists.openwrt.org/pipermail/openwrt-devel/2023-October/041673.html

Signed-off-by: Zoltan HERPAI <[email protected]>
3 weeks agokernel/mxs: Create kernel files for v6.12 (from v6.6)
Zoltan HERPAI [Wed, 30 Apr 2025 14:05:42 +0000 (14:05 +0000)]
kernel/mxs: Create kernel files for v6.12 (from v6.6)

This is an automatically generated commit.

When doing `git bisect`, consider `git bisect --skip`.

Signed-off-by: Zoltan HERPAI <[email protected]>
3 weeks agogeneric: 6.12: add missing symbols
Zoltan HERPAI [Sat, 3 May 2025 21:14:38 +0000 (21:14 +0000)]
generic: 6.12: add missing symbols

These were found while working on mxs and sunxi 6.12.

Signed-off-by: Zoltan HERPAI <[email protected]>
3 weeks agorealtek: harmonize power functions for RTL8214FC
Markus Stockhausen [Sun, 4 May 2025 19:40:00 +0000 (15:40 -0400)]
realtek: harmonize power functions for RTL8214FC

There are currently two power functions for the RTL8214FC in the driver

- rtl8380_rtl8214fc_on_off(): powers on/off both ports
- rtl8214fc_power_set(): powers on/off fibre or copper individually

While it seems obvious to merge these, one of them uses extended register
29 and the other register 30 to achieve the update. From looking at the
GPL source drops both methods exist with exactly the same operations. So
where to go from here? The descision was made based on:

- register 30 is only used during patching, 29 during normal operation
- Avoid raw page if possible to use function for RTL839x

So the attached patch was created. The result in the power down bits
was compared for the two old and the new implementation. Result is
always the same.

Signed-off-by: Markus Stockhausen <[email protected]>
Link: https://github.com/openwrt/openwrt/pull/18707
Signed-off-by: Robert Marko <[email protected]>
3 weeks agorealtek: Identify RTL9311 properly
Markus Stockhausen [Wed, 21 May 2025 15:29:05 +0000 (11:29 -0400)]
realtek: Identify RTL9311 properly

RTL9311 switches (like the Linksys LGS352C) will boot but have not set
the right family id in the soc_info structure. Fix that so drivers do
their work right when checking for that.

Signed-off-by: Markus Stockhausen <[email protected]>
Link: https://github.com/openwrt/openwrt/pull/18871
Signed-off-by: Robert Marko <[email protected]>
3 weeks agobcm27xx: refresh patches for v6.12.29
Álvaro Fernández Rojas [Wed, 21 May 2025 15:19:42 +0000 (17:19 +0200)]
bcm27xx: refresh patches for v6.12.29

Commit 0912d3f59547 ("kernel: bump 6.12 to 6.12.29") was merged right after
bcm27xx 6.12 support commits, causing conflicts.

Refresh patches and removed upstreamed patch in v6.12.29:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-6.12.y&id=a5f162727b91e480656da1876247a91f651f76de

Fixes: 0912d3f59547 ("kernel: bump 6.12 to 6.12.29")
Signed-off-by: Álvaro Fernández Rojas <[email protected]>
3 weeks agomold: update to 2.39.1
Robert Marko [Wed, 21 May 2025 09:15:21 +0000 (11:15 +0200)]
mold: update to 2.39.1

Update to latest mold linker version 2.39.1.

Link: https://github.com/openwrt/openwrt/pull/18865
Signed-off-by: Robert Marko <[email protected]>
3 weeks agobcm27xx: drop 6.6 support
Álvaro Fernández Rojas [Wed, 21 May 2025 12:10:49 +0000 (14:10 +0200)]
bcm27xx: drop 6.6 support

Drop configs, files and patches for Linux 6.6.

Signed-off-by: Álvaro Fernández Rojas <[email protected]>
3 weeks agobcm27xx: use kernel 6.12 by default
Álvaro Fernández Rojas [Wed, 21 May 2025 12:07:39 +0000 (14:07 +0200)]
bcm27xx: use kernel 6.12 by default

Switch to Linux kernel version 6.12.

Signed-off-by: Álvaro Fernández Rojas <[email protected]>
3 weeks agobcm27xx: switch to upstream SDHOST driver
Álvaro Fernández Rojas [Wed, 21 May 2025 10:28:44 +0000 (12:28 +0200)]
bcm27xx: switch to upstream SDHOST driver

The RPi upstream repo switched to the upstream SDHOST driver some time ago, so
it's time to do the same in our configs.

Signed-off-by: Álvaro Fernández Rojas <[email protected]>
3 weeks agorealtek: refactor net rx interrupt handler rtl83xx_net_irq()
Markus Stockhausen [Tue, 20 May 2025 20:10:44 +0000 (16:10 -0400)]
realtek: refactor net rx interrupt handler rtl83xx_net_irq()

Cleanup the code of the RTL83xx packet receive interrupt handler. Not
only for better readability but to avoid inconsistencies and stalls on
the RTL839x targets.

The current implementation seems to come from the GPL source code.
Calling the existing cleanup() function inside the interrupt context
without any locks conflicts with SMP & NAPI polling and makes things
worse instead of giving any benefit. Simply ignore RX buffer overruns
and let the device handle packet dropping itself.

Signed-off-by: Markus Stockhausen <[email protected]>
Link: https://github.com/openwrt/openwrt/pull/18855
Signed-off-by: Robert Marko <[email protected]>
3 weeks agokernel: bump 6.12 to 6.12.29
Mieczyslaw Nalewaj [Sun, 18 May 2025 13:02:42 +0000 (15:02 +0200)]
kernel: bump 6.12 to 6.12.29

Changelog: https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.12.29

Removed upstreamed:
        generic/pending-6.12/730-net-ethernet-mtk_eth_soc-reset-all-TX-queues-on-DMA-.patch[1]

Added settings:
        x86: CONFIG_MITIGATION_ITS=y[2]

1. https://web.git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-6.12.y&id=aac9d5fa537b0c19f6d3af3c8a124028510bb647
2. https://web.git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-6.12.y&id=68d59e9ba38424389168eddf8791265818f67292

All other patches automatically rebased.

Build system: x86/64
Build-tested: x86/64
Run-tested: x86/64

Signed-off-by: Mieczyslaw Nalewaj <[email protected]>
Link: https://github.com/openwrt/openwrt/pull/18837
Signed-off-by: Robert Marko <[email protected]>
3 weeks agotoolchain: glibc: Update glibc 2.38 to recent HEAD
Konstantin Demin [Wed, 21 May 2025 05:34:16 +0000 (08:34 +0300)]
toolchain: glibc: Update glibc 2.38 to recent HEAD

3be3728d elf: Ignore LD_LIBRARY_PATH and debug env var for setuid for static
454f24e9 support: Use const char * argument in support_capture_subprogram_self_sgid
4335cd9b support: Add support_record_failure_barrier
31fa0f73 elf: Test case for bug 32976 (CVE-2025-4802)
ca41fe44 x86_64: Fix typo in ifunc-impl-list.c.

Signed-off-by: Konstantin Demin <[email protected]>
Link: https://github.com/openwrt/openwrt/pull/18863
Signed-off-by: Robert Marko <[email protected]>
3 weeks agobcm27xx: enable 6.12 kernel testing
Álvaro Fernández Rojas [Wed, 7 May 2025 12:35:43 +0000 (14:35 +0200)]
bcm27xx: enable 6.12 kernel testing

bcm27xx target now supports 6.12 kernel as testing.

Tested-by: Zoltan HERPAI <[email protected]>
Signed-off-by: Álvaro Fernández Rojas <[email protected]>
3 weeks agobcm27xx: update config for kernel 6.12
Álvaro Fernández Rojas [Wed, 7 May 2025 12:00:08 +0000 (14:00 +0200)]
bcm27xx: update config for kernel 6.12

Update bcm27xx target config for kernel 6.12.

Signed-off-by: Álvaro Fernández Rojas <[email protected]>
3 weeks agobcm27xx: add 6.12 patches from RPi repo
Álvaro Fernández Rojas [Wed, 7 May 2025 10:08:00 +0000 (12:08 +0200)]
bcm27xx: add 6.12 patches from RPi repo

These patches were generated from:
https://github.com/raspberrypi/linux/commits/rpi-6.12.y
With the following command:
git format-patch -N v6.12.27..HEAD
(HEAD -> 8d3206ee456a5ecdf9ddbfd8e5e231e4f0cd716e)

Exceptions:
- (def)configs patches
- github workflows patches
- applied & reverted patches
- readme patches
- wireless patches

Signed-off-by: Álvaro Fernández Rojas <[email protected]>
3 weeks agobcm27xx: restore kernel config for v6.6
Álvaro Fernández Rojas [Wed, 7 May 2025 10:00:43 +0000 (12:00 +0200)]
bcm27xx: restore kernel config for v6.6

This is an automatically generated commit which aids following Kernel patch
history, as git will see the move and copy as a rename thus defeating the
purpose.

For the original discussion see:
https://lists.openwrt.org/pipermail/openwrt-devel/2023-October/041673.html

Signed-off-by: Álvaro Fernández Rojas <[email protected]>
3 weeks agobcm27xx: create kernel config for v6.12 (from v6.6)
Álvaro Fernández Rojas [Wed, 7 May 2025 09:59:29 +0000 (11:59 +0200)]
bcm27xx: create kernel config for v6.12 (from v6.6)

This is an automatically generated commit.

When doing `git bisect`, consider `git bisect --skip`.

Signed-off-by: Álvaro Fernández Rojas <[email protected]>
3 weeks agomvebu: armada37xx: add pending PXA I2C recovery fix
Robert Marko [Tue, 20 May 2025 09:25:17 +0000 (11:25 +0200)]
mvebu: armada37xx: add pending PXA I2C recovery fix

Import pending PXA I2C recovery fixes so that if I2C recovery is enabled in
the DTS it does not completely break I2C as it currently does since kernel
6.6.

Signed-off-by: Robert Marko <[email protected]>
3 weeks agomvebu: armada37xx: backport pinctrl fixes
Robert Marko [Tue, 20 May 2025 09:23:52 +0000 (11:23 +0200)]
mvebu: armada37xx: backport pinctrl fixes

Backport upstream pinctrl fixes, these are required for the follow-up I2C
PXA recovery fixes.

Signed-off-by: Robert Marko <[email protected]>
3 weeks agounetmsg: fix host name in response messages
Felix Fietkau [Tue, 20 May 2025 12:32:02 +0000 (14:32 +0200)]
unetmsg: fix host name in response messages

Avoid using loop iterator variable when generating the closure

Signed-off-by: Felix Fietkau <[email protected]>
3 weeks agounetmsg: add support for sending requests/messages to specific hosts
Felix Fietkau [Fri, 16 May 2025 11:44:38 +0000 (13:44 +0200)]
unetmsg: add support for sending requests/messages to specific hosts

Makes it possible to implement unetmsg APIs for host control

Signed-off-by: Felix Fietkau <[email protected]>
3 weeks agoramips: mt7621: fix broken hexdump expression in iodata.sh
INAGAKI Hiroshi [Sat, 17 May 2025 11:22:57 +0000 (20:22 +0900)]
ramips: mt7621: fix broken hexdump expression in iodata.sh

Use the "1/1" as a iteration count of hexdump expression instead of the
broken "1", to fix the issue that the invalid bootnum will be obtained.

Currently, the hexdump command always outputs "0" when the decimal format
and the iteration count "1" are specified[0]. This is unexpected
behaviour, but the cause is unknown and use this fix as a workaround.

[0]: https://github.com/openwrt/openwrt/issues/18808

Signed-off-by: INAGAKI Hiroshi <[email protected]>
Link: https://github.com/openwrt/openwrt/pull/18827
Signed-off-by: Robert Marko <[email protected]>
3 weeks agokernel/i2c: x86: remove kernel 6.12 conditions checking
Mieczyslaw Nalewaj [Mon, 19 May 2025 21:03:43 +0000 (23:03 +0200)]
kernel/i2c: x86: remove kernel 6.12 conditions checking

After removing kernel 6.6 support for x86 targets,
kernel 6.12 conditions no longer need to be checked.

Signed-off-by: Mieczyslaw Nalewaj <[email protected]>
Link: https://github.com/openwrt/openwrt/pull/18848
Signed-off-by: Robert Marko <[email protected]>
3 weeks agox86: drop 6.6 support
Mieczyslaw Nalewaj [Mon, 19 May 2025 20:27:57 +0000 (22:27 +0200)]
x86: drop 6.6 support

Drop configs, files and patches for Linux 6.6.

Signed-off-by: Mieczyslaw Nalewaj <[email protected]>
Link: https://github.com/openwrt/openwrt/pull/18848
Signed-off-by: Robert Marko <[email protected]>
3 weeks agox86: use kernel 6.12 by default
Mieczyslaw Nalewaj [Mon, 19 May 2025 20:21:59 +0000 (22:21 +0200)]
x86: use kernel 6.12 by default

Switch to Linux kernel version 6.12.

Signed-off-by: Mieczyslaw Nalewaj <[email protected]>
Link: https://github.com/openwrt/openwrt/pull/18848
Signed-off-by: Robert Marko <[email protected]>
3 weeks agotoolchain: glibc: set min kernel version to 6.6
Konstantin Demin [Tue, 20 May 2025 07:04:14 +0000 (10:04 +0300)]
toolchain: glibc: set min kernel version to 6.6

Minimum kernel version is 6.6 so it's safe to increase minimum kernel version to 6.6 for glibc too.
This change effectively removes last compatibility quirk in [1] which leads to better/faster detection of SVE support in string ifuncs for aarch64.
Furthermore, this change will allow to use "fchmodat2" syscall within fchmodat() wrapper in future glibc versions (starting from 2.39) as noted in [2] and [3].

[1] https://sourceware.org/git/?p=glibc.git;a=blob;f=sysdeps/unix/sysv/linux/aarch64/cpu-features.c;h=4a205a6b35050ffcfac771b4b4ff2d9fb7581f93;hb=refs/heads/release/2.38/master
[2] https://sourceware.org/git/?p=glibc.git;a=blob;f=sysdeps/unix/sysv/linux/kernel-features.h;h=86b2d3ce512588c8823c11076c91116092836402;hb=refs/heads/release/2.41/master
[3] https://sourceware.org/git/?p=glibc.git;a=blob;f=sysdeps/unix/sysv/linux/fchmodat.c;h=dd1fa5db86bde99fe3eb4804b06c5adf11914b94;hb=refs/heads/release/2.41/master

Signed-off-by: Konstantin Demin <[email protected]>
Link: https://github.com/openwrt/openwrt/pull/18850
Signed-off-by: Robert Marko <[email protected]>
3 weeks agoqualcommax: default to 6.12
Robert Marko [Mon, 19 May 2025 10:16:32 +0000 (12:16 +0200)]
qualcommax: default to 6.12

Default qualcommax target to 6.12 kernel.

It makes no sense for us to double the effort required for backporting
upstreamed patches or for downstream modifications.

Link: https://github.com/openwrt/openwrt/pull/18840
Signed-off-by: Robert Marko <[email protected]>
3 weeks agotreewide: strip trailing whitespace
Mieczyslaw Nalewaj [Mon, 19 May 2025 12:27:36 +0000 (14:27 +0200)]
treewide: strip trailing whitespace

Strip trailing whitespace in all code:
find . -type f | grep "\.c$" | xargs sed -i 's/[ \t]\+$//'
find . -type f | grep "\.h$" | xargs sed -i 's/[ \t]\+$//'
find . -type f | grep "\.dts$" | xargs sed -i 's/[ \t]\+$//'
find . -type f | grep "\.dtsi$" | xargs sed -i 's/[ \t]\+$//'

Signed-off-by: Mieczyslaw Nalewaj <[email protected]>
Link: https://github.com/openwrt/openwrt/pull/18626
Signed-off-by: Robert Marko <[email protected]>
4 weeks agomediatek: mt7622: add the missing phy interrupt-parent for WAX206
Shiji Yang [Mon, 19 May 2025 00:50:10 +0000 (08:50 +0800)]
mediatek: mt7622: add the missing phy interrupt-parent for WAX206

Based on other mt7622 dts, it is not difficult to infer that the
missing interrupt controller is "pio". Fix dtc warning:

mt7622.dtsi:282.3-26: Warning (interrupts_property): /ethernet@1b100000/mdio-bus/ethernet-phy@7:#interrupt-cells: size is (8), expected multiple of 12

Signed-off-by: Shiji Yang <[email protected]>
4 weeks agomediatek: mt7622: various dtc warning fixes for D-Link EAGLE PRO AI
Shiji Yang [Mon, 19 May 2025 00:26:37 +0000 (08:26 +0800)]
mediatek: mt7622: various dtc warning fixes for D-Link EAGLE PRO AI

- Add missing #address-cells and #size-cells to the partition nodes.
- Add missing #address-cells and #size-cells to the switch ports nodes.

This patch fixes the following dtc warnings:

../dts/mt7622-dlink-eagle-pro-ai-r32-a1.dts:74.3-20: Warning (reg_format): /spi@1100d000/flash@0/partitions/partition@180000/nvmem-layout/macaddr@81:reg: property has invalid length (8 bytes) (#address-cells == 2, #size-cells == 1)
../dts/mt7622-dlink-eagle-pro-ai-ax3200-a1.dtsi:289.6-36: Warning (reg_format): /spi@1100d000/flash@0/partitions/partition@2C0000/partition@0:reg: property has invalid length (8 bytes) (#address-cells == 2, #size-cells == 1)
../dts/mt7622-dlink-eagle-pro-ai-ax3200-a1.dtsi:294.6-36: Warning (reg_format): /spi@1100d000/flash@0/partitions/partition@2C0000/partition@800000:reg: property has invalid length (8 bytes) (#address-cells == 2, #size-cells == 1)
../dts/mt7622-dlink-eagle-pro-ai-ax3200-a1.dtsi:306.6-36: Warning (reg_format): /spi@1100d000/flash@0/partitions/partition@2FC0000/partition@0:reg: property has invalid length (8 bytes) (#address-cells == 2, #size-cells == 1)
../dts/mt7622-dlink-eagle-pro-ai-ax3200-a1.dtsi:311.6-36: Warning (reg_format): /spi@1100d000/flash@0/partitions/partition@2FC0000/partition@800000:reg: property has invalid length (8 bytes) (#address-cells == 2, #size-cells == 1)
../dts/mt7622-dlink-eagle-pro-ai-ax3200-a1.dtsi:90.6-16: Warning (reg_format): /ethernet@1b100000/mdio-bus/switch@1f/ports/port@4:reg: property has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)
../dts/mt7622-dlink-eagle-pro-ai-ax3200-a1.dtsi:97.6-16: Warning (reg_format): /ethernet@1b100000/mdio-bus/switch@1f/ports/port@6:reg: property has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)
../dts/mt7622-dlink-eagle-pro-ai-r32-a1.dts:50.4-14: Warning (reg_format): /ethernet@1b100000/mdio-bus/switch@1f/ports/port@0:reg: property has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)
../dts/mt7622-dlink-eagle-pro-ai-r32-a1.dts:55.4-14: Warning (reg_format): /ethernet@1b100000/mdio-bus/switch@1f/ports/port@1:reg: property has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)
../dts/mt7622-dlink-eagle-pro-ai-m32-a1.dts:45.4-14: Warning (reg_format): /ethernet@1b100000/mdio-bus/switch@1f/ports/port@2:reg: property has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)
../dts/mt7622-dlink-eagle-pro-ai-m32-a1.dts:50.4-14: Warning (reg_format): /ethernet@1b100000/mdio-bus/switch@1f/ports/port@3:reg: property has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)
../dts/mt7622-dlink-eagle-pro-ai-r32-a1.dts:60.4-14: Warning (reg_format): /ethernet@1b100000/mdio-bus/switch@1f/ports/port@2:reg: property has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)
../dts/mt7622-dlink-eagle-pro-ai-r32-a1.dts:65.4-14: Warning (reg_format): /ethernet@1b100000/mdio-bus/switch@1f/ports/port@3:reg: property has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)

Signed-off-by: Shiji Yang <[email protected]>
4 weeks agomediatek: mt7622: fix mmc dtc warnings
Shiji Yang [Mon, 19 May 2025 00:20:52 +0000 (08:20 +0800)]
mediatek: mt7622: fix mmc dtc warnings

Add missing #address-cells and #size-cells to fix the
following dtc warnings:

mt7622-bananapi-bpi-r64.dts:243.3-13: Warning (reg_format): /mmc@11230000/card@0:reg: property has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)
mt7622-bananapi-bpi-r64.dts:278.3-13: Warning (reg_format): /mmc@11240000/card@0:reg: property has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)

Signed-off-by: Shiji Yang <[email protected]>
4 weeks agomediatek: mt7623: fix mmc dtc warnings
Shiji Yang [Mon, 19 May 2025 00:20:06 +0000 (08:20 +0800)]
mediatek: mt7623: fix mmc dtc warnings

Add missing #address-cells and #size-cells to fix the
following dtc warnings:

mt7623n-bananapi-bpi-r2.dts:346.3-13: Warning (reg_format): /mmc@11230000/card@0:reg: property has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)
mt7623n-bananapi-bpi-r2.dts:373.3-13: Warning (reg_format): /mmc@11240000/card@0:reg: property has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)
../dts/mt7623a-unielec-u7623-02.dts:23.3-13: Warning (reg_format): /mmc@11230000/card@0:reg: property has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)

Signed-off-by: Shiji Yang <[email protected]>
4 weeks agomediatek: filogic: fix mxl phy node dtc warnings
Shiji Yang [Mon, 19 May 2025 00:15:21 +0000 (08:15 +0800)]
mediatek: filogic: fix mxl phy node dtc warnings

Add missing #address-cells and #size-cells to fix the
following dtc warnings:

mt7981-rfb-mxl-2p5g-phy-eth1.dtso:26.5-15: Warning (reg_format): /fragment@1/__overlay__/ethernet-phy@5:reg: property has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)
mt7981-rfb-mxl-2p5g-phy-swp5.dtso:27.5-15: Warning (reg_format): /fragment@1/__overlay__/ethernet-phy@5:reg: property has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)

Signed-off-by: Shiji Yang <[email protected]>
4 weeks agomediatek: filogic: fix SPI node reg size dtc warnings
Shiji Yang [Mon, 19 May 2025 00:12:56 +0000 (08:12 +0800)]
mediatek: filogic: fix SPI node reg size dtc warnings

Add missing #address-cells and #size-cells to fix the
following dtc warnings:

../dts/mt7981b-cmcc-rax3000m-nand.dtso:67.5-15: Warning (reg_format): /fragment@4/__overlay__/spi_nand@0:reg: property has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)
mt7988a-rfb-snfi-nand.dtso:20.5-15: Warning (reg_format): /fragment@0/__overlay__/flash@0:reg: property has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)
mt7988a-rfb-spim-nand.dtso:22.5-15: Warning (reg_format): /fragment@0/__overlay__/flash@0:reg: property has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)
mt7988a-rfb-spim-nor.dtso:31.5-15: Warning (reg_format): /fragment@0/__overlay__/flash@0:reg: property has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)

Signed-off-by: Shiji Yang <[email protected]>
4 weeks agomediatek: filogic: fix bpi-r4 eeprom dtc warnings
Shiji Yang [Mon, 19 May 2025 00:10:52 +0000 (08:10 +0800)]
mediatek: filogic: fix bpi-r4 eeprom dtc warnings

Add missing #address-cells and #size-cells to fix the
following dtc warnings:

mt7988a-bananapi-bpi-r4-wifi-mt7996a.dtso:31.5-18: Warning (reg_format): /fragment@1/__overlay__/wifi_eeprom@51:reg: property has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)
mt7988a-bananapi-bpi-r4-wifi-mt7996a.dtso:50.5-18: Warning (reg_format): /fragment@1/__overlay__/wifi_eeprom@52:reg: property has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)

Signed-off-by: Shiji Yang <[email protected]>
4 weeks agomediatek: filogic: fix PCIe node dtc warnings
Shiji Yang [Mon, 19 May 2025 00:09:47 +0000 (08:09 +0800)]
mediatek: filogic: fix PCIe node dtc warnings

Add missing #address-cells and #size-cells to fix the
following dtc warnings:

../dts/mt7986a-smartrg-bonanza-peak.dtsi:359.4-27: Warning (reg_format): /soc/pcie@11280000/pcie@0,0/mt7915@0,0:reg: property has invalid length (20 bytes) (#address-cells == 2, #size-cells == 1)
../dts/mt7988a-smartrg-mt-stuart.dtsi:551.4-27: Warning (reg_format): /soc/pcie@11300000/pcie@0,0/mt7996@0,0:reg: property has invalid length (20 bytes) (#address-cells == 2, #size-cells == 1)
../dts/mt7988a-arcadyan-mozart.dts:331.4-27: Warning (reg_format): /soc/pcie@11300000/pcie@0,0/mt7996@1,0:reg: property has invalid length (20 bytes) (#address-cells == 2, #size-cells == 1)
../dts/mt7988d-asus-zenwifi-bt8.dtsi:291.4-27: Warning (reg_format): /soc/pcie@11300000/pcie@0,0/mt7996@0,0:reg: property has invalid length (20 bytes) (#address-cells == 2, #size-cells == 1)
mt7988a-bananapi-bpi-r4-wifi-mt7996a.dtso:72.5-28: Warning (reg_format): /fragment@2/__overlay__/pcie@0,0:reg: property has invalid length (20 bytes) (#address-cells == 2, #size-cells == 1)
mt7988a-bananapi-bpi-r4-wifi-mt7996a.dtso:76.6-29: Warning (reg_format): /fragment@2/__overlay__/pcie@0,0/wifi@0,0:reg: property has invalid length (20 bytes) (#address-cells == 2, #size-cells == 1)
mt7988a-bananapi-bpi-r4-wifi-mt7996a.dtso:88.5-28: Warning (reg_format): /fragment@3/__overlay__/pcie@0,0:reg: property has invalid length (20 bytes) (#address-cells == 2, #size-cells == 1)
mt7988a-bananapi-bpi-r4-wifi-mt7996a.dtso:92.6-29: Warning (reg_format): /fragment@3/__overlay__/pcie@0,0/wifi@0,0:reg: property has invalid length (20 bytes) (#address-cells == 2, #size-cells == 1)
mt7988a-rfb-spim-nand-factory.dtso:47.5-28: Warning (reg_format): /fragment@1/__overlay__/pcie@0,0:reg: property has invalid length (20 bytes) (#address-cells == 2, #size-cells == 1)
mt7988a-rfb-spim-nand-factory.dtso:51.6-29: Warning (reg_format): /fragment@1/__overlay__/pcie@0,0/wifi@0,0:reg: property has invalid length (20 bytes) (#address-cells == 2, #size-cells == 1)
../dts/mt7986a-tplink-tl-xtr8488.dts:305.4-27: Warning (reg_format): /soc/pcie@11280000/pcie@0,0/wifi@0,0:reg: property has invalid length (20 bytes) (#address-cells == 2, #size-cells == 1)
../dts/mt7986a-zyxel-ex5700-telenor.dts:268.4-27: Warning (reg_format): /soc/pcie@11280000/pcie@0,0/wifi@0,0:reg: property has invalid length (20 bytes) (#address-cells == 2, #size-cells == 1)
mt7988a-bananapi-bpi-r4-wifi-mt7996a.dtso:77.5-28: Warning (reg_format): /fragment@2/__overlay__/pcie@0,0:reg: property has invalid length (20 bytes) (#address-cells == 2, #size-cells == 1)
mt7988a-bananapi-bpi-r4-wifi-mt7996a.dtso:95.5-28: Warning (reg_format): /fragment@3/__overlay__/pcie@0,0:reg: property has invalid length (20 bytes) (#address-cells == 2, #size-cells == 1)
mt7988a-rfb-spim-nand-factory.dtso:49.5-28: Warning (reg_format): /fragment@1/__overlay__/pcie@0,0:reg: property has invalid length (20 bytes) (#address-cells == 2, #size-cells == 1)

Signed-off-by: Shiji Yang <[email protected]>
4 weeks agomediatek: filogic: fix wm8960 dtc warnings
Shiji Yang [Sun, 18 May 2025 23:58:02 +0000 (07:58 +0800)]
mediatek: filogic: fix wm8960 dtc warnings

Add missing #address-cells, #size-cells and #sound-dai-cells to
fix the following dtc warnings:

mt7986a-bananapi-bpi-r3-respeaker-2mics.dtso:46.5-18: Warning (reg_format): /fragment@1/__overlay__/wm8960@1a:reg: property has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)
mt7986a-bananapi-bpi-r3-respeaker-2mics.dtso:29.11-31.7: Warning (sound_dai_property): /fragment@0/__overlay__/sound_wm8960/codec: Missing property '#sound-dai-cells' in node /fragment@1/__overlay__/wm8960@1a or bad phandle (referred from sound-dai[0])
mt7986a-rfb-spim-nand.dts:17.12-19.5: Warning (sound_dai_property): /sound_wm8960/platform: Missing property '#sound-dai-cells' in node /soc/audio-controller@11210000 or bad phandle (referred from sound-dai[0])
mt7986a-rfb-spim-nand.dts:21.9-23.5: Warning (sound_dai_property): /sound_wm8960/codec: Missing property '#sound-dai-cells' in node /soc/i2c@11008000/wm8960@1a or bad phandle (referred from sound-dai[0])

Signed-off-by: Shiji Yang <[email protected]>
4 weeks agomediatek: filogic: fix WiFi MAC address invalid length dtc warnings
Shiji Yang [Sun, 18 May 2025 23:46:59 +0000 (07:46 +0800)]
mediatek: filogic: fix WiFi MAC address invalid length dtc warnings

Add missing #address-cells and #size-cells to fix the
following dtc warnings:

../dts/mt7988a-smartrg-mt-stuart.dtsi:558.5-15: Warning (reg_format): /soc/pcie@11300000/pcie@0,0/mt7996@0,0/band@0:reg: property has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)
../dts/mt7988a-smartrg-mt-stuart.dtsi:565.5-15: Warning (reg_format): /soc/pcie@11300000/pcie@0,0/mt7996@0,0/band@1:reg: property has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)
../dts/mt7988a-smartrg-mt-stuart.dtsi:572.5-15: Warning (reg_format): /soc/pcie@11300000/pcie@0,0/mt7996@0,0/band@2:reg: property has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)
../dts/mt7988d-asus-zenwifi-bt8.dts:78.3-13: Warning (reg_format): /soc/pcie@11300000/pcie@0,0/mt7996@0,0/band@0:reg: property has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)
../dts/mt7988d-asus-zenwifi-bt8.dts:85.3-13: Warning (reg_format): /soc/pcie@11300000/pcie@0,0/mt7996@0,0/band@1:reg: property has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)
../dts/mt7988d-asus-zenwifi-bt8.dts:92.3-13: Warning (reg_format): /soc/pcie@11300000/pcie@0,0/mt7996@0,0/band@2:reg: property has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)
../dts/mt7988d-asus-zenwifi-bt8-ubootmod.dts:82.3-13: Warning (reg_format): /soc/pcie@11300000/pcie@0,0/mt7996@0,0/band@0:reg: property has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)
../dts/mt7988d-asus-zenwifi-bt8-ubootmod.dts:89.3-13: Warning (reg_format): /soc/pcie@11300000/pcie@0,0/mt7996@0,0/band@1:reg: property has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)
../dts/mt7988d-asus-zenwifi-bt8-ubootmod.dts:96.3-13: Warning (reg_format): /soc/pcie@11300000/pcie@0,0/mt7996@0,0/band@2:reg: property has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)
../dts/mt7981b-cmcc-a10.dtsi:250.3-13: Warning (reg_format): /soc/wifi@18000000/band@1:reg: property has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)
../dts/mt7986a-dlink-aquila-pro-ai-m60-a1.dts:324.3-13: Warning (reg_format): /soc/wifi@18000000/band@0:reg: property has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)
../dts/mt7986a-dlink-aquila-pro-ai-m60-a1.dts:330.3-13: Warning (reg_format): /soc/wifi@18000000/band@1:reg: property has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)
../dts/mt7981b-gatonetworks-gdsp.dts:247.3-13: Warning (reg_format): /soc/wifi@18000000/band@0:reg: property has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)
../dts/mt7981b-gatonetworks-gdsp.dts:253.3-13: Warning (reg_format): /soc/wifi@18000000/band@1:reg: property has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)
../dts/mt7981b-huasifei-wh3000.dts:182.3-13: Warning (reg_format): /soc/wifi@18000000/band@1:reg: property has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)
../dts/mt7986b-mercusys-mr90x-v1-ubi.dts:114.3-13: Warning (reg_format): /soc/wifi@18000000/band@0:reg: property has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)
../dts/mt7986b-mercusys-mr90x-v1-ubi.dts:120.3-13: Warning (reg_format): /soc/wifi@18000000/band@1:reg: property has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)
../dts/mt7981b-openembed-som7981.dts:287.3-13: Warning (reg_format): /soc/wifi@18000000/band@1:reg: property has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)
../dts/mt7981b-openwrt-one.dts:446.3-13: Warning (reg_format): /soc/wifi@18000000/band@0:reg: property has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)
../dts/mt7981b-openwrt-one.dts:452.3-13: Warning (reg_format): /soc/wifi@18000000/band@1:reg: property has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)
../dts/mt7981b-routerich-ax3000-v1.dts:323.3-13: Warning (reg_format): /soc/wifi@18000000/band@0:reg: property has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)
../dts/mt7981b-routerich-ax3000-v1.dts:329.3-13: Warning (reg_format): /soc/wifi@18000000/band@1:reg: property has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)

Signed-off-by: Shiji Yang <[email protected]>
4 weeks agomediatek: filogic: fix "unknown,gca230718" dtc warnings
Shiji Yang [Sun, 18 May 2025 23:43:29 +0000 (07:43 +0800)]
mediatek: filogic: fix "unknown,gca230718" dtc warnings

Add missing #address-cells and #size-cells to fix the
following dtc warnings:

../dts/mt7981b-dlink-aquila-pro-ai-m30-a1.dts:289.4-14: Warning (reg_format): /soc/i2c@11007000/gca230718@40/led@0:reg: property has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)
../dts/mt7981b-dlink-aquila-pro-ai-m30-a1.dts:295.4-14: Warning (reg_format): /soc/i2c@11007000/gca230718@40/led@1:reg: property has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)
../dts/mt7981b-dlink-aquila-pro-ai-m30-a1.dts:301.4-14: Warning (reg_format): /soc/i2c@11007000/gca230718@40/led@2:reg: property has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)
../dts/mt7981b-dlink-aquila-pro-ai-m30-a1.dts:307.4-14: Warning (reg_format): /soc/i2c@11007000/gca230718@40/led@3:reg: property has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)
../dts/mt7986a-dlink-aquila-pro-ai-m60-a1.dts:356.4-14: Warning (reg_format): /soc/i2c@11008000/gca230718@40/led@0:reg: property has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)
../dts/mt7986a-dlink-aquila-pro-ai-m60-a1.dts:362.4-14: Warning (reg_format): /soc/i2c@11008000/gca230718@40/led@1:reg: property has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)
../dts/mt7986a-dlink-aquila-pro-ai-m60-a1.dts:368.4-14: Warning (reg_format): /soc/i2c@11008000/gca230718@40/led@2:reg: property has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)
../dts/mt7986a-dlink-aquila-pro-ai-m60-a1.dts:374.4-14: Warning (reg_format): /soc/i2c@11008000/gca230718@40/led@3:reg: property has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)

Signed-off-by: Shiji Yang <[email protected]>
4 weeks agomediatek: filogic: fix memory node invalid length dtc warnings
Shiji Yang [Sun, 18 May 2025 23:36:51 +0000 (07:36 +0800)]
mediatek: filogic: fix memory node invalid length dtc warnings

Correct the dts memory reg property to fix the following dtc
warnings:

../dts/mt7986a-zyxel-ex5601-t0-stock.dts:19.3-33: Warning (reg_format): /memory@40000000:reg: property has invalid length (8 bytes) (#address-cells == 2, #size-cells == 2)
../dts/mt7986a-zyxel-ex5601-t0-ubootmod.dts:19.3-33: Warning (reg_format): /memory@40000000:reg: property has invalid length (8 bytes) (#address-cells == 2, #size-cells == 2)

Signed-off-by: Shiji Yang <[email protected]>
4 weeks agomediatek: filogic: fix unit name leading 0s dtc warnings
Shiji Yang [Sun, 18 May 2025 23:30:58 +0000 (07:30 +0800)]
mediatek: filogic: fix unit name leading 0s dtc warnings

Trim unnecessary 0s to fix the following dtc warnings:

../dts/mt7981b-cudy-re3000-v1.dts:135.20-139.6: Warning (unit_address_format): /soc/spi@11009000/flash@0/partitions/partition@00000: unit name should not have leading 0s
../dts/mt7981b-cudy-wr3000-v1.dts:153.20-157.6: Warning (unit_address_format): /soc/spi@11009000/flash@0/partitions/partition@00000: unit name should not have leading 0s
../dts/mt7981b-gatonetworks-gdsp.dts:276.20-280.6: Warning (unit_address_format): /soc/spi@11009000/flash@0/partitions/partition@00000: unit name should not have leading 0s
mt7988a-rfb-spim-nor.dtso:36.21-39.7: Warning (unit_address_format): /fragment@0/__overlay__/flash@0/partition@00000: unit name should not have leading 0s
../dts/mt7981a-ubnt-unifi-6-plus.dts:113.28-131.6: Warning (unit_address_format): /soc/spi@11009000/flash@0/partitions/partition@00000: unit name should not have leading 0s
../dts/mt7981b-wavlink-wl-wn586x3.dts:147.20-151.6: Warning (unit_address_format): /soc/spi@11009000/flash@0/partitions/partition@00000: unit name should not have leading 0s
../dts/mt7981b-wavlink-wl-wn573hx3.dts:102.20-106.6: Warning (unit_address_format): /soc/spi@11009000/flash@0/partitions/partition@00000: unit name should not have leading 0s
../dts/mt7981b-yuncore-ax835.dts:161.20-165.6: Warning (unit_address_format): /soc/spi@11009000/flash@0/partitions/partition@00000: unit name should not have leading 0s
../dts/mt7986a-zyxel-ex5601-t0-stock.dts:57.39-61.6: Warning (unit_address_format): /soc/spi@1100a000/spi_nand@0/partitions/partition@180000/nvmem-layout/macaddr@0004: unit name should not have leading 0s
../dts/mt7986a-zyxel-ex5601-t0-stock.dts:63.39-67.6: Warning (unit_address_format): /soc/spi@1100a000/spi_nand@0/partitions/partition@180000/nvmem-layout/macaddr@0024: unit name should not have leading 0s
../dts/mt7986a-zyxel-ex5601-t0-stock.dts:69.39-73.6: Warning (unit_address_format): /soc/spi@1100a000/spi_nand@0/partitions/partition@180000/nvmem-layout/macaddr@002a: unit name should not have leading 0s
../dts/mt7986a-zyxel-ex5601-t0-ubootmod.dts:56.39-60.6: Warning (unit_address_format): /soc/spi@1100a000/spi_nand@0/partitions/partition@180000/nvmem-layout/macaddr@0004: unit name should not have leading 0s
../dts/mt7986a-zyxel-ex5601-t0-ubootmod.dts:62.39-66.6: Warning (unit_address_format): /soc/spi@1100a000/spi_nand@0/partitions/partition@180000/nvmem-layout/macaddr@0024: unit name should not have leading 0s
../dts/mt7986a-zyxel-ex5601-t0-ubootmod.dts:68.39-72.6: Warning (unit_address_format): /soc/spi@1100a000/spi_nand@0/partitions/partition@180000/nvmem-layout/macaddr@002a: unit name should not have leading 0s

Signed-off-by: Shiji Yang <[email protected]>
4 weeks agomediatek: filogic: fix flash node name dtc warnings
Shiji Yang [Sun, 18 May 2025 23:25:27 +0000 (07:25 +0800)]
mediatek: filogic: fix flash node name dtc warnings

Correct dts node name based on reg property to fix the
following dtc warnings:

mt7981-rfb-spim-nand.dtso:20.25-67.6: Warning (spi_bus_reg): /fragment@1/__overlay__/spi_nand@0: SPI bus unit address format error, expected "1"
mt7986a-rfb-spim-nand.dts:41.23-76.4: Warning (spi_bus_reg): /soc/spi@1100a000/spi_nand@0: SPI bus unit address format error, expected "1"
../dts/mt7981a-comfast-cf-e393ax.dts:135.23-206.4: Warning (spi_bus_reg): /soc/spi@1100a000/spi_nand@0: SPI bus unit address format error, expected "1"
../dts/mt7981b-openwrt-one.dts:305.10-342.4: Warning (spi_bus_reg): /soc/spi@1100a000/flash@0: SPI bus unit address format error, expected "1"
../dts/mt7986a-zyxel-ex5601-t0-common.dtsi:166.30-180.4: Warning (spi_bus_reg): /soc/spi@1100a000/spi_nand@0: SPI bus unit address format error, expected "1"

Signed-off-by: Shiji Yang <[email protected]>
4 weeks agomediatek: filogic: fix mmc dtc warnings
Shiji Yang [Sun, 18 May 2025 23:18:13 +0000 (07:18 +0800)]
mediatek: filogic: fix mmc dtc warnings

Add missing #address-cells and #size-cells to fix the
following dtc warnings:

../dts/mt7986a-smartrg-bonanza-peak.dtsi:310.3-13: Warning (reg_format): /soc/mmc@11230000/card@0:reg: property has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)
mt7986a-bananapi-bpi-r3-emmc.dtso:29.5-15: Warning (reg_format): /fragment@0/__overlay__/card@0:reg: property has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)
mt7986a-bananapi-bpi-r3-sd.dtso:23.5-15: Warning (reg_format): /fragment@0/__overlay__/card@0:reg: property has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)
../dts/mt7986a-bananapi-bpi-r3-mini.dts:274.3-13: Warning (reg_format): /soc/mmc@11230000/card@0:reg: property has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)
../dts/mt7981b-cmcc-rax3000m-emmc.dtso:48.5-15: Warning (reg_format): /fragment@3/__overlay__/card@0:reg: property has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)
../dts/mt7981b-glinet-gl-mt2500.dts:158.3-13: Warning (reg_format): /soc/mmc@11230000/card@0:reg: property has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)
../dts/mt7986a-glinet-gl-mt6000.dts:319.3-13: Warning (reg_format): /soc/mmc@11230000/card@0:reg: property has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)
../dts/mt7981a-glinet-gl-x3000-xe3000-common.dtsi:142.3-13: Warning (reg_format): /soc/mmc@11230000/card@0:reg: property has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)
../dts/mt7981b-huasifei-wh3000.dts:118.3-13: Warning (reg_format): /soc/mmc@11230000/card@0:reg: property has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)
../dts/mt7986a-jdcloud-re-cp-03.dts:171.3-13: Warning (reg_format): /soc/mmc@11230000/card@0:reg: property has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)
../dts/mt7981b-nradio-c8-668gl.dts:110.3-13: Warning (reg_format): /soc/mmc@11230000/card@0:reg: property has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)
../dts/mt7981b-unielec-u7981-01-emmc.dts:26.3-13: Warning (reg_format): /soc/mmc@11230000/card@0:reg: property has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)

Signed-off-by: Shiji Yang <[email protected]>
4 weeks agomediatek: filogic: fix "srg,sysled" dtc warnings
Shiji Yang [Sun, 18 May 2025 22:53:31 +0000 (06:53 +0800)]
mediatek: filogic: fix "srg,sysled" dtc warnings

Add missing #address-cells and #size-cells to fix the
following dtc warnings:

../dts/mt7986a-smartrg-bonanza-peak.dtsi:562.4-14: Warning (reg_format): /soc/i2c@11008000/system-leds/led@1:reg: property has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)
../dts/mt7986a-smartrg-bonanza-peak.dtsi:568.4-14: Warning (reg_format): /soc/i2c@11008000/system-leds/led@2:reg: property has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)
../dts/mt7986a-smartrg-bonanza-peak.dtsi:574.4-14: Warning (reg_format): /soc/i2c@11008000/system-leds/led@3:reg: property has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)
../dts/mt7986a-smartrg-bonanza-peak.dtsi:580.4-14: Warning (reg_format): /soc/i2c@11008000/system-leds/led@4:reg: property has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)
../dts/mt7988a-smartrg-mt-stuart.dtsi:394.4-14: Warning (reg_format): /soc/i2c@11004000/system-leds/system_red:reg: property has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)
../dts/mt7988a-smartrg-mt-stuart.dtsi:399.4-14: Warning (reg_format): /soc/i2c@11004000/system-leds/system_green:reg: property has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)
../dts/mt7988a-smartrg-mt-stuart.dtsi:404.4-14: Warning (reg_format): /soc/i2c@11004000/system-leds/system_blue:reg: property has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)
../dts/mt7988a-smartrg-mt-stuart.dtsi:409.4-14: Warning (reg_format): /soc/i2c@11004000/system-leds/system_white:reg: property has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)
../dts/mt7986a-smartrg-bonanza-peak.dtsi:559.14-588.4: Warning (i2c_bus_reg): /soc/i2c@11008000/system-leds: I2C bus unit address format error, expected "30"
../dts/mt7988a-smartrg-mt-stuart.dtsi:388.14-413.4: Warning (i2c_bus_reg): /soc/i2c@11004000/system-leds: I2C bus unit address format error, expected "30"

Signed-off-by: Shiji Yang <[email protected]>
4 weeks agokernel: modules: define fb-io-fops module
Mieczyslaw Nalewaj [Sun, 18 May 2025 10:17:30 +0000 (12:17 +0200)]
kernel: modules: define fb-io-fops module

Define define fb-io-fops module - Fbdev helpers for framebuffers in I/O memory
By creating a hidden module it is possible to load fb_io_fops.ko
according to the kernel version.

Fixes: 5048c9d ("kernel: modules: adjust the object files of kmod-fb ")
Package kmod-drm-radeon is missing dependencies for the following libraries:
fb_io_fops.ko
make[2]: *** [modules/video.mk:620: /__w/openwrt/openwrt/openwrt/bin/targets/x86/geode/packages/kmod-drm-radeon-6.12.28-r1.apk] Error 1
time: package/kernel/linux/compile#45.35#40.01#75.34

Signed-off-by: Mieczyslaw Nalewaj <[email protected]>
Link: https://github.com/openwrt/openwrt/pull/18771
Signed-off-by: Robert Marko <[email protected]>
4 weeks agotreewide: dts: trim "#size-cells" from "gpio-export" node
Shiji Yang [Sun, 30 Mar 2025 02:06:06 +0000 (10:06 +0800)]
treewide: dts: trim "#size-cells" from "gpio-export" node

The "gpio-export" driver doesn't require a "reg" property in the
device tree, hence we don't need to use the "#size-cells" property
to describe the size of "reg".

Signed-off-by: Shiji Yang <[email protected]>
Link: https://github.com/openwrt/openwrt/pull/18290
Signed-off-by: Robert Marko <[email protected]>
OSZAR »