[OpenWrt-Devel] New ath10k-ct firmware and driver available

Here are recent release notes: wave-1: * April 2, 2019: Support some get/set API for eeprom rate power tables. Mostly backported from 10.2 * April 2, 2019: Support adaptive-CCA, backported from 10.2 * April 3, 2019: Support adding eeprom configAddr pairs via

[OpenWrt-Devel] [PATCH RESEND V3 1/2] base-files: improve lib/upgrade/common.sh

Recently, upgrade device autodetection has been added to the mvebu target. This exposes some shortcomings of the generic export_bootdevice function, e.g. on the Turris Omnia: export_bootdevice silently reports the root partition to be the boot device. This makes the sysupgrade process fail at sever

[OpenWrt-Devel] [PATCH RESEND V3 2/2] mvebu: fix board_name condition in 79_move_config

The correct board_name for the Turris Omnia is armada-385-turris-omnia. Fixes: 4e8345ff68 ("mvebu: base-files: autodetect upgrade device") Signed-off-by: Klaus Kudielka --- target/linux/mvebu/base-files/lib/preinit/79_move_config | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

Re: [OpenWrt-Devel] [PATCH v2] lantiq: image: build initramfs only for FRITZ7362SL

Op maandag 6 mei 2019 om 12:13 schreef Petr Štetiar : Commit "lantiq/xrx200: enable initramfs images" enabled creation of initramfs images for all devices in lantiq's xrx200 subtarget, just because FRITZ7362SL needs initramfs during OpenWrt instalation. Then David Bauer informed me, that FRIT