openwrt/upstream - upstream openwrt

	Commit message (Collapse)	Author	Age	Files	Lines
*	generic: enable CONFIG_ARM_CRYPTO for 32bit arm targets	Lu jicong	2023-05-10	1	-0/+1
\| \| \| \| \| \| \|	Fix following error when building 32bit arm targets with kmod-crypto-sha512 ERROR: module '/home/user/openwrt/build_dir/target-arm_xscale_musl_eabi/linux-kirkwood_generic/linux-5.15.109/arch/arm/crypto/sha512-arm.ko' is missing. Signed-off-by: Lu jicong <jiconglu58@gmail.com>
*	generic: refresh 5.15 kernel config	Lu jicong	2023-05-10	1	-5/+1
\| \| \| \| \| \|	prepare for enabling CONFIG_ARM_CRYPTO on these targets Signed-off-by: Lu jicong <jiconglu58@gmail.com>
*	kernel: improve handling of CONFIG_IO_URING	Tony Ambardar	2023-05-03	1	-1/+0
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	Kernel setting CONFIG_IO_URING supports high-performance I/O for file access and servers, generally for more performant platforms, and adds ~45 KB to kernel sizes. The need for this on less "beefy" devices is questionable, as is the size cost considering many platforms have kernel size limits which require tricky repartitioning if outgrown. The size cost is also large relative to the ~180 KB bump expected between major OpenWRT kernel releases. No OpenWrt packages have hard dependencies on this; samba4 and mariadb can take advantage if available (+KERNEL_IO_URING:liburing) but otherwise build and work fine. Since CONFIG_IO_URING is already managed via the KERNEL_IO_URING setting in Config-kernel.in (default Y), remove it from those target configs which unconditionally enable it, and update the defaults to enable it conditionally only on more powerful 64-bit x86 and arm devices. It may still be manually enabled as needed for high-performance custom builds. Signed-off-by: Tony Ambardar <itugrok@yahoo.com>
*	kernel: mtd: backport SafeLoader parser	Rafał Miłecki	2022-10-19	1	-0/+1
\| \| \| \|	Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
*	bcm53xx: 5.15: add missing LEDS_BCM63138 config symbol	Petr Štetiar	2022-08-25	1	-0/+1
\| \| \| \| \| \| \| \| \|	Fixes following build issue found during build testing with 5.15.63 kernel: LED Support for Broadcom BCM63138 SoC (LEDS_BCM63138) [N/m/y/?] (NEW) Signed-off-by: Petr Štetiar <ynezz@true.cz>
*	kernel: Activate CONFIG_GPIOLIB in generic configuration	Hauke Mehrtens	2022-08-10	1	-1/+0
\| \| \| \| \| \| \| \|	All targets expect the malta target already activate the CONFIG_GPIOLIB option. Move it to generic kernel configuration and also activate it for malta. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
*	generic: enable CRYPTO_LIB_BLAKE2S[_X86\|_ARM]	Tomasz Maciej Nowak	2022-06-24	1	-0/+2
\| \| \| \| \| \| \| \| \| \| \| \|	This is now built-in, enable so it won't propagate on target configs. Link: https://lkml.org/lkml/2022/1/3/168 Fixes: 79e7a2552e89 ("kernel: bump 5.15 to 5.15.44") Fixes: 0ca93670693b ("kernel: bump 5.10 to 5.10.119") Signed-off-by: Tomasz Maciej Nowak <tmn505@gmail.com> (Link to Kernel's commit taht made it built-in, CRYPTO_LIB_BLAKE2S[_ARM\|_X86] as it's selectable, 5.10 backport) Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
*	config: limit CONFIG_DEBUG_INFO to top-level generic configs	Tony Ambardar	2022-05-18	1	-1/+0
\| \| \| \| \| \| \| \| \| \|	Remove redundant target-level entries, noting that these settings will be configured from "Kernel build options" of Kconfig. Signed-off-by: Tony Ambardar <itugrok@yahoo.com> Signed-off-by: Felix Fietkau <nbd@nbd.name> [remove from new configs introduced after patch submission] Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
*	bcm53xx: refresh kernel 5.15 config	Rafał Miłecki	2022-04-08	1	-2/+14
\| \| \| \|	Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
*	bcm53xx: prepare kernel 5.15 support	Rafał Miłecki	2022-03-30	1	-0/+307
	Tested on Luxul XWR-3150 (boot, NAND, PCIe, switch, Ethernet). Signed-off-by: Rafał Miłecki <rafal@milecki.pl>