[OpenWrt-Devel] [PATCHv2] mdadm: revised mdadm config & init logic

2019-08-16 Thread Rosen Penev
From: Joseph Tingiris This is a significant revision of /etc/init.d/mdadm. It adds new features, support for new configuration options, safer error handling, (configurable) verbose output, and contains multiple bug fixes. Most notably, mdadm was being started with the --config flag and that pre

[OpenWrt-Devel] Cannot compile cryptodev-linux using x86-64 SDK

2019-08-16 Thread Jeffery To
Hi, As the subject of this email says, I get an error when trying to compile cryptodev-linux using the x86-64 SDK. (Though a different error than the one I found with the armvirt-64 SDK.) This error has been happening for a while, at least a month. (I haven't had time to follow up until now.) I s

Re: [OpenWrt-Devel] [PATCH procd] system: support passing "options" to the "sysupgrade" ubus method

2019-08-16 Thread John Crispin
On 16/08/2019 18:17, Bjørn Mork wrote: John Crispin writes: + for (c = name + strlen(prefix); *c; c++) { + *c = toupper(*c); + } + and, matter of tatse, but i'd drop the travolta brackets on single line clauses I thought <> were "travolta br

Re: [OpenWrt-Devel] [PATCH procd] system: support passing "options" to the "sysupgrade" ubus method

2019-08-16 Thread Bjørn Mork
John Crispin writes: >> +for (c = name + strlen(prefix); *c; c++) { >> +*c = toupper(*c); >> +} >> + > > and, matter of tatse, but i'd drop the travolta brackets on single > line clauses I thought <> were "travolta brackets", ref http://www.morethings.

[OpenWrt-Devel] [PATCH procd V2] system: support passing "options" to the "sysupgrade" ubus method

2019-08-16 Thread Rafał Miłecki
From: Rafał Miłecki Object passed as "options" gets translated into environment variables UPGRADE_OPT_*. E.g. "options": { "foo": 5 } will result in setting UPGRADE_OPT_FOO=5. This allows stage2 sysupgrade to get options explicitly. So far it was guessing what to do by checking for existence of

[OpenWrt-Devel] [PATCH 2/2] treewide: sysupgrade: pass "save_partitions" option to the "sysupgrade" method

2019-08-16 Thread Rafał Miłecki
From: Rafał Miłecki This explicitly lets stage2 know if partitions should be preserved. No more "touch /tmp/sysupgrade.always.overwrite.bootdisk.partmap" hack. Signed-off-by: Rafał Miłecki --- package/base-files/files/lib/upgrade/stage2 | 5 - package/base-files/files/sbin/sys

[OpenWrt-Devel] [PATCH 1/2] base-files: pass "save_config" option to the "sysupgrade" method

2019-08-16 Thread Rafał Miłecki
From: Rafał Miłecki This explicitly lets stage2 know if config should be preserved. Signed-off-by: Rafał Miłecki --- package/base-files/files/lib/upgrade/common.sh | 2 +- package/base-files/files/lib/upgrade/do_stage2 | 2 +- package/base-files/files/lib/upgrade/stage2| 2 -- package/base

Re: [OpenWrt-Devel] [PATCH procd] system: support passing "options" to the "sysupgrade" ubus method

2019-08-16 Thread John Crispin
On 16/08/2019 16:28, Rafał Miłecki wrote: From: Rafał Miłecki Object passed as "options" gets translated into environment variables UPGRADE_OPT_*. E.g. "options": { "foo": 5 } will result in setting UPGRADE_OPT_FOO=5. This allows stage2 sysupgrade to get options explicitly. So far it was gues

[OpenWrt-Devel] [PATCH procd] system: support passing "options" to the "sysupgrade" ubus method

2019-08-16 Thread Rafał Miłecki
From: Rafał Miłecki Object passed as "options" gets translated into environment variables UPGRADE_OPT_*. E.g. "options": { "foo": 5 } will result in setting UPGRADE_OPT_FOO=5. This allows stage2 sysupgrade to get options explicitly. So far it was guessing what to do by checking for existence of

[OpenWrt-Devel] [PATCH] ramips: remove RAM size from device name for UniElec devices

2019-08-16 Thread Adrian Schmutzler
UniElec devices are the last ones in ramips target still having the RAM size in device name although RAM size is auto-detected. Remove this from device name, compatible, etc., as it's not required and might be misleading to users and developers adding device support copying those devices. Signed-

[OpenWrt-Devel] [PATCH] ar71xx: ag71xx: add missing register writes

2019-08-16 Thread Koen Vandeputte
These are added in ath79, but were not backported here Signed-off-by: Koen Vandeputte --- .../files/drivers/net/ethernet/atheros/ag71xx/ag71xx_main.c | 5 + 1 file changed, 5 insertions(+) diff --git a/target/linux/ar71xx/files/drivers/net/ethernet/atheros/ag71xx/ag71xx_main.c b/target/l

Re: [OpenWrt-Devel] ath9k: fix dynack in IBSS mode

2019-08-16 Thread Koen Vandeputte
Hi Joe, Lorenzo, I deployed an ath9k auto distance solution in April that is working for the AREDN community http://www.arednmesh.org . https://github.com/aredn/aredn_ar71xx/blob/develop/patches/712-auto-distance-settings.patch Summary of solution: * no dependency on wpa_supplicant * init

Re: [OpenWrt-Devel] ath9k: mtd-cal-data vs firmware bin file

2019-08-16 Thread Michal Cieslakiewicz
Hello Martin, Thank you (and Dmitry Tunin and Chuanhong Guo) for explaining this topic to me. Now it is perfectly clear. So the idea of reading mtd isn't completely abandoned, Martin's approach just seems to be more flexible and universal. On the other hand, I've never assumed sparing this 4k (eve