Re: Matter integration

2023-07-27 Thread Dave Taht 
So wonderful to see matter begin to matter!

https://forum.openwrt.org/t/cerowrt-ii-would-anyone-care/110554

regrettably I am mostly retired from openwrt now and do not understand
the workflow.

On Thu, Jul 27, 2023 at 2:14 PM Karsten Sperling via openwrt-devel
 wrote:
>
> The sender domain has a DMARC Reject/Quarantine policy which disallows
> sending mailing list messages using the original "From" header.
>
> To mitigate this problem, the original message has been wrapped
> automatically by the mailing list software.
>
>
> -- Forwarded message --
> From: Karsten Sperling 
> To: openwrt-devel@lists.openwrt.org
> Cc:
> Bcc:
> Date: Fri, 28 Jul 2023 09:11:10 +1200
> Subject: Matter integration
> Hello,
>
> I’m part of an effort by the Connectivity Standards Alliance to bring support 
> for routers and access points into Matter.  Matter is an open-source 
> connectivity standard built to enable developers and device manufacturers to 
> build reliable and secure connected home devices [1][2].
>
> In this context we’re working on a reference implementation for 
> Matter-enabled routers / access points, which will be taking the form of an 
> OpenWRT feed.  Development on this has recently started at 
> https://github.com/project-chip/matter-openwrt.  We’re using OpenWRT as a 
> platform because of its open nature and great hardware support.  I wanted to 
> reach out to make the OpenWRT developer community aware of this effort, and 
> to invite you to collaborate with us if you’re interested.
>
> On a more concrete level, I would also like to ask for support for this small 
> PR on OpenWRT I’ve opened here: https://github.com/openwrt/openwrt/pull/13000
>
> The cross-platform nature of the Matter SDK combined with the fact that it 
> uses git sub-modules for dependency management results in the repo having a 
> LOT of sub-modules (about 70 direct, 130 total), only 4 of which are needed 
> when building within OpenWRT. Getting this PR merged would help us to get the 
> Matter SDK and related software to build cleanly under OpenWRT.
>
> Thanks!
>
> [1] https://buildwithmatter.com 
> [2] https://github.com/project-chip/connectedhomeip
>
>
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/mailman/listinfo/openwrt-devel



-- 
Podcast: https://www.youtube.com/watch?v=bxmoBr4cBKg
Dave Täht CSO, LibreQos

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Matter integration

2023-07-27 Thread Karsten Sperling via openwrt-devel 
The sender domain has a DMARC Reject/Quarantine policy which disallows
sending mailing list messages using the original "From" header.

To mitigate this problem, the original message has been wrapped
automatically by the mailing list software.--- Begin Message ---
Hello,

I’m part of an effort by the Connectivity Standards Alliance to bring support 
for routers and access points into Matter.  Matter is an open-source 
connectivity standard built to enable developers and device manufacturers to 
build reliable and secure connected home devices [1][2].

In this context we’re working on a reference implementation for Matter-enabled 
routers / access points, which will be taking the form of an OpenWRT feed.  
Development on this has recently started at 
https://github.com/project-chip/matter-openwrt.  We’re using OpenWRT as a 
platform because of its open nature and great hardware support.  I wanted to 
reach out to make the OpenWRT developer community aware of this effort, and to 
invite you to collaborate with us if you’re interested.

On a more concrete level, I would also like to ask for support for this small 
PR on OpenWRT I’ve opened here: https://github.com/openwrt/openwrt/pull/13000

The cross-platform nature of the Matter SDK combined with the fact that it uses 
git sub-modules for dependency management results in the repo having a LOT of 
sub-modules (about 70 direct, 130 total), only 4 of which are needed when 
building within OpenWRT. Getting this PR merged would help us to get the Matter 
SDK and related software to build cleanly under OpenWRT.

Thanks!

[1] https://buildwithmatter.com 
[2] https://github.com/project-chip/connectedhomeip


--- End Message ---
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

[PATCH 3/4] tegra: initial kernel 6.1 support

2023-07-27 Thread Tomasz Maciej Nowak 
From: Tomasz Maciej Nowak 

- refresh patches
- adjust kernel config, with main change enabling VIDEO_TEGRA_VDE,
  necessary for driving power domain responsible for clean reboot
- adjust LED patch to changes in LED drivers

Signed-off-by: Tomasz Maciej Nowak 
---
 package/kernel/linux/modules/video.mk |  4 +-
 target/linux/tegra/Makefile   |  1 +
 target/linux/tegra/config-6.1 | 77 +--
 ...interrupts-due-to-tegra2-silicon-bug.patch |  2 +-
 ...enable-front-panel-leds-in-TrimSlice.patch | 22 --
 5 files changed, 90 insertions(+), 16 deletions(-)

diff --git a/package/kernel/linux/modules/video.mk 
b/package/kernel/linux/modules/video.mk
index e8a2d479ee03..b0f5c027ed60 100644
--- a/package/kernel/linux/modules/video.mk
+++ b/package/kernel/linux/modules/video.mk
@@ -1058,7 +1058,7 @@ define KernelPackage/video-mem2mem
   SUBMENU:=$(VIDEO_MENU)
   TITLE:=Memory 2 Memory device support
   HIDDEN:=1
-  DEPENDS:=+kmod-video-videobuf2
+  DEPENDS:=@!TARGET_tegra +kmod-video-videobuf2
   KCONFIG:= CONFIG_V4L_MEM2MEM_DRIVERS=y
   FILES:= $(LINUX_DIR)/drivers/media/$(V4L2_DIR)/v4l2-mem2mem.ko
   AUTOLOAD:=$(call AutoLoad,66,v4l2-mem2mem)
@@ -1075,7 +1075,7 @@ define KernelPackage/video-dma
   SUBMENU:=$(VIDEO_MENU)
   TITLE:=Video DMA support
   HIDDEN:=1
-  DEPENDS:=+kmod-video-videobuf2
+  DEPENDS:=@!TARGET_tegra +kmod-video-videobuf2
   KCONFIG:= \
CONFIG_VIDEOBUF2_DMA_CONTIG \
CONFIG_VIDEOBUF2_DMA_SG
diff --git a/target/linux/tegra/Makefile b/target/linux/tegra/Makefile
index 43ca154e8a08..95d62cf6b0f5 100644
--- a/target/linux/tegra/Makefile
+++ b/target/linux/tegra/Makefile
@@ -13,6 +13,7 @@ CPU_SUBTYPE := vfpv3-d16
 SUBTARGETS := generic
 
 KERNEL_PATCHVER := 5.15
+KERNEL_TESTING_PATCHVER := 6.1
 
 include $(INCLUDE_DIR)/target.mk
 
diff --git a/target/linux/tegra/config-6.1 b/target/linux/tegra/config-6.1
index 257ffda252ad..1f244916 100644
--- a/target/linux/tegra/config-6.1
+++ b/target/linux/tegra/config-6.1
@@ -23,12 +23,11 @@ CONFIG_ARCH_TEGRA_2x_SOC=y
 CONFIG_ARM=y
 CONFIG_ARM_AMBA=y
 CONFIG_ARM_CPU_SUSPEND=y
-CONFIG_ARM_CRYPTO=y
 CONFIG_ARM_ERRATA_720789=y
 CONFIG_ARM_ERRATA_754327=y
 CONFIG_ARM_ERRATA_764369=y
 CONFIG_ARM_GIC=y
-CONFIG_ARM_HAS_SG_CHAIN=y
+CONFIG_ARM_HAS_GROUP_RELOCS=y
 CONFIG_ARM_HEAVY_MB=y
 CONFIG_ARM_L1_CACHE_SHIFT=6
 CONFIG_ARM_L1_CACHE_SHIFT_6=y
@@ -55,6 +54,8 @@ CONFIG_BLK_MQ_PCI=y
 CONFIG_BLK_PM=y
 CONFIG_BOUNCE=y
 CONFIG_CACHE_L2X0=y
+CONFIG_CC_HAVE_STACKPROTECTOR_TLS=y
+CONFIG_CC_IMPLICIT_FALLTHROUGH="-Wimplicit-fallthrough=5"
 CONFIG_CLKSRC_MMIO=y
 CONFIG_CLONE_BACKWARDS=y
 CONFIG_CLZ_TAB=y
@@ -70,7 +71,10 @@ CONFIG_CMA_SIZE_SEL_MBYTES=y
 # CONFIG_CMA_SIZE_SEL_PERCENTAGE is not set
 # CONFIG_CMA_SYSFS is not set
 CONFIG_COMMON_CLK=y
+CONFIG_COMPACT_UNEVICTABLE_DEFAULT=1
 CONFIG_COMPAT_32BIT_TIME=y
+CONFIG_CONTEXT_TRACKING=y
+CONFIG_CONTEXT_TRACKING_IDLE=y
 CONFIG_CONTIG_ALLOC=y
 CONFIG_CPUFREQ_DT=y
 CONFIG_CPUFREQ_DT_PLATDEV=y
@@ -97,6 +101,7 @@ CONFIG_CPU_FREQ_GOV_USERSPACE=y
 CONFIG_CPU_HAS_ASID=y
 CONFIG_CPU_IDLE=y
 CONFIG_CPU_IDLE_GOV_LADDER=y
+CONFIG_CPU_LITTLE_ENDIAN=y
 CONFIG_CPU_PABRT_V7=y
 CONFIG_CPU_PM=y
 CONFIG_CPU_RMAP=y
@@ -120,7 +125,9 @@ CONFIG_CRYPTO_ECHAINIV=y
 CONFIG_CRYPTO_HMAC=y
 CONFIG_CRYPTO_JITTERENTROPY=y
 CONFIG_CRYPTO_LIB_BLAKE2S_GENERIC=y
+CONFIG_CRYPTO_LIB_SHA1=y
 CONFIG_CRYPTO_LIB_SHA256=y
+CONFIG_CRYPTO_LIB_UTILS=y
 CONFIG_CRYPTO_LZ4=y
 CONFIG_CRYPTO_LZ4HC=y
 CONFIG_CRYPTO_LZO=y
@@ -137,30 +144,37 @@ CONFIG_CRYPTO_SHA512=y
 CONFIG_CRYPTO_SHA512_ARM=y
 CONFIG_CRYPTO_TWOFISH=y
 CONFIG_CRYPTO_TWOFISH_COMMON=y
+CONFIG_CURRENT_POINTER_IN_TPIDRURO=y
 CONFIG_DCACHE_WORD_ACCESS=y
+CONFIG_DDR=y
 CONFIG_DEBUG_ALIGN_RODATA=y
+CONFIG_DEBUG_INFO=y
 CONFIG_DEBUG_LL_INCLUDE="mach/debug-macro.S"
 # CONFIG_DEVFREQ_GOV_PASSIVE is not set
 # CONFIG_DEVFREQ_GOV_PERFORMANCE is not set
 # CONFIG_DEVFREQ_GOV_POWERSAVE is not set
 CONFIG_DEVFREQ_GOV_SIMPLE_ONDEMAND=y
 # CONFIG_DEVFREQ_GOV_USERSPACE is not set
-CONFIG_DEVFREQ_THERMAL=y
+# CONFIG_DEVFREQ_THERMAL is not set
 # CONFIG_DEVPORT is not set
 CONFIG_DMADEVICES=y
 CONFIG_DMA_CMA=y
 CONFIG_DMA_ENGINE=y
 CONFIG_DMA_OF=y
 CONFIG_DMA_OPS=y
-CONFIG_DMA_REMAP=y
 CONFIG_DMA_SHARED_BUFFER=y
 CONFIG_DNOTIFY=y
 CONFIG_DRM=y
 CONFIG_DRM_BRIDGE=y
+CONFIG_DRM_DISPLAY_DP_HELPER=y
+CONFIG_DRM_DISPLAY_HDMI_HELPER=y
+CONFIG_DRM_DISPLAY_HELPER=y
+CONFIG_DRM_DP_AUX_BUS=y
 CONFIG_DRM_FBDEV_EMULATION=y
 CONFIG_DRM_FBDEV_OVERALLOC=100
 CONFIG_DRM_KMS_HELPER=y
 CONFIG_DRM_MIPI_DSI=y
+CONFIG_DRM_NOMODESET=y
 CONFIG_DRM_PANEL=y
 CONFIG_DRM_PANEL_BRIDGE=y
 CONFIG_DRM_PANEL_ORIENTATION_QUIRKS=y
@@ -170,6 +184,7 @@ CONFIG_DRM_TEGRA=y
 CONFIG_DTC=y
 CONFIG_EDAC_ATOMIC_SCRUB=y
 CONFIG_EDAC_SUPPORT=y
+CONFIG_EXCLUSIVE_SYSTEM_RAM=y
 CONFIG_EXT4_FS=y
 CONFIG_EXTCON=y
 CONFIG_F2FS_FS=y
@@ -187,6 +202,7 @@ CONFIG_FIX_EARLYCON_MEM=y
 CONFIG_FS_IOMAP=y
 CONFIG_FS_MBCACHE=y
 CONFIG_FW_LOADER_PAGED_BUF=y
+CONFIG_FW_LOADER_SYSFS=y
 CONFIG_GENERIC_ALLOCATOR=y

[PATCH 4/4] tegra: switch to 6.1 kernel

2023-07-27 Thread Tomasz Maciej Nowak 
From: Tomasz Maciej Nowak 

Testing results were all good, so move target to newer kernel by default.

Signed-off-by: Tomasz Maciej Nowak 
---
 target/linux/tegra/Makefile | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/target/linux/tegra/Makefile b/target/linux/tegra/Makefile
index 95d62cf6b0f5..f289c09c05c0 100644
--- a/target/linux/tegra/Makefile
+++ b/target/linux/tegra/Makefile
@@ -12,7 +12,7 @@ CPU_TYPE := cortex-a9
 CPU_SUBTYPE := vfpv3-d16
 SUBTARGETS := generic
 
-KERNEL_PATCHVER := 5.15
+KERNEL_PATCHVER := 6.1
 KERNEL_TESTING_PATCHVER := 6.1
 
 include $(INCLUDE_DIR)/target.mk
-- 
2.41.0


___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

[PATCH 2/4] tegra: copy patches and config for kernel 6.1

2023-07-27 Thread Tomasz Maciej Nowak 
From: Tomasz Maciej Nowak 

Prepare for addition of kernel 6.1 support.

Signed-off-by: Tomasz Maciej Nowak 
---
 target/linux/tegra/config-6.1 | 504 ++
 ...interrupts-due-to-tegra2-silicon-bug.patch |  77 +++
 ...enable-front-panel-leds-in-TrimSlice.patch |  46 ++
 3 files changed, 627 insertions(+)
 create mode 100644 target/linux/tegra/config-6.1
 create mode 100644 
target/linux/tegra/patches-6.1/100-serial8250-on-tegra-hsuart-recover-from-spurious-interrupts-due-to-tegra2-silicon-bug.patch
 create mode 100644 
target/linux/tegra/patches-6.1/101-ARM-dtc-tegra-enable-front-panel-leds-in-TrimSlice.patch

diff --git a/target/linux/tegra/config-6.1 b/target/linux/tegra/config-6.1
new file mode 100644
index ..257ffda252ad
--- /dev/null
+++ b/target/linux/tegra/config-6.1
@@ -0,0 +1,504 @@
+CONFIG_AC97_BUS=y
+# CONFIG_AHCI_TEGRA is not set
+CONFIG_ALIGNMENT_TRAP=y
+CONFIG_ARCH_32BIT_OFF_T=y
+CONFIG_ARCH_HIBERNATION_POSSIBLE=y
+CONFIG_ARCH_KEEP_MEMBLOCK=y
+CONFIG_ARCH_MIGHT_HAVE_PC_PARPORT=y
+CONFIG_ARCH_MULTIPLATFORM=y
+CONFIG_ARCH_MULTI_V6_V7=y
+CONFIG_ARCH_MULTI_V7=y
+CONFIG_ARCH_NEEDS_CPU_IDLE_COUPLED=y
+CONFIG_ARCH_NR_GPIO=1024
+CONFIG_ARCH_OPTIONAL_KERNEL_RWX=y
+CONFIG_ARCH_OPTIONAL_KERNEL_RWX_DEFAULT=y
+CONFIG_ARCH_SELECT_MEMORY_MODEL=y
+CONFIG_ARCH_SPARSEMEM_ENABLE=y
+CONFIG_ARCH_SUSPEND_POSSIBLE=y
+CONFIG_ARCH_TEGRA=y
+# CONFIG_ARCH_TEGRA_114_SOC is not set
+# CONFIG_ARCH_TEGRA_124_SOC is not set
+CONFIG_ARCH_TEGRA_2x_SOC=y
+# CONFIG_ARCH_TEGRA_3x_SOC is not set
+CONFIG_ARM=y
+CONFIG_ARM_AMBA=y
+CONFIG_ARM_CPU_SUSPEND=y
+CONFIG_ARM_CRYPTO=y
+CONFIG_ARM_ERRATA_720789=y
+CONFIG_ARM_ERRATA_754327=y
+CONFIG_ARM_ERRATA_764369=y
+CONFIG_ARM_GIC=y
+CONFIG_ARM_HAS_SG_CHAIN=y
+CONFIG_ARM_HEAVY_MB=y
+CONFIG_ARM_L1_CACHE_SHIFT=6
+CONFIG_ARM_L1_CACHE_SHIFT_6=y
+CONFIG_ARM_PATCH_IDIV=y
+CONFIG_ARM_PATCH_PHYS_VIRT=y
+# CONFIG_ARM_PL172_MPMC is not set
+# CONFIG_ARM_SMMU is not set
+# CONFIG_ARM_TEGRA124_CPUFREQ is not set
+CONFIG_ARM_TEGRA20_CPUFREQ=y
+CONFIG_ARM_TEGRA_CPUIDLE=y
+CONFIG_ARM_THUMB=y
+CONFIG_ARM_THUMBEE=y
+CONFIG_ARM_UNWIND=y
+CONFIG_ARM_VIRT_EXT=y
+CONFIG_ASN1=y
+CONFIG_ATA=y
+CONFIG_ATAGS=y
+CONFIG_AUTO_ZRELADDR=y
+CONFIG_BINFMT_FLAT_ARGVP_ENVP_ON_STACK=y
+CONFIG_BLK_DEV_BSG=y
+CONFIG_BLK_DEV_BSG_COMMON=y
+CONFIG_BLK_DEV_LOOP=y
+CONFIG_BLK_MQ_PCI=y
+CONFIG_BLK_PM=y
+CONFIG_BOUNCE=y
+CONFIG_CACHE_L2X0=y
+CONFIG_CLKSRC_MMIO=y
+CONFIG_CLONE_BACKWARDS=y
+CONFIG_CLZ_TAB=y
+CONFIG_CMA=y
+CONFIG_CMA_ALIGNMENT=8
+CONFIG_CMA_AREAS=7
+# CONFIG_CMA_DEBUG is not set
+# CONFIG_CMA_DEBUGFS is not set
+CONFIG_CMA_SIZE_MBYTES=16
+# CONFIG_CMA_SIZE_SEL_MAX is not set
+CONFIG_CMA_SIZE_SEL_MBYTES=y
+# CONFIG_CMA_SIZE_SEL_MIN is not set
+# CONFIG_CMA_SIZE_SEL_PERCENTAGE is not set
+# CONFIG_CMA_SYSFS is not set
+CONFIG_COMMON_CLK=y
+CONFIG_COMPAT_32BIT_TIME=y
+CONFIG_CONTIG_ALLOC=y
+CONFIG_CPUFREQ_DT=y
+CONFIG_CPUFREQ_DT_PLATDEV=y
+CONFIG_CPU_32v6K=y
+CONFIG_CPU_32v7=y
+CONFIG_CPU_ABRT_EV7=y
+CONFIG_CPU_CACHE_V7=y
+CONFIG_CPU_CACHE_VIPT=y
+CONFIG_CPU_COPY_V6=y
+CONFIG_CPU_CP15=y
+CONFIG_CPU_CP15_MMU=y
+CONFIG_CPU_FREQ=y
+CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=y
+# CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set
+CONFIG_CPU_FREQ_GOV_ATTR_SET=y
+CONFIG_CPU_FREQ_GOV_COMMON=y
+CONFIG_CPU_FREQ_GOV_CONSERVATIVE=y
+CONFIG_CPU_FREQ_GOV_ONDEMAND=y
+CONFIG_CPU_FREQ_GOV_PERFORMANCE=y
+CONFIG_CPU_FREQ_GOV_POWERSAVE=y
+CONFIG_CPU_FREQ_GOV_SCHEDUTIL=y
+CONFIG_CPU_FREQ_GOV_USERSPACE=y
+# CONFIG_CPU_FREQ_STAT is not set
+CONFIG_CPU_HAS_ASID=y
+CONFIG_CPU_IDLE=y
+CONFIG_CPU_IDLE_GOV_LADDER=y
+CONFIG_CPU_PABRT_V7=y
+CONFIG_CPU_PM=y
+CONFIG_CPU_RMAP=y
+CONFIG_CPU_SPECTRE=y
+CONFIG_CPU_THUMB_CAPABLE=y
+CONFIG_CPU_TLB_V7=y
+CONFIG_CPU_V7=y
+CONFIG_CRC16=y
+# CONFIG_CRC32_SARWATE is not set
+CONFIG_CRC32_SLICEBY8=y
+CONFIG_CROSS_MEMORY_ATTACH=y
+CONFIG_CRYPTO_AES_ARM=y
+CONFIG_CRYPTO_CRC32=y
+CONFIG_CRYPTO_CRC32C=y
+CONFIG_CRYPTO_CRYPTD=y
+CONFIG_CRYPTO_DEFLATE=y
+CONFIG_CRYPTO_DRBG=y
+CONFIG_CRYPTO_DRBG_HMAC=y
+CONFIG_CRYPTO_DRBG_MENU=y
+CONFIG_CRYPTO_ECHAINIV=y
+CONFIG_CRYPTO_HMAC=y
+CONFIG_CRYPTO_JITTERENTROPY=y
+CONFIG_CRYPTO_LIB_BLAKE2S_GENERIC=y
+CONFIG_CRYPTO_LIB_SHA256=y
+CONFIG_CRYPTO_LZ4=y
+CONFIG_CRYPTO_LZ4HC=y
+CONFIG_CRYPTO_LZO=y
+CONFIG_CRYPTO_RNG=y
+CONFIG_CRYPTO_RNG2=y
+CONFIG_CRYPTO_RNG_DEFAULT=y
+CONFIG_CRYPTO_RSA=y
+CONFIG_CRYPTO_SEQIV=y
+CONFIG_CRYPTO_SHA1=y
+CONFIG_CRYPTO_SHA1_ARM=y
+CONFIG_CRYPTO_SHA256=y
+CONFIG_CRYPTO_SHA256_ARM=y
+CONFIG_CRYPTO_SHA512=y
+CONFIG_CRYPTO_SHA512_ARM=y
+CONFIG_CRYPTO_TWOFISH=y
+CONFIG_CRYPTO_TWOFISH_COMMON=y
+CONFIG_DCACHE_WORD_ACCESS=y
+CONFIG_DEBUG_ALIGN_RODATA=y
+CONFIG_DEBUG_LL_INCLUDE="mach/debug-macro.S"
+# CONFIG_DEVFREQ_GOV_PASSIVE is not set
+# CONFIG_DEVFREQ_GOV_PERFORMANCE is not set
+# CONFIG_DEVFREQ_GOV_POWERSAVE is not set
+CONFIG_DEVFREQ_GOV_SIMPLE_ONDEMAND=y
+# CONFIG_DEVFREQ_GOV_USERSPACE is not set
+CONFIG_DEVFREQ_THERMAL=y
+# CONFIG_DEVPORT is not set
+CONFIG_DMADEVICES=y
+CONFIG_DMA_CMA=y
+CONFIG_DMA_ENGINE=y

[PATCH 0/4] tegra: bump to 6.1

2023-07-27 Thread Tomasz Maciej Nowak 
From: Tomasz Maciej Nowak 

Straightforward update and small generic config modification.

Tomasz Maciej Nowak (4):
  kernel: 6.1: move NO_ARRAY_BOUNDS to generic
  tegra: copy patches and config for kernel 6.1
  tegra: initial kernel 6.1 support
  tegra: switch to 6.1 kernel

 package/kernel/linux/modules/video.mk |   4 +-
 target/linux/bcm27xx/bcm2708/config-6.1   |   2 -
 target/linux/bcm27xx/bcm2709/config-6.1   |   2 -
 target/linux/bcm27xx/bcm2710/config-6.1   |   2 -
 target/linux/bcm27xx/bcm2711/config-6.1   |   2 -
 target/linux/bmips/bcm6318/config-6.1 |   2 -
 target/linux/bmips/bcm63268/config-6.1|   2 -
 target/linux/bmips/bcm6328/config-6.1 |   2 -
 target/linux/bmips/bcm6358/config-6.1 |   2 -
 target/linux/bmips/bcm6362/config-6.1 |   2 -
 target/linux/bmips/bcm6368/config-6.1 |   2 -
 target/linux/generic/config-6.1   |   2 +
 target/linux/mediatek/filogic/config-6.1  |   2 -
 target/linux/mediatek/mt7622/config-6.1   |   2 -
 target/linux/mediatek/mt7623/config-6.1   |   2 -
 target/linux/mediatek/mt7629/config-6.1   |   2 -
 target/linux/qualcommax/config-6.1|   2 -
 target/linux/rockchip/armv8/config-6.1|   2 -
 target/linux/tegra/Makefile   |   3 +-
 target/linux/tegra/config-6.1 | 565 ++
 ...interrupts-due-to-tegra2-silicon-bug.patch |  77 +++
 ...enable-front-panel-leds-in-TrimSlice.patch |  58 ++
 target/linux/uml/config-6.1   |   1 -
 23 files changed, 706 insertions(+), 36 deletions(-)
 create mode 100644 target/linux/tegra/config-6.1
 create mode 100644 
target/linux/tegra/patches-6.1/100-serial8250-on-tegra-hsuart-recover-from-spurious-interrupts-due-to-tegra2-silicon-bug.patch
 create mode 100644 
target/linux/tegra/patches-6.1/101-ARM-dtc-tegra-enable-front-panel-leds-in-TrimSlice.patch

-- 
2.41.0


___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

[PATCH 1/4] kernel: 6.1: move NO_ARRAY_BOUNDS to generic

2023-07-27 Thread Tomasz Maciej Nowak 
From: Tomasz Maciej Nowak 

Array bounds are disabled for GCC 11 or later. It's better to track it in
global (generic) config.

Signed-off-by: Tomasz Maciej Nowak 
---
 target/linux/bcm27xx/bcm2708/config-6.1  | 2 --
 target/linux/bcm27xx/bcm2709/config-6.1  | 2 --
 target/linux/bcm27xx/bcm2710/config-6.1  | 2 --
 target/linux/bcm27xx/bcm2711/config-6.1  | 2 --
 target/linux/bmips/bcm6318/config-6.1| 2 --
 target/linux/bmips/bcm63268/config-6.1   | 2 --
 target/linux/bmips/bcm6328/config-6.1| 2 --
 target/linux/bmips/bcm6358/config-6.1| 2 --
 target/linux/bmips/bcm6362/config-6.1| 2 --
 target/linux/bmips/bcm6368/config-6.1| 2 --
 target/linux/generic/config-6.1  | 2 ++
 target/linux/mediatek/filogic/config-6.1 | 2 --
 target/linux/mediatek/mt7622/config-6.1  | 2 --
 target/linux/mediatek/mt7623/config-6.1  | 2 --
 target/linux/mediatek/mt7629/config-6.1  | 2 --
 target/linux/qualcommax/config-6.1   | 2 --
 target/linux/rockchip/armv8/config-6.1   | 2 --
 target/linux/uml/config-6.1  | 1 -
 18 files changed, 2 insertions(+), 33 deletions(-)

diff --git a/target/linux/bcm27xx/bcm2708/config-6.1 
b/target/linux/bcm27xx/bcm2708/config-6.1
index c5d604e6bc25..29884c661305 100644
--- a/target/linux/bcm27xx/bcm2708/config-6.1
+++ b/target/linux/bcm27xx/bcm2708/config-6.1
@@ -56,7 +56,6 @@ CONFIG_BRCM_CHAR_DRIVERS=y
 # CONFIG_CACHE_L2X0 is not set
 CONFIG_CC_HAVE_STACKPROTECTOR_TLS=y
 CONFIG_CC_IMPLICIT_FALLTHROUGH="-Wimplicit-fallthrough=5"
-CONFIG_CC_NO_ARRAY_BOUNDS=y
 CONFIG_CLKSRC_MMIO=y
 CONFIG_CLK_BCM2711_DVP=y
 CONFIG_CLK_BCM2835=y
@@ -170,7 +169,6 @@ CONFIG_FWNODE_MDIO=y
 CONFIG_FW_CACHE=y
 CONFIG_FW_LOADER_PAGED_BUF=y
 CONFIG_FW_LOADER_SYSFS=y
-CONFIG_GCC11_NO_ARRAY_BOUNDS=y
 CONFIG_GENERIC_ALLOCATOR=y
 CONFIG_GENERIC_BUG=y
 CONFIG_GENERIC_CLOCKEVENTS=y
diff --git a/target/linux/bcm27xx/bcm2709/config-6.1 
b/target/linux/bcm27xx/bcm2709/config-6.1
index ec2e7f3fa610..7479ee37a31f 100644
--- a/target/linux/bcm27xx/bcm2709/config-6.1
+++ b/target/linux/bcm27xx/bcm2709/config-6.1
@@ -70,7 +70,6 @@ CONFIG_BROADCOM_PHY=y
 # CONFIG_CACHE_L2X0 is not set
 CONFIG_CC_HAVE_STACKPROTECTOR_TLS=y
 CONFIG_CC_IMPLICIT_FALLTHROUGH="-Wimplicit-fallthrough=5"
-CONFIG_CC_NO_ARRAY_BOUNDS=y
 CONFIG_CLKSRC_MMIO=y
 CONFIG_CLK_BCM2711_DVP=y
 CONFIG_CLK_BCM2835=y
@@ -207,7 +206,6 @@ CONFIG_FWNODE_MDIO=y
 CONFIG_FW_CACHE=y
 CONFIG_FW_LOADER_PAGED_BUF=y
 CONFIG_FW_LOADER_SYSFS=y
-CONFIG_GCC11_NO_ARRAY_BOUNDS=y
 CONFIG_GENERIC_ALLOCATOR=y
 CONFIG_GENERIC_ARCH_TOPOLOGY=y
 CONFIG_GENERIC_BUG=y
diff --git a/target/linux/bcm27xx/bcm2710/config-6.1 
b/target/linux/bcm27xx/bcm2710/config-6.1
index b0abd49c7f12..f0af261f1691 100644
--- a/target/linux/bcm27xx/bcm2710/config-6.1
+++ b/target/linux/bcm27xx/bcm2710/config-6.1
@@ -87,7 +87,6 @@ CONFIG_CAVIUM_ERRATUM_27456=y
 CONFIG_CC_HAVE_SHADOW_CALL_STACK=y
 CONFIG_CC_HAVE_STACKPROTECTOR_SYSREG=y
 CONFIG_CC_IMPLICIT_FALLTHROUGH="-Wimplicit-fallthrough=5"
-CONFIG_CC_NO_ARRAY_BOUNDS=y
 CONFIG_CLKSRC_MMIO=y
 CONFIG_CLK_BCM2711_DVP=y
 CONFIG_CLK_BCM2835=y
@@ -217,7 +216,6 @@ CONFIG_FWNODE_MDIO=y
 CONFIG_FW_CACHE=y
 CONFIG_FW_LOADER_PAGED_BUF=y
 CONFIG_FW_LOADER_SYSFS=y
-CONFIG_GCC11_NO_ARRAY_BOUNDS=y
 CONFIG_GCC_SUPPORTS_DYNAMIC_FTRACE_WITH_REGS=y
 CONFIG_GENERIC_ALLOCATOR=y
 CONFIG_GENERIC_ARCH_TOPOLOGY=y
diff --git a/target/linux/bcm27xx/bcm2711/config-6.1 
b/target/linux/bcm27xx/bcm2711/config-6.1
index ff88926e3df5..f44019cee3f1 100644
--- a/target/linux/bcm27xx/bcm2711/config-6.1
+++ b/target/linux/bcm27xx/bcm2711/config-6.1
@@ -91,7 +91,6 @@ CONFIG_CAVIUM_ERRATUM_27456=y
 CONFIG_CC_HAVE_SHADOW_CALL_STACK=y
 CONFIG_CC_HAVE_STACKPROTECTOR_SYSREG=y
 CONFIG_CC_IMPLICIT_FALLTHROUGH="-Wimplicit-fallthrough=5"
-CONFIG_CC_NO_ARRAY_BOUNDS=y
 CONFIG_CLKSRC_MMIO=y
 CONFIG_CLK_BCM2711_DVP=y
 CONFIG_CLK_BCM2835=y
@@ -222,7 +221,6 @@ CONFIG_FWNODE_MDIO=y
 CONFIG_FW_CACHE=y
 CONFIG_FW_LOADER_PAGED_BUF=y
 CONFIG_FW_LOADER_SYSFS=y
-CONFIG_GCC11_NO_ARRAY_BOUNDS=y
 CONFIG_GCC_SUPPORTS_DYNAMIC_FTRACE_WITH_REGS=y
 CONFIG_GENERIC_ALLOCATOR=y
 CONFIG_GENERIC_ARCH_TOPOLOGY=y
diff --git a/target/linux/bmips/bcm6318/config-6.1 
b/target/linux/bmips/bcm6318/config-6.1
index 526319da33d8..9837bc74458e 100644
--- a/target/linux/bmips/bcm6318/config-6.1
+++ b/target/linux/bmips/bcm6318/config-6.1
@@ -18,7 +18,6 @@ CONFIG_BLK_MQ_PCI=y
 CONFIG_BLK_PM=y
 CONFIG_BMIPS_GENERIC=y
 CONFIG_CC_IMPLICIT_FALLTHROUGH="-Wimplicit-fallthrough=5"
-CONFIG_CC_NO_ARRAY_BOUNDS=y
 CONFIG_CEVT_R4K=y
 # CONFIG_CLK_BCM63268_TIMER is not set
 CONFIG_CLK_BCM_63XX_GATE=y
@@ -82,7 +81,6 @@ CONFIG_FWNODE_MDIO=y
 CONFIG_FW_CFE=y
 CONFIG_FW_LOADER_PAGED_BUF=y
 CONFIG_FW_LOADER_SYSFS=y
-CONFIG_GCC11_NO_ARRAY_BOUNDS=y
 CONFIG_GENERIC_ATOMIC64=y
 CONFIG_GENERIC_CLOCKEVENTS=y
 CONFIG_GENERIC_CMOS_UPDATE=y
diff --git a/target/linux/bmips/bcm63268/config-6.1 
b/target/linux/bmips/bcm63268/config-6.1
index 624c00556db9..534307bd3222 100644
--- a/target/linux/bmips/bcm63268/config-6.1
+++

Re: kernel-headers: platform/target patches are not applied

2023-07-27 Thread Felix Fietkau 

Hi Martin,

On 27.07.23 13:23, Martin Schiller wrote:

When preparing the kernel sources to build the kernel headers, currently
only the patches from the generic folder are applied, but not from the
actual selected target.

This is basically understandable if one assumes that one wants to use a
toolchain for different targets with the same architecture.

But if a target has a kernel patch which also changes the uapi, then
this is not considered in the toolchain/kernel-headers and thus when
compiling Userspace applications at the moment.

This is currently already the case for the following targets:
* ath79
* bcm27xx
* bcm63xx
* ipq40xx
* lantiq
* realtek

I am currently working on a new target, have now stumbled across this
problem and would now like to start a discussion here on how best to
solve this now.

I am looking forward to your ideas.


Packages that depend on target specific UAPI changes can always include 
kernel.mk in the package Makefile, make themselves non-shared and pull 
include files from $(LINUX_DIR)/user_headers


The default for all other packages should be to not rely on target 
specific UAPI changes.


- Felix

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

[PATCH v4 3/3] ipq40xx: pakedge_wr-1: workaround for kernel bigger than 4MiB

2023-07-27 Thread Tomasz Maciej Nowak 
From: Tomasz Maciej Nowak 

Alter booting command in U-Boot on first boot after upgrade to workaround
the kernel size limitation. The kernel size read from flash will be 8MiB,
which should suffice for forseable future. As precaution a warning
interupting upgrade is emited, explaining what to do.

Signed-off-by: Tomasz Maciej Nowak 
---
 .../etc/uci-defaults/05_fix-compat-version |  3 ++-
 .../base-files/lib/preinit/81_patch_uboot_env.sh   | 14 ++
 target/linux/ipq40xx/image/generic.mk  |  8 +++-
 3 files changed, 23 insertions(+), 2 deletions(-)
 create mode 100644 
target/linux/ipq40xx/base-files/lib/preinit/81_patch_uboot_env.sh

diff --git 
a/target/linux/ipq40xx/base-files/etc/uci-defaults/05_fix-compat-version 
b/target/linux/ipq40xx/base-files/etc/uci-defaults/05_fix-compat-version
index c01192089712..a3f90125c6e5 100644
--- a/target/linux/ipq40xx/base-files/etc/uci-defaults/05_fix-compat-version
+++ b/target/linux/ipq40xx/base-files/etc/uci-defaults/05_fix-compat-version
@@ -4,7 +4,8 @@ case "$(board_name)" in
 linksys,ea6350v3|\
 linksys,ea8300|\
 linksys,mr8300|\
-ezviz,cs-w3-wd1200g-eup)
+ezviz,cs-w3-wd1200g-eup|\
+pakedge,wr-1)
uci set system.@system[0].compat_version="2.0"
uci commit system
;;
diff --git a/target/linux/ipq40xx/base-files/lib/preinit/81_patch_uboot_env.sh 
b/target/linux/ipq40xx/base-files/lib/preinit/81_patch_uboot_env.sh
new file mode 100644
index ..0cc0ab0fca6f
--- /dev/null
+++ b/target/linux/ipq40xx/base-files/lib/preinit/81_patch_uboot_env.sh
@@ -0,0 +1,14 @@
+. /lib/functions.sh
+
+preinit_patch_uboot_env() {
+   case $(board_name) in
+   pakedge,wr-1)
+   if ! fw_printenv -n OpenWrt &>/dev/null; then
+   fw_setenv OpenWrt 'sf probe; sf read 0x8400 
0x18 0x80; bootm 0x8400'
+   fw_setenv bootcmd "$(fw_printenv -n bootcmd | sed -e 
's,bootipq,run OpenWrt,')"
+   fi
+   ;;
+   esac
+}
+
+boot_hook_add preinit_main preinit_patch_uboot_env
diff --git a/target/linux/ipq40xx/image/generic.mk 
b/target/linux/ipq40xx/image/generic.mk
index 13b6ce1fee41..742576a29e5e 100644
--- a/target/linux/ipq40xx/image/generic.mk
+++ b/target/linux/ipq40xx/image/generic.mk
@@ -957,8 +957,14 @@ define Device/pakedge_wr-1
SOC := qcom-ipq4018
BLOCKSIZE := 64k
IMAGE_SIZE := 31232k
-   KERNEL_SIZE := 4096k
+   KERNEL_SIZE := 8192k
IMAGE/sysupgrade.bin := append-kernel | pad-to (BLOCKSIZE) | 
append-rootfs | pad-rootfs | append-metadata
+   DEVICE_COMPAT_VERSION := 2.0
+   DEVICE_COMPAT_MESSAGE := \n$\
+   Booting command in U-Boot needs to be changed because of kernel 
\n$\
+   growing beyond 4MiB. Force upgrade to 23.05.0 first and it will 
\n$\
+   automatically amend booting command in U-Boot on first boot. 
\n$\
+   Then proceed with the upgrade to desired version.
 endef
 TARGET_DEVICES += pakedge_wr-1
 
-- 
2.41.0


___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

[PATCH v4 1/3] ipq40xx: image: limit kernel size for NOR devices

2023-07-27 Thread Tomasz Maciej Nowak 
From: Tomasz Maciej Nowak 

'bootipq' command on some devices, with kernel on NOR flash chip, read
kernel partition size from Qualcomm proprietary partition table, which
seems to be stored in MIBIB partition. The partition table can be read
by 'smeminfo' command in U-Boot command line interface. Because this
partition table is never updated on sysupgrade (even when the kernel
size changes) kernel size is capped at initial value, usually 4MiB.
Sysupgrading such kernel will soft-brick the device, which will need
serial console for recovery. Some devices already suffer from this,
beacuse its U-Boot does not allow to boot LZMA or GZIP compressed kernel
image. Even some devices allowing to boot LZMA compressed kernel will hit
this limitation later. Therefore limit the kernel size to 4MiB for
devices not having it specified, so we won't create soft-bricking images.

Signed-off-by: Tomasz Maciej Nowak 
---
 target/linux/ipq40xx/image/generic.mk | 6 ++
 1 file changed, 6 insertions(+)

diff --git a/target/linux/ipq40xx/image/generic.mk 
b/target/linux/ipq40xx/image/generic.mk
index a9dd2aa0912f..13b6ce1fee41 100644
--- a/target/linux/ipq40xx/image/generic.mk
+++ b/target/linux/ipq40xx/image/generic.mk
@@ -400,6 +400,7 @@ define Device/dlink_dap-2610
WRGG_DEVNAME := /dev/mtdblock/8
WRGG_SIGNATURE := wapac30_dkbs_dap2610
IMAGE_SIZE := 14080k
+   KERNEL_SIZE := 4096k
IMAGES += factory.bin
# Bootloader expects a special 160 byte header which is added by
# wrgg-image.
@@ -478,6 +479,7 @@ define Device/engenius_emd1
DEVICE_DTS_CONFIG := config@4
SOC := qcom-ipq4018
IMAGE_SIZE := 30720k
+   KERNEL_SIZE := 4096k
IMAGES += factory.bin
IMAGE/sysupgrade.bin := append-kernel | append-rootfs | pad-rootfs | 
append-metadata
IMAGE/factory.bin := qsdk-ipq-factory-nor | check-size
@@ -800,6 +802,7 @@ define Device/netgear_ex61x0v2
NETGEAR_BOARD_ID := EX6150v2series
NETGEAR_HW_ID := 29765285+16+0+128+2x2
IMAGE_SIZE := 14400k
+   KERNEL_SIZE := 4096k
SOC := qcom-ipq4018
 endef
 
@@ -954,6 +957,7 @@ define Device/pakedge_wr-1
SOC := qcom-ipq4018
BLOCKSIZE := 64k
IMAGE_SIZE := 31232k
+   KERNEL_SIZE := 4096k
IMAGE/sysupgrade.bin := append-kernel | pad-to (BLOCKSIZE) | 
append-rootfs | pad-rootfs | append-metadata
 endef
 TARGET_DEVICES += pakedge_wr-1
@@ -1030,6 +1034,7 @@ define Device/qxwlan_e2600ac-c1
BOARD_NAME := e2600ac-c1
SOC := qcom-ipq4019
IMAGE_SIZE := 31232k
+   KERNEL_SIZE := 4096k
IMAGE/sysupgrade.bin := append-kernel | append-rootfs | pad-rootfs | 
append-metadata
 endef
 TARGET_DEVICES += qxwlan_e2600ac-c1
@@ -1218,6 +1223,7 @@ define Device/zyxel_wre6606
DEVICE_DTS_CONFIG := config@4
SOC := qcom-ipq4018
IMAGE_SIZE := 13184k
+   KERNEL_SIZE := 4096k
IMAGE/sysupgrade.bin := append-kernel | append-rootfs | pad-rootfs | 
check-size | append-metadata
DEVICE_PACKAGES := -kmod-ath10k-ct kmod-ath10k-ct-smallbuffers
 endef
-- 
2.41.0


___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

[PATCH v4 0/3] ipq40xx: remedy potential of producing soft-bricking images

2023-07-27 Thread Tomasz Maciej Nowak 
From: Tomasz Maciej Nowak 

Some of devices having kernel on NOR flash could reach limit of kernel
partition size at 4MiB and soft-brick them. Unfortunately we don't know
if all of them are affected, thus kernel size limit is added to all of
remaining ones. Later commit allows for some devices to prepare painless
transition, while the last one shows how it can be done for device i
introduced. I tried to make transition for the device as generic as
possible so it coulld be used on others, but unfortunately I own only
one device, which means the owners of the rest device need to verify if
it works for them and add their devices.

Tomasz Maciej Nowak (3):
  ipq40xx: image: limit kernel size for NOR devices
v1 -> v2: no changes
v2 -> v3: no changes
v3 -> v4: remove Habanero board (does not have a limit),
  straighten inaccuracy in commit message (zImage is
  self-extracting which doesn't depend on U-Boot
  capabilities, while GZIPped uImage does) 
  ipq40xx: dts: allow writing to U-Boot environment
v1 -> v2: no changes
v2 -> v3: no changes
v3 -> v4: straighten inaccuracy in commit message (zImage is
  self-extracting which doesn't depend on U-Boot
  capabilities, while GZIPped uImage does)
  ipq40xx: pakedge_wr-1: workaround for kernel bigger than 4MiB
v1 -> v2: remove printing command from sed invocation which prints
  double output and breaks future 'bootcmd' modifications
v2 -> v3: shortened description of problem presented to user as
  users having firmware 23.05.0 or later won't see the
  message
v3 -> v4: no changes


Tomasz Maciej Nowak (3):
  ipq40xx: image: limit kernel size for NOR devices
  ipq40xx: dts: allow writing to U-Boot environment
  ipq40xx: pakedge_wr-1: workaround for kernel bigger than 4MiB

 .../etc/uci-defaults/05_fix-compat-version |  3 ++-
 .../base-files/lib/preinit/81_patch_uboot_env.sh   | 14 ++
 .../boot/dts/qcom-ipq4018-cs-w3-wd1200g-eup.dts|  1 -
 .../arch/arm/boot/dts/qcom-ipq4018-dap-2610.dts|  1 -
 .../arch/arm/boot/dts/qcom-ipq4018-eap1300.dts |  1 -
 .../files/arch/arm/boot/dts/qcom-ipq4018-emd1.dts  |  1 -
 .../arch/arm/boot/dts/qcom-ipq4018-emr3500.dts |  1 -
 .../arch/arm/boot/dts/qcom-ipq4018-ens620ext.dts   |  1 -
 .../arch/arm/boot/dts/qcom-ipq4018-ex61x0v2.dtsi   |  1 -
 .../files/arch/arm/boot/dts/qcom-ipq4018-wr-1.dts  |  1 -
 .../arch/arm/boot/dts/qcom-ipq4018-wre6606.dts |  1 -
 .../arch/arm/boot/dts/qcom-ipq4019-e2600ac-c1.dts  |  1 -
 .../arm/boot/dts/qcom-ipq4019-habanero-dvk.dts |  1 -
 .../arch/arm/boot/dts/qcom-ipq4019-u4019-32m.dts   |  1 -
 .../files/arch/arm/boot/dts/qcom-ipq4019-x1pro.dts |  1 -
 .../arch/arm/boot/dts/qcom-ipq4028-wpj428.dts  |  1 -
 .../arch/arm/boot/dts/qcom-ipq4029-gl-b1300.dts|  1 -
 .../arch/arm/boot/dts/qcom-ipq4029-gl-s1300.dts|  1 -
 target/linux/ipq40xx/image/generic.mk  | 12 
 19 files changed, 28 insertions(+), 17 deletions(-)
 create mode 100644 
target/linux/ipq40xx/base-files/lib/preinit/81_patch_uboot_env.sh

-- 
2.41.0


___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

[PATCH v4 2/3] ipq40xx: dts: allow writing to U-Boot environment

2023-07-27 Thread Tomasz Maciej Nowak 
From: Tomasz Maciej Nowak 

Devices allowing to boot LZMA or GZIP compressed kernel didn't hit yet
the 4MiB boundary for kernel size, thus allowing to prepare workaround
for the issue, without need for serial console attachment.
The workaround is modifying 'bootcmd' variable in U-Boot environment
which will replace 'bootipq' command with equivalent not limited by
imposed partition table.
This commit also touches devices which boot uncompressed kernel, so
even if those are already soft-bricked, it will still allow to alter
U-Boot environment from initramfs booted device.

Signed-off-by: Tomasz Maciej Nowak 
---
 .../files/arch/arm/boot/dts/qcom-ipq4018-cs-w3-wd1200g-eup.dts   | 1 -
 .../ipq40xx/files/arch/arm/boot/dts/qcom-ipq4018-dap-2610.dts| 1 -
 .../ipq40xx/files/arch/arm/boot/dts/qcom-ipq4018-eap1300.dts | 1 -
 .../linux/ipq40xx/files/arch/arm/boot/dts/qcom-ipq4018-emd1.dts  | 1 -
 .../ipq40xx/files/arch/arm/boot/dts/qcom-ipq4018-emr3500.dts | 1 -
 .../ipq40xx/files/arch/arm/boot/dts/qcom-ipq4018-ens620ext.dts   | 1 -
 .../ipq40xx/files/arch/arm/boot/dts/qcom-ipq4018-ex61x0v2.dtsi   | 1 -
 .../linux/ipq40xx/files/arch/arm/boot/dts/qcom-ipq4018-wr-1.dts  | 1 -
 .../ipq40xx/files/arch/arm/boot/dts/qcom-ipq4018-wre6606.dts | 1 -
 .../ipq40xx/files/arch/arm/boot/dts/qcom-ipq4019-e2600ac-c1.dts  | 1 -
 .../files/arch/arm/boot/dts/qcom-ipq4019-habanero-dvk.dts| 1 -
 .../ipq40xx/files/arch/arm/boot/dts/qcom-ipq4019-u4019-32m.dts   | 1 -
 .../linux/ipq40xx/files/arch/arm/boot/dts/qcom-ipq4019-x1pro.dts | 1 -
 .../ipq40xx/files/arch/arm/boot/dts/qcom-ipq4028-wpj428.dts  | 1 -
 .../ipq40xx/files/arch/arm/boot/dts/qcom-ipq4029-gl-b1300.dts| 1 -
 .../ipq40xx/files/arch/arm/boot/dts/qcom-ipq4029-gl-s1300.dts| 1 -
 16 files changed, 16 deletions(-)

diff --git 
a/target/linux/ipq40xx/files/arch/arm/boot/dts/qcom-ipq4018-cs-w3-wd1200g-eup.dts
 
b/target/linux/ipq40xx/files/arch/arm/boot/dts/qcom-ipq4018-cs-w3-wd1200g-eup.dts
index 22a48c12c44e..0772c5ac464a 100644
--- 
a/target/linux/ipq40xx/files/arch/arm/boot/dts/qcom-ipq4018-cs-w3-wd1200g-eup.dts
+++ 
b/target/linux/ipq40xx/files/arch/arm/boot/dts/qcom-ipq4018-cs-w3-wd1200g-eup.dts
@@ -185,7 +185,6 @@
partition5@E {
label = "APPSBLENV";
reg = <0x000e 0x0001>;
-   read-only;
};
 
partition6@F {
diff --git 
a/target/linux/ipq40xx/files/arch/arm/boot/dts/qcom-ipq4018-dap-2610.dts 
b/target/linux/ipq40xx/files/arch/arm/boot/dts/qcom-ipq4018-dap-2610.dts
index 493905d56d8f..dea90b13e209 100644
--- a/target/linux/ipq40xx/files/arch/arm/boot/dts/qcom-ipq4018-dap-2610.dts
+++ b/target/linux/ipq40xx/files/arch/arm/boot/dts/qcom-ipq4018-dap-2610.dts
@@ -117,7 +117,6 @@
partition@e {
label = "APPSBLENV";
reg = <0xe 0x1>;
-   read-only;
};
partition@f {
label = "APPSBL";
diff --git 
a/target/linux/ipq40xx/files/arch/arm/boot/dts/qcom-ipq4018-eap1300.dts 
b/target/linux/ipq40xx/files/arch/arm/boot/dts/qcom-ipq4018-eap1300.dts
index a8f24aa00e60..2e9cb8ecdb68 100644
--- a/target/linux/ipq40xx/files/arch/arm/boot/dts/qcom-ipq4018-eap1300.dts
+++ b/target/linux/ipq40xx/files/arch/arm/boot/dts/qcom-ipq4018-eap1300.dts
@@ -165,7 +165,6 @@
partition5@e {
label = "0:APPSBLENV";
reg = <0x000e 0x0001>;
-   read-only;
};
partition6@f {
label = "0:APPSBL";
diff --git a/target/linux/ipq40xx/files/arch/arm/boot/dts/qcom-ipq4018-emd1.dts 
b/target/linux/ipq40xx/files/arch/arm/boot/dts/qcom-ipq4018-emd1.dts
index 396595ba5185..615c6aaf678f 100644
--- a/target/linux/ipq40xx/files/arch/arm/boot/dts/qcom-ipq4018-emd1.dts
+++ b/target/linux/ipq40xx/files/arch/arm/boot/dts/qcom-ipq4018-emd1.dts
@@ -163,7 +163,6 @@
partition5@e {
label = "0:APPSBLENV";
reg = <0x000e 0x0001>;
-   read-only;
};
partition6@f {
label = "0:APPSBL";
diff --git 
a/target/linux/ipq40xx/files/arch/arm/boot/dts/qcom-ipq4018-emr3500.dts 
b/target/linux/ipq40xx/files/arch/arm/boot/dts/qcom-ipq4018-emr3500.dts
index 361614945145..8c038917b668 100644
--- a/target/linux/ipq40xx/files/arch/arm/boot/dts/qcom-ipq4018-emr3500.dts
+++ b/target/linux/ipq40xx/files/arch/arm/boot/dts/qcom-ipq4018-emr3500.dts
@@ -164,7 +164,6 @@
partition@e {

kernel-headers: platform/target patches are not applied

2023-07-27 Thread Martin Schiller 
When preparing the kernel sources to build the kernel headers, currently 
only the patches from the generic folder are applied, but not from the 
actual selected target.


This is basically understandable if one assumes that one wants to use a 
toolchain for different targets with the same architecture.


But if a target has a kernel patch which also changes the uapi, then 
this is not considered in the toolchain/kernel-headers and thus when 
compiling Userspace applications at the moment.


This is currently already the case for the following targets:
* ath79
* bcm27xx
* bcm63xx
* ipq40xx
* lantiq
* realtek

I am currently working on a new target, have now stumbled across this 
problem and would now like to start a discussion here on how best to 
solve this now.


I am looking forward to your ideas.


___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel