**** BEGIN LOGGING AT Tue Aug 20 03:01:37 2019 Aug 20 06:09:56 skrzyp: because the intersection of people used to these clis, developing on openwrt and having time and motiviation to work on such a feature is close to zero Aug 20 06:13:43 it only takes one Aug 20 06:15:15 the odd thing is that there was an add-on available for sveasoft back in the day that did something similar and usually worked out of the box on whiterussian and early kamikaze too Aug 20 06:15:45 the name escapes me atm Aug 20 06:21:01 ah, it was called fwbuilder Aug 20 06:22:19 https://sourceforge.net/projects/fwbuilder/ Aug 20 09:31:12 skrzyp: also, not that this is necessarily bad, but it tends to only work well when you stick to just doing the networking configurations. Aug 20 09:31:37 when you look at the _other_ stuff that people put ontheir openwrt boxes, being just a small linux machine, it becomes rather limiting rather quickly, IMO. Aug 20 10:17:56 karlp: of course I know, but I'm just counting in the things that have UCI interface Aug 20 10:18:57 and I don't want to make a closed shell with that - for other things, people could just jump onto regular bash/ash like JunOS does - but for network-specific configuration it might be a pleasing esperience Aug 20 10:20:22 jow: I'm planning to write it on my own, just looking for the interest and researching for now. I'm still unsure which programming language should I choose to not bring any additional runtimes onto constrained OpenWRT environment and keep resource usage at minimum, yet still let people extend it for their own needs Aug 20 10:23:44 I like the idea Aug 20 10:43:48 doesn't pfsense have some limited shell thing? Aug 20 10:45:46 skrzyp: you could also ask for interest on the forum and on the ML. if there is enough interest you could even consider a crowdfunding? Aug 20 11:05:33 Linux v5.4 seems to be the next LT release. https://www.kernel.org/category/releases.html Aug 20 13:43:27 lets bump! :p Aug 20 13:44:12 the v5.4 kernel predictions: merge window closes on Sunday, 2019-09-29 and release on Sunday, 2019-11-17 Aug 20 13:48:34 and on monday people will ask why we aren't on 5.4 since months already Aug 20 13:49:17 You are even talking about it now ;) Aug 20 14:40:23 jow: why aren't we ? Aug 20 14:41:37 blogic: Why arent we on ath11k yet? ;-) Aug 20 14:42:19 i wonder if it will tripple my ath9k chip's throughput .. :/ Aug 20 14:50:51 xback: where is my pony Aug 20 14:51:23 xback: i actually am getting mails asking if ath11k will run on ath10k HW and improve the stability Aug 20 14:51:50 feel free to forward me your reply ;-) Aug 20 14:51:59 i did not reply ;) Aug 20 16:31:49 and on monday people will ask why we aren't on 5.4 since months already Aug 20 16:31:55 oops Aug 20 16:32:03 arrow up fail Aug 20 16:32:06 jow: why aren't we ? Aug 20 16:32:07 :) Aug 20 16:32:30 blogic: because we're lazy and working on the wrong things Aug 20 16:35:37 you have to be ahead, 5.9 is the way we should go! Aug 20 16:36:10 Why aren't we on 6.0 already? Aug 20 16:36:56 because it miscompiles with gcc 11 Aug 20 16:37:24 just needs an autotools update.... add more checks.... Aug 20 18:12:46 and python4 Aug 20 19:42:12 ath11k has been posted for public review Aug 20 19:44:53 nice Aug 20 20:06:23 Hauke: thank you very very much! Aug 20 20:38:24 blogic: nice Aug 20 20:39:59 only the wifi, or SoC's too? Aug 21 00:17:35 DonkeyHotei: only the wireless driver, but some (very limited) parts of ipq8074 are mainline since october 2018 (nothing since) **** ENDING LOGGING AT Wed Aug 21 02:59:58 2019