staging/neocturne/config, branch main

apk: limit CONFIG_IPK_FILES_CHECKSUMS config to OPKG

2024-06-20T03:52:06Z

Limit CONFIG_IPK_FILES_CHECKSUMS config to OPKG as APK have different way to validate package integrity (apk audit) Signed-off-by: Christian Marangi

Revert "apk: limit CONFIG_IPK_FILES_CHECKSUMS config to OPKG"

2024-06-20T03:52:05Z

This reverts commit 25bbefcdd9424ed1b6ef35a39e84420fc4cce322. Only the Config-build.in change needed to be merged and this contains leftover from previous revision of the feature. Signed-off-by: Christian Marangi

config: imply apk-mbedtls with USE_APK

2024-06-11T21:58:19Z

On top of the fixup to select apk-mbedtls when USE_APK is enabled from a new config, also imply the package when enabling the config to catch .config that are already init. (Having both opkg and apk installed in a system is not a problem but if USE_APK is used, APK presence in the system is mandatory) Link: https://github.com/openwrt/openwrt/pull/15543 Signed-off-by: Christian Marangi

apk: limit CONFIG_IPK_FILES_CHECKSUMS config to OPKG

2024-06-11T21:58:19Z

Limit CONFIG_IPK_FILES_CHECKSUMS config to OPKG as APK have different way to validate package integrity (apk audit) Link: https://github.com/openwrt/openwrt/pull/15543 Signed-off-by: Christian Marangi

config: kernel: remove KASAN_EXTRA

2024-06-07T10:04:04Z

The option has been removed from the kernel since 5.1. Signed-off-by: Qingfang Deng

build: add option KERNEL_DEBUG_INFO_BTF_MODULES

2024-05-31T21:50:30Z

The recent kernel v6.6.31 update broke BTF-enabled builds since upstream Linux added a prompt for config option DEBUG_INFO_BTF_MODULES in commit 2166cb2e21 ("bpf, kconfig: Fix DEBUG_INFO_BTF_MODULES Kconfig definition"). Fix by updating Config-kernel.in to add the option, cleaning up a related dependency and whitespace also. Fixes: 10d77b9bc3 ("kernel: bump 6.6 to 6.6.31") Signed-off-by: Tony Ambardar

build: add APK package build capabilities

2024-05-17T20:21:26Z

A new option called `USE_APK` is added which generated APK packages (.apk) instead of OPKG packages (.ipk). Some features like fstools `snapshot` command are not yet ported Signed-off-by: Paul Spooren

config: build: dont allow STRIP_KERNEL_EXPORTS on kernel 6.6

2024-05-16T13:12:53Z

STRIP_KERNEL_EXPORTS is currently not working on kernel 6.6 as there have been major changes in the upstream kernel. I have looked at it, and I dont think we can adapt the current patch to work so until this is fixed lets prevent STRIP_KERNEL_EXPORTS from being selected on 6.6. Link: https://github.com/openwrt/openwrt/pull/15498 Signed-off-by: Robert Marko

config: add ARM PMUv3 for kernel 6.6

2024-05-14T11:23:57Z

Kernel 6.6 has moved the ARM PMUv3 driver to drivers/perf and now once KERNEL_ARM_PMU is selected trying to build the kernel will stop with: ARM PMUv3 support (ARM_PMUV3) [N/y/?] (NEW) So, lets enable ARM_PMUV3 for ARMv7 and ARMv8 architectures if KERNEL_PERF_EVENTS is selected. Fixes: #15466 Link: https://github.com/openwrt/openwrt/pull/15469 Signed-off-by: Robert Marko

loongarch64: new target

2024-05-04T06:14:16Z

Add target for Loongson LoongArch64-based boards. LoongArch is a new RISC ISA developed by Loongson. It's a bit like MIPS or RISC-V. LoongArch includes both 32-bit and 64-bit versions (LoongArch32/LoongArch64). Loongson 3A5000 and 3A6000 are the two existing CPUs of LoongArch64 and is used for PC products. It's BIOS supports ACPI and UEFI-only boot. These CPUs supports SMP and SMT. At present only LoongArch64 is supported by linux kernel. Toolchain requirement: binutils >= 2.40 gcc >= 13.1 For details, please check the following links: https://lwn.net/Articles/861951/ https://loongson.github.io/LoongArch-Documentation/README-EN.html Signed-off-by: Weijie Gao