ChanServ changed the topic of #linux-rockchip to: Rockchip development discussion | IRC log http://irclog.whitequark.org/linux-rockchip | Community GH https://github.com/linux-rockchip | Rockchip GH https://github.com/rockchip-linux | ML https://groups.google.com/group/linux-rockchip
vicencb has quit [Quit: Leaving.]
s_frit has quit [Remote host closed the connection]
s_frit has joined #linux-rockchip
<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?
<s_frit> mrueg: thankyou
<mrueg> (but it might be outdated)
<s_frit> no GPU and "incomplete" HDMI are the things that might affect me. i'm developing on-device with a monitor
stikonas has quit [Remote host closed the connection]
nighty- has joined #linux-rockchip
vstehle has quit [Ping timeout: 240 seconds]
marcodiego has quit [Ping timeout: 250 seconds]
_whitelogger has joined #linux-rockchip
field^Zzz3 has joined #linux-rockchip
field^Zzz2 has quit [Ping timeout: 268 seconds]
aalm has quit [Ping timeout: 246 seconds]
<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
lurchi__ has quit [Ping timeout: 246 seconds]
<s_frit> \join #armbian
hanetzer has quit [Ping timeout: 244 seconds]
vstehle has joined #linux-rockchip
aalm has joined #linux-rockchip
<tomeu> s_frit: I'm using a nanopc-t4 to hack on panfrost, and it's working quite well
<tomeu> with hdmi
<s_frit> tomeu: interesting. you're using mainline kernel?
<tomeu> yep, 5.0-rc*
<s_frit> are you using the m.2 slot?
<tomeu> nope
<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
<tomeu> guess one would need to test with mainline, see how it fails, and probably ask Robin Murphy if he knows anything about it
<tomeu> (he's upstreaming support for this board)
<s_frit> what are you using for userspace?
<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
<tomeu> just debian
<tomeu> sounds good to me, though debugging the kernel is a great way of learning how things tie together :)
<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
<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 ;-)
<s_frit> mmind00: true. but to do that wouldn't i have to learn how to build a bootable debian image with mainline kernel?
<tomeu> s_frit: tbh, i think debugging existing code makes the learning curve smoother, not steeper
<s_frit> in my case the learning curve involves learning how to get started with linux images and kernel building + debugging
<s_frit> i'm not worried about the code debugging aspect, i have plenty of experience with that
<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
<tomeu> I would expect that investment to pay off, though
<s_frit> the investment will be less when i am motivated to do it
<s_frit> i don't feel like i need to know how to debug a non-booting board just to develop an lkm
<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
<tomeu> that basically depends on what bootloader you are running
<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
<s_frit> i'm not sure whether armbian installer replaced the bootloader. i would imagine so
ldevulder has joined #linux-rockchip
indy has quit [Quit: ZNC - http://znc.sourceforge.net]
indy has joined #linux-rockchip
apritzel has joined #linux-rockchip
nsaenz has joined #linux-rockchip
<mani_s> mmind00, have you seen any issue with using (AP6356 + linux-firmware) on rk3399 based devices?
<mani_s> rock960 works well with rockchip wifi driver but not with upstream brcmfmac driver + firmware from linux-firmware
BenG83 has joined #linux-rockchip
loswillios has joined #linux-rockchip
<mmind00> mani_s: I don't really touch wifi, so no clue
<mani_s> mmind00, okay, no probs
nsaenz has quit [Remote host closed the connection]
nsaenz has joined #linux-rockchip
hanetzer has joined #linux-rockchip
sb35 has quit [Quit: sb35]
vicencb has joined #linux-rockchip
loswillios has quit [Ping timeout: 246 seconds]
afaerber has joined #linux-rockchip
loswillios has joined #linux-rockchip
s_frit has quit [Remote host closed the connection]
s_frit has joined #linux-rockchip
JohnDoe_71Rus has joined #linux-rockchip
perr has joined #linux-rockchip
perr has quit [Remote host closed the connection]
nighty- has quit [Quit: Disappears in a puff of smoke]
BenG83 has quit [Quit: Leaving]
ayaka has quit [Ping timeout: 246 seconds]
ayaka has joined #linux-rockchip
stikonas has joined #linux-rockchip
nashpa has quit [Ping timeout: 272 seconds]
ayaka has quit [Ping timeout: 268 seconds]
ayaka has joined #linux-rockchip
ayaka has quit [Ping timeout: 245 seconds]
ayaka has joined #linux-rockchip
apritzel has quit [Ping timeout: 245 seconds]
ayaka has quit [Ping timeout: 245 seconds]
ayaka has joined #linux-rockchip
afaerber has quit [Quit: Leaving]
sb35 has joined #linux-rockchip
lkcl has quit [Read error: Connection reset by peer]
lkcl has joined #linux-rockchip
nsaenz has quit [Remote host closed the connection]
nsaenz has joined #linux-rockchip
JohnDoe_71Rus has quit [Quit: KVIrc 5.0.0 Aria http://www.kvirc.net/]
rperier has quit [Remote host closed the connection]
nsaenz has quit [Remote host closed the connection]
nsaenz has joined #linux-rockchip
nsaenz has quit [Remote host closed the connection]
nsaenz has joined #linux-rockchip
nsaenz has quit [Remote host closed the connection]
ayaka has quit [Ping timeout: 250 seconds]
ayaka has joined #linux-rockchip
ldevulder has quit [Ping timeout: 240 seconds]
VargaD has joined #linux-rockchip
VargaD has quit [Ping timeout: 264 seconds]
VargaD has joined #linux-rockchip
vicencb has quit [Quit: Leaving.]
vagrantc has joined #linux-rockchip
vicencb has joined #linux-rockchip
lurchi_ has joined #linux-rockchip
vicencb has quit [Quit: Leaving.]