**** BEGIN LOGGING AT Sat Nov 10 02:59:59 2018
Nov 10 09:30:37 <barhom> ipq4019, ath10k drivers? (2 and 5 ghz), where are these open source drivers being developed? anyone know a link to the git or something?
Nov 10 09:31:54 <russell--> https://wireless.wiki.kernel.org/en/users/drivers/ath10k/sources
Nov 10 10:55:46 <stintel> KanjiMonster: are you planning to send https://pastebin.com/WD3383t6 upstream ?
Nov 10 11:07:19 <stintel> Hauke: https://git.openwrt.org/?p=openwrt/staging/stintel.git;a=shortlog;h=refs/heads/brcm2708-4_14
Nov 10 11:07:28 <stintel> have this running on my Zero W right now
Nov 10 11:14:09 <Hauke> stintel: nice
Nov 10 11:14:35 <stintel> Hauke: would you mind having a look at the patches and tell me if you think I should drop more (because unrelated)?
Nov 10 11:15:27 <stintel> and if you think it's OK I would like to push it
Nov 10 11:15:33 <Hauke> will have a look at this tomorrow
Nov 10 11:15:37 <stintel> should have done this way earlier :)
Nov 10 11:15:59 <Hauke> I am currently taking part in this: https://ructfe.org/
Nov 10 11:16:16 <stintel> cool, good luck!
Nov 10 11:16:20 <stintel> and thanks in advance
Nov 10 11:22:49 <stintel> Hauke: I'm going to send a link to my staging tree to the ML as well
Nov 10 11:23:11 <stintel> not going to embed the patch, it's going to be a mess with all those raspberry pi patches
Nov 10 11:26:57 <stintel> KanjiMonster: I can send it too but you wrote it ;-)
Nov 10 12:08:33 <danrl> I am maintainer of a package in openwrt/luci and would like to drop maintainership for it. I was not able to find a successor over the past months and I am not sure how to proceed. Shall I remove the PKG_MAINTAINER variable entirely from the Makefile, set it so a special value, or remove the entire package source (and therefore the functionality). What's the best way to handle this?
Nov 10 12:21:58 <jow> danrl: just remove the maintainer
Nov 10 12:22:13 <danrl> jow: thanks! will do.
Nov 10 14:51:05 <mirko> anybody familiar with the layout of QCA mtd partitions named "art" / "art-backup", supposed to have ath10k calibration data stored on? apparently data on my art partition is not formatted in any expected way (according to the hotplug firmware loading script)..
Nov 10 14:54:07 <mirko> apropos maintainer - is there a defined way of having multiple maintainers listed for a package?
Nov 10 15:00:24 <gch981213[w]> Hi all! Are there any updates for ath79 target? it seems that pull requests on GitHub are piling up...
Nov 10 15:28:24 <ldir> mirko: define 'defined' ?  Do you mean just comma separated or with continuation lines?
Nov 10 15:29:17 <Borromini> gch981213[w]: since ath79 won't be ready for 19.01 i think it has lower priority atm... plans seem to be to phase out ar71xx for a 19.06 release though.
Nov 10 15:32:35 <ldir> mirko: I favour the latter but I've seen both e.g. https://git.openwrt.org/?p=openwrt/openwrt.git;a=blob;f=package/network/services/wireguard/Makefile;h=8a71ce27d785802abe66e553d4770d0215093f17;hb=5617e138bdaff94587d700def3d74e81c5b2db19
Nov 10 16:05:43 <jow> mirko: comma separated
Nov 10 16:06:09 <jow> PKG_MAINTAINER:=Foo Bar <blah@example.org>, Bar Baz <other@example.org>
Nov 10 16:19:00 <stintel> hmm, kmod-bluetooth contains btusb, if I want to add btbcm, should I add it to kmod-bluetooth as well? or should I create a separate package for it? in case of the latter I need to split off btusb from kmod-bluetooth as well because btusb depends on btbcm when it is enabled in kernel config
Nov 10 16:20:48 <stintel> for prebuilt images it's not going to make a difference, if a user will install kmod-btusb it will pull in kmod-btbcm due to all kmods being enabled in image builds
Nov 10 16:21:47 <stintel> the bluetooth dependencies in the kernel are weird
Nov 10 16:27:19 <jow> stintel: lump them all together into kmod-bluetooth
Nov 10 16:28:17 <stintel> jow: ok
Nov 10 16:49:00 <ldir> jow: continuous line?  What happens with 4 maintainers etc?
Nov 10 16:58:48 <jow> ldir: <comma> <space> <baskslash> <tab> next name
Nov 10 17:11:23 <greearb__> bleh, rtl8812au driver doesn't specify a MAC for its phy device...guess it is time to dig a bit!
Nov 10 18:29:28 <greearb__> here is an update for the rtl8812au that fixes phy0 mac-address:  https://github.com/greearb/openwrt-ct/commit/196cf45c9aa815b7b5ab56d546db2643b1c36ecc
Nov 10 19:36:27 <ThijsNL> hi
Nov 10 19:38:03 <ThijsNL> I've got a question regarding uploading images to the openwrt wiki. Mediamanager says my access rights are insufficient
Nov 10 19:59:27 <pkgadd> ThijsNL: /* How to add images ========> http://openwrt.org/meta/adding_images_to_openwrt_wiki */
Nov 10 20:02:41 <ThijsNL> thank you pkgadd
Nov 10 20:05:52 <ThijsNL> it worked
Nov 10 22:56:24 <jwh> hm, my unifi ap is not impressed with 18.06
Nov 10 23:07:24 <jwh> nothing logged, but it seems to stall and disconnect stations (I know very little about wifi so thats probably as good as I can explain it0
Nov 10 23:07:27 <jwh> )
Nov 10 23:10:03 <mirko> jow: ldir: thanks
Nov 10 23:15:37 <pkgadd> if logread won't help, keep hostapd_cli running, perhaps that can give you pointers
Nov 10 23:16:52 <jwh> yeah, all thats in the logs is the deauth
Nov 10 23:16:55 <jwh> after a timeout
Nov 10 23:17:10 <jwh> but I meant more like no messages from the driver or anything
Nov 10 23:17:19 <jwh> it doesn't seem to be all clients either, hmmm
Nov 10 23:18:03 <jwh> the worst affected is my intel ac laptop, but I swear the intel stuff is really picky about APs
Nov 10 23:18:12 <jwh> wasn't present on 17 though
**** ENDING LOGGING AT Sun Nov 11 03:00:00 2018