09:01 <hejux> xdarklight: so far so good, the macirq fix seems to work

13:21 <xdarklight> hejux: great that ccaione's fix also works on your board :)

13:21 <xdarklight> narmstrong: please forget about the topic from my previous ping, I think I figured it out

13:21 <xdarklight> narmstrong: however, I'm hunting down why I don't get anything out of OSD1 on the 32-bit Meson SoCs

13:22 <xdarklight> narmstrong: do you have any idea why VIU_OSD1_CTRL_STAT bit 21 (OSD_ENABLE) stays 0? according to the datasheet it's a read-only bit but your DRM driver is still writing it (which shouldn't hurt though)

13:25 <xdarklight> if I read it back after writing the OSD registers in meson_crtc_irq I get: VIU_OSD1_CTRL_STAT = 0x050ff001, wanted = 0x002ff001

16:43 <hejux> xdarklight: yeah, i wonder how fast can wifi get.

16:43 <hejux> dmesg shows there is a brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6

16:44 <hejux> i made it work on 80Mhz via hostapd, my macbook air connected to it and shows 390Mbps 5G ac, but iperf3 actually speed is only 84Mbps

20:59 <warpme_> guys: what is status mainline 4.20 kernel regarding HDMI audio on s905? Should I apply any patches like for 4.19 (i.e. https://github.com/jeromebrunet/linux/commits/v4.19/aml/gx-audio-wip)?

21:36 <xdarklight> hejux: I've seen worse wifi speeds - I'm not sure what the "best possible" throughput is though

21:45 <Lyude> has anyone managed to actually get the wifi on the vim2 to work with a mainline kernel?

21:45 <Lyude> mine never seems to manage to load the firmware properly: [ 8.853350] brcmfmac mmc2:0001:1: Direct firmware load for brcm/brcmfmac4356-sdio.txt failed with error -2

21:50 <xdarklight> Lyude: which VIM2 exactly? 16GB storage or more?

21:51 <Lyude> xdarklight: 16GB storage, it's the one with the mali T820 on it

21:51 <xdarklight> OK, just wanted to confirm because depending on the model there's a different wireless chip on it...

21:51 <xdarklight> yours has an Ampak AP6356S

21:52 <Lyude> xdarklight: what's the kernel driver that's usually used for that

21:52 <xdarklight> brcmfmac

21:52 <xdarklight> linux-firmware only comes with half of the files you need

21:52 <Lyude> what are the other ones?

21:52 <xdarklight> there's a firmware for the chip itself and some config txt file

21:52 <xdarklight> linux-firmware only ships the firmware but not the config blob

21:53 <xdarklight> https://raw.githubusercontent.com/khadas/android_hardware_amlogic_wifi/Vim/bcm_ampak/config/4356/nvram_ap6356.txt IIRC that is the right one for your device - put that in /lib/firmware/brcm/brcmfmac4356-sdio.txt and reload the brcmfmac driver

21:53 <Lyude> alright, gimme one sec

21:58 <Lyude> xdarklight seems to work! One last warning though: https://paste.fedoraproject.org/paste/eqyHaENCYqpyhfL2jt-Y4g

22:00 <xdarklight> Lyude: I have that as well on my brcmfmac based boards: I don't remember the exact details anymore but that's some newer config blob. I keep telling myself to ignore it because "everything works fine" but it triggers my OCD when I check the kernel logs...

22:06 <xdarklight> Hi chewitt

22:07 <xdarklight> chewitt: I'm not sure if you've seen it: I'm very impatient which is why I send that power_down fix upstream: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git/commit/?h=usb-next&id=cc10ce0c51b13d1566d0ec1dcb472fb86330b391 - it'll be part of v4.21

22:08 <xdarklight> (once it hits mainline we can even ask Greg to backport it to -stable if that doesn't happen automagically due to the Fixes tag)

22:10 <xdarklight> s/Fixes/Cc/