**** BEGIN LOGGING AT Fri Sep 21 03:00:01 2018 Sep 21 05:30:56 Linux version 4.14.71 (gcc version 7.3.0 (OpenWrt GCC 7.3.0 r8082+34-95b3f8ec8d)) #0 SMP Fri Sep 21 01:39:07 2018 SoC Type: MediaTek MT7621 ver:1 eco:3 MIPS: machine is Xiaomi Mi Router 3G Sep 21 05:31:10 yay Sep 21 12:27:32 building with gcc8 seems to be broken for bcm63xx smp Sep 21 16:46:13 Hello! Is there anyone from the system developers? Sep 21 17:00:58 Tohin: if you want to ask something, it's better to ask that instead of asking a meta question. Sep 21 18:02:36 I think I have found a mistake in the openWRT 18.01. which makes it impossible to install on the mtk 7623 chipset Sep 21 18:07:09 DonkeyHotei: yes you are right, the MIPS VDSO patch in OpenWrt should be replaced with the one from the stable kernel Sep 21 18:07:21 OpenWrt ships an older version of this patch Sep 21 18:34:36 Hauke: the patch pointed to disables vdso on mips entirely. Sep 21 18:35:24 I think the suggestion is to do this https://git.openwrt.org/?p=openwrt/staging/ldir.git;a=commitdiff;h=18ca9c1183ce73bb51c6f17480335421e0cbcdcf Sep 21 18:43:01 and now in https://patchwork.ozlabs.org/patch/973395/ Sep 21 19:48:00 ldir: yes Sep 21 19:48:13 I thought I merged an older version of this patch Sep 21 19:48:25 ldir: this looks correct Sep 21 19:50:28 I'm interested in adding support for the TP-Link Archer A7 v5. It's the same hardware as the Archer C7 v5 but it looks like the flash partitioning is different. Sep 21 19:50:42 I have some questions, but first, should I be looking at device tree or a mach file? Sep 21 19:55:02 jtf: please add it to the device tree target Sep 21 19:55:42 the mach file aproach is deprecated and we will probably remove it in some future version Sep 21 19:57:22 Hauke: sounds good, I'm new to this so I'm bound to have some silly questions Sep 21 19:57:29 is it better to ask here or on the forum? Sep 21 19:58:09 probably here or on the mailing list Sep 21 19:58:55 ah ok thanks! Sep 21 20:12:17 current popoplug-v3 /tmp/sysinfo/board_name contains "unknown" Sep 21 20:51:18 ldir: possible to backports the upstream fix to older kernels? Sep 21 20:54:54 ldir: it is already send for incusion into 4.4 and 4.9 Sep 21 20:56:13 who is taking care of the openssl 1.1 patches? Sep 21 20:56:34 I tink it looks good and also upstream openssh now supports openssl 1.1 Sep 21 20:56:43 the next release should be shipped with it Sep 21 20:57:14 the author of the pull request really spend a lot of effort to get it in Sep 21 20:57:38 Hauke: I've been testing the 1.0 support for months, and 1.1 for weeks. It seems ready Sep 21 20:59:32 One thing I've been meaning to test is the crypto support. mvebu has a crypto engine that I believe can be leveraged by OpenSSL. It currently sits at 0 interrupts though Sep 21 21:13:48 have there been any updates on the ubifs problem? Sep 21 21:15:29 wasn't it fixed by reverting that patch? Sep 21 21:15:40 don't operate on deleted inodes oe Sep 21 21:15:41 one* Sep 21 21:16:04 idk because i don't have any devices that use ubifs Sep 21 21:16:15 oh Sep 21 21:16:15 :D Sep 21 21:16:32 that's why i'm asking Sep 21 21:16:42 otherwise i'd just check Sep 21 21:18:25 [OpenWrt-Devel] UBIFS issues within kernel 4.14.69? Sep 21 21:18:26 on the list Sep 21 21:18:43 it seemed like the ubifs bug was the big blocker for 18.06.2 Sep 21 21:18:45 doesn't look like its i master yet though Sep 21 21:18:48 in Sep 21 21:18:59 unless my quick log grepping is off Sep 21 21:19:58 i lied Sep 21 21:19:59 Added new patch: Sep 21 21:19:59 - 192-Revert-ubifs-xattr-Don-t-operate-on-deleted-inodes.patch Sep 21 21:20:05 0cda4af005f22f3e9a18a1760d8482be1a45e02a Sep 21 21:21:15 someone else spotted the issue before I bumped my ubifs devices, haven't had chance to test since that went in Sep 22 00:11:36 sooo `ipfs repo gc` doesnt seem to release any space.. Sep 22 02:30:27 huh, my glib2 fix seems to have fixed parallel builds for me Sep 22 02:30:30 sweet **** ENDING LOGGING AT Sat Sep 22 03:00:00 2018