01:32 <s_frit> for rk3399 is there a list somewhere of what works on 4.4 but is not working on mainline and/or armbian 4.20.y?

01:34 <mrueg> s_frit: http://opensource.rock-chips.com/wiki_Status_Matrix#Mainline_Kernel_Status_Matrix

01:34 <s_frit> mrueg: thankyou

01:35 <mrueg> (but it might be outdated)

01:38 <s_frit> no GPU and "incomplete" HDMI are the things that might affect me. i'm developing on-device with a monitor

05:06 <s_frit> NanoPC T4 M.2 PCIe is supposedly not working with the Armbian 4.20.y kernel so, no new kernel for me. i wonder what the issue is

05:24 <s_frit> \join #armbian

06:25 <tomeu> s_frit: I'm using a nanopc-t4 to hack on panfrost, and it's working quite well

06:25 <tomeu> with hdmi

06:28 <s_frit> tomeu: interesting. you're using mainline kernel?

06:28 <tomeu> yep, 5.0-rc*

06:28 <s_frit> are you using the m.2 slot?

06:28 <tomeu> nope

06:29 <s_frit> i'm booting off an nvme. igor mentioned on the forums recently that m.2 is broken with the latest armbian 4.20 kernel. but i have no other info

06:29 <tomeu> guess one would need to test with mainline, see how it fails, and probably ask Robin Murphy if he knows anything about it

06:29 <tomeu> (he's upstreaming support for this board)

06:30 <s_frit> what are you using for userspace?

06:32 <s_frit> this might all be best left to people who know what they're doing. i'm just starting learning to write kernel modules (driver for custom audio board) so i can probably get by with 4.4 kernel until the m.2 issue is resolved

06:33 <tomeu> just debian

06:33 <tomeu> sounds good to me, though debugging the kernel is a great way of learning how things tie together :)

06:34 <s_frit> yeah. i fear that the learning curve to get from where i am now, to "debugging the kernel" might be a bit steep

06:44 <mmind00> s_frit: you could nevertheless train to collect debug info :-) ... aka dump serial output somewhere and check for pcie errors or any log lines related to it ;-)

06:55 <s_frit> mmind00: true. but to do that wouldn't i have to learn how to build a bootable debian image with mainline kernel?

06:55 <tomeu> s_frit: tbh, i think debugging existing code makes the learning curve smoother, not steeper

06:56 <s_frit> in my case the learning curve involves learning how to get started with linux images and kernel building + debugging

06:57 <s_frit> i'm not worried about the code debugging aspect, i have plenty of experience with that

06:57 <tomeu> I personally cannot contemplate writing kernel code before having such skills, but I guess there could be many ways of coming up with your driver

06:58 <tomeu> I would expect that investment to pay off, though

06:58 <s_frit> the investment will be less when i am motivated to do it

06:59 <s_frit> i don't feel like i need to know how to debug a non-booting board just to develop an lkm

07:01 <s_frit> anyhow, i'd be happy to contribute to fixing this pcie issue if there was an easy way to get started, but last time i looked for instructions i did not find a one-stop howto for building a bootable image

07:04 <tomeu> that basically depends on what bootloader you are running

07:04 <tomeu> first time I booted mine, I installed mainline u-boot though, so I'm not sure how that would be done with the factory one

07:08 <s_frit> i'm not sure whether armbian installer replaced the bootloader. i would imagine so

09:38 <mani_s> mmind00, have you seen any issue with using (AP6356 + linux-firmware) on rk3399 based devices?

09:39 <mani_s> rock960 works well with rockchip wifi driver but not with upstream brcmfmac driver + firmware from linux-firmware

09:42 <mani_s> mmind00, log: https://pastebin.ubuntu.com/p/xZDMcQsMmT/

11:32 <mmind00> mani_s: I don't really touch wifi, so no clue

11:35 <mani_s> mmind00, okay, no probs