**** BEGIN LOGGING AT Mon Feb 11 03:00:11 2019 Feb 11 05:55:25 Hauke: i rest my case Feb 11 08:17:13 ynezz: regarding TX fail on ar71xx: No warnings. it just stops passing packets Feb 11 08:38:58 xback: hm, then it's very likely, that you've probably hit some other issue Feb 11 09:28:56 ldir: jow: https://pastebin.com/DNvUdNZ8 to work around the dnsmasq pre-release version problem (won't fix retroactively, but future test/rcs would then order test < rc < release) Feb 11 09:40:26 stintel: so there are Qt packages for OpenWrt? Feb 11 09:42:30 KanjiMonster: looks good. and provides a way to handle other packages that might name tarballs inconveniently. Feb 11 09:43:03 ynezz: there's an outdated Makefile somewhere. I modified it a bit, and have something working. thinking to redo it from scratch though, too much I didn't like Feb 11 09:44:20 KanjiMonster: I think jow is away/busy at the moment. Feb 11 09:45:05 stintel: nice! Feb 11 09:45:14 ldir: KanjiMonster: 30|12:08:40< jow> ah good. I'll be more or less completely offline from feb 18th to march 4th Feb 11 09:45:27 ynezz: you have interest in qt for openwrt ? Feb 11 09:45:47 stintel: ah, so in theory he's not gone......yet ;-) Feb 11 09:46:00 ;-) Feb 11 09:47:43 stintel: Yes, I've it on my long todo list, so I'm certainly interested Feb 11 09:53:38 ynezz: good to know, I'll throw something in https://github.com/stintel/lede-wip when I have something that is clean enough to my liking Feb 11 10:05:48 now I have to figure out how to calibrate the touchscreen Feb 11 10:05:53 oh well, that's for after work Feb 11 12:34:37 stintel: did you use the video feed as a starting point for qt? mirko added qt support there and I used this once for a comercial project Feb 11 12:35:15 ah no, I used something I found in a forum post Feb 11 12:35:31 well fsck me Feb 11 12:35:52 ynezz: https://github.com/openwrt/video/tree/master/frameworks Feb 11 12:36:39 probably better to start from there Feb 11 13:21:07 stintel: ah, great, thanks! Feb 11 13:45:10 it seems 4-addr mode is disabled in 4.19 and higher kernels, anyone have a work-around or fix for this? Feb 11 13:48:45 any idea if this can run openwrt easily? https://wikidevi.com/wiki/Google_Home_Mini_(H0A) Feb 11 13:49:25 could be useful for tts for some home automation stuff Feb 11 13:52:23 greearb: I think there is a bug with 4addr mode + ath19k in 4.19 Feb 11 13:53:11 there was a bug in my wave2 FW, but I fixed that. 4addr still broken in 'trunk' evidently, but now it is not a firmware problem. Feb 11 13:53:24 greearb: see https://github.com/openwrt/openwrt/pull/1640 Feb 11 13:54:25 is that in openwrt currently? Feb 11 13:55:33 greearb: I think not yet, will try to take care of this in the next few days Feb 11 13:56:05 there is some other change in ath10k related to 4addr mode, I think it is some other problem: https://git.kernel.org/linus/68c295f21abc192163c416b333aca7c41a195075 Feb 11 14:00:38 I could probably hack that support into my firmware, but it seems it will still mostly function w/out the firmware fix. Feb 11 14:20:16 heh, found this gem in iperf3 comment: * For hysterical raisins, we only emit one JSON Feb 11 14:30:41 nom raisins Feb 11 14:39:50 Mmmm, hysterical raisins. Feb 11 15:23:00 hi Feb 11 15:26:19 Bah, I should have trusted my instinct and enabled the WDT *before* those last changes! Feb 11 17:54:32 ynezz: found a nice clue: https://pastebin.com/JUxyW5KQ Feb 11 17:55:08 sometimes the devices wrongly sets itself as 1Gbit iso 100Mbit/s Feb 11 17:55:29 the hardware is only capable of 100mbit/s max Feb 11 18:27:51 nice, free speedup Feb 11 18:34:42 xback: ping Feb 11 20:24:11 i've noticed some, what seem like startup problems on firstboot, on a few wndr3800 with recent master branch. either both radios don't start or a device hanging off a LAN port isn't reachable, a reboot seems to fix it. Feb 11 20:48:08 russell--: Have you seen 0c24b363a6 Feb 11 20:48:25 ha cutn'paste fail Feb 11 20:48:27 https://github.com/openwrt/openwrt/pull/1627 Feb 11 20:58:34 xback: btw, what device is that exactly? Feb 11 22:42:38 does ath79 still have issues with USB2? Feb 11 22:50:57 What kind of issues? Archer C7v2 still needs a hub for an ancient USB device, but seems to work otherwise Feb 11 22:52:01 jeffsf: last I remember it was stuck at USB 1.1 speeds Feb 11 22:52:05 no idea if fixed. Feb 11 22:54:34 Anyone know where the DT documentation for a bridge node within a qcom,pcie node residces? Feb 11 22:54:43 https://github.com/torvalds/linux/blob/master/Documentation/devicetree/bindings/pci/qcom%2Cpcie.txt doesn't give me any hints **** BEGIN LOGGING AT Mon Feb 11 23:39:46 2019 Feb 11 23:51:29 Does a QCA PCI wifi chip showing up as an Ethernet controller ring a bell for anyone? Feb 11 23:51:48 On OEM: 01:00.0 Class 0280: 168c:0056 ath_ol_pci Feb 11 23:52:09 On OpenWrt WIP (QCA4109): 01:00.0 Ethernet controller [0200]: Qualcomm Atheros Device [168c:abcd] (rev 01) Feb 11 23:52:44 Archer C7v2 picks it up as 00:00.0 Network controller [0280]: Qualcomm Atheros QCA986x/988x 802.11ac Wireless Network Adapter [168c:003c] Feb 11 23:53:14 (where "it" is a QCA wireless on PCI) Feb 12 00:48:07 gch981213: any negatives to increasing SPI frequency? Also, any insight into why mt7621 seems to peak at 80MHz? Feb 12 00:49:30 Client chips might not support higher speeds Feb 12 00:50:23 jeffsf: full context: http://lists.infradead.org/pipermail/openwrt-devel/2019-February/015755.html Feb 12 00:50:26 Or craptastic board design... Feb 12 01:02:04 wonder if i can do the same to my c7 v2... Feb 12 01:03:01 25MHz looks to be set as some kind of default Feb 12 01:05:32 (Found missing GPIO -- 01:00.0 Network controller [0280]: Qualcomm Atheros Device [168c:0056]) **** BEGIN LOGGING AT Tue Feb 12 02:23:30 2019 Feb 12 02:33:14 mangix: no idea about mt7621 though. I only used 40MHz on that controller and never tried higher clock. **** ENDING LOGGING AT Tue Feb 12 02:59:59 2019