<amstan>
i'm amused that dwc2 is still a common subject of conversation in here
stdint has joined #linux-rockchip
kaspter has joined #linux-rockchip
kaspter has quit [Client Quit]
kaspter has joined #linux-rockchip
kaspter has quit [Ping timeout: 268 seconds]
afaerber has quit [Ping timeout: 240 seconds]
kaspter has joined #linux-rockchip
<solidhal>
amstan: is there a better place to be asking?
<amstan>
solidhal: no, sorry, don't misunderstand
<amstan>
you're probably fine in here, i'm sure there's many people that would know too
<amstan>
it's just that it seems like it's been a long road to get dwc2 working nicely
<solidhal>
cool, I hope someone does. dwc2 handles some thindwc2does. dwc2 is funky
<amstan>
it's getting better, but there's still issues i guess (as shown by your question)
<solidhal>
yeah, it still doesnt play well with some of the open wireless devices
<amstan>
recently we've been doing another round of upstreaming for the rk3288 chromebooks that we released a while back, through that we might find a bunch of patches that we forgot
<amstan>
there's a chance something in there might help
<amstan>
well, maybe not that many on a second look
<solidhal>
atleast a few look interesting
afaerber has joined #linux-rockchip
perr has joined #linux-rockchip
perr has quit [Remote host closed the connection]
perr has joined #linux-rockchip
perr has quit [Remote host closed the connection]
<hanetzer>
maz: question? as of this moment, is 5.0.7 capable of kexec'ing on arm64/rk3399 or do I need your patches?
_whitelogger has joined #linux-rockchip
perr has joined #linux-rockchip
MoeIcenowy has quit [Quit: ZNC 1.6.5+deb1+deb9u1 - http://znc.in]
MoeIcenowy has joined #linux-rockchip
lkcl has quit [Ping timeout: 268 seconds]
vagrantc has quit [Quit: leaving]
vagrantc_ is now known as vagrantc
gnufan_home has joined #linux-rockchip
lkcl has joined #linux-rockchip
gnufan_home has quit [Ping timeout: 255 seconds]
chewitt has quit [Quit: Adios!]
gnufan_home has joined #linux-rockchip
perr has quit [Remote host closed the connection]
perr has joined #linux-rockchip
perr has quit [Remote host closed the connection]
arnd has quit [Ping timeout: 252 seconds]
perr has joined #linux-rockchip
warpme_ has joined #linux-rockchip
arnd has joined #linux-rockchip
gaulishcoin has joined #linux-rockchip
ayaka has quit [Ping timeout: 264 seconds]
yann has quit [Ping timeout: 255 seconds]
warpme_ has quit [Quit: warpme_]
perr has quit [Remote host closed the connection]
perr has joined #linux-rockchip
stikonas has joined #linux-rockchip
ayaka has joined #linux-rockchip
stikonas has quit [Remote host closed the connection]
ayaka has quit [Ping timeout: 255 seconds]
ayaka has joined #linux-rockchip
warpme_ has joined #linux-rockchip
ldevulder_ is now known as ldevulder
vagrantc has quit [Quit: leaving]
stdint has quit [Read error: Connection reset by peer]
stdint has joined #linux-rockchip
<maz>
hanetzer: it is capable of kexec-ing, but the main issue is that a number of devices are not properly reset (I seem to have ongoing issues with the clocks on my kevin's internal display).
perr has quit [Remote host closed the connection]
<maz>
hanetzer: (although that's with 5.0-rc7 and a gazillion of patches that I had otherwise queued or needed to test)
perr has joined #linux-rockchip
perr has quit [Remote host closed the connection]
vicencb has joined #linux-rockchip
warpme_ has quit [Quit: warpme_]
yann has joined #linux-rockchip
BenG83 has quit [Ping timeout: 255 seconds]
vicencb has quit [Remote host closed the connection]
vicencb has joined #linux-rockchip
<mmind00>
maz: did you find time to check the drm-shutdown-patch yet?
perr has joined #linux-rockchip
vicencb has quit [Remote host closed the connection]
vicencb has joined #linux-rockchip
vicencb has quit [Client Quit]
perr has quit [Remote host closed the connection]
perr has joined #linux-rockchip
t3st3r has quit [Remote host closed the connection]
perr has quit [Remote host closed the connection]
perr has joined #linux-rockchip
t3st3r has joined #linux-rockchip
perr has quit [Remote host closed the connection]
perr has joined #linux-rockchip
field^Mop has joined #linux-rockchip
perr has quit [Remote host closed the connection]
<sphalerite>
mmind00: the device tree for nanopi* is there in 5.1+, but zfs doesn't currently build against 5.0+ on aarch64 so I can't use it yet :(
<mmind00>
sphalerite: that dts doesn't contain magic I think, so you should just be able to use that on 5.0 as well
<sphalerite>
mmind00: oh sweet!
<sphalerite>
what about 4.19? :p
<sphalerite>
(since zfs doesn't build with 5.0 either…)
<mmind00>
sphalerite: maybe use filesystem that is supported? :-P
<mmind00>
sphalerite: but the same should apply for 4.19 ... but may or may not need adaptions
<sphalerite>
mmind00: would be glad to, if I could magically migrate my zfs pool to a btrfs pool…
<sphalerite>
(although I'd also need to learn how to use btrfs :p )
<sphalerite>
plus I'm still a little bit worried that btrfs might eat my data
<sphalerite>
although if it's the default filesystem for SLES nowadays…
<sphalerite>
and if I could zfs send | btrfs recv :p
_whitelogger has joined #linux-rockchip
gnufan_home has quit [Ping timeout: 246 seconds]
kaspter has quit [Read error: Connection reset by peer]
kaspter has joined #linux-rockchip
s_frit has joined #linux-rockchip
<hanetzer>
maz: problem is some reason I'm stuck at 'kexec_core: Starting new kernel' when booted in a buildroot-based initramfs
<hanetzer>
unsure what's failing here.
<sphalerite>
hanetzer: how long?
<sphalerite>
oh maz seems to know more things, never mind me.
afaerber has quit [Quit: Leaving]
EmilKarlson has joined #linux-rockchip
thefloweringash is now known as thefloweringash_
warpme_ has joined #linux-rockchip
afaerber has joined #linux-rockchip
gnufan_home has joined #linux-rockchip
vicencb has joined #linux-rockchip
warpme_ has quit [Quit: warpme_]
mniip_ has joined #linux-rockchip
mniip has quit [Ping timeout: 633 seconds]
mniip_ is now known as mniip
mniip has quit [Client Quit]
gnufan_home has quit [Ping timeout: 246 seconds]
mniip has joined #linux-rockchip
<hanetzer>
sphalerite: long enough for me to say 'indefinite'
<hanetzer>
I gotta use said laptop so I can't keep it stuck forever :P
EmilKarlson has quit [Write error: Connection reset by peer]
warpme_ has joined #linux-rockchip
JohnDoe_71Rus has joined #linux-rockchip
arnd has quit []
arnd has joined #linux-rockchip
thefloweringash has joined #linux-rockchip
Guest32482 has joined #linux-rockchip
<warpme_>
guys: is it possible to get hdmi audio working on beelink a1 rk3328 with mainline 5.0.7 kernel? If yes - then what patchset needs to be applied?
<warpme_>
hmm - may you pls give me a bit more details? what is ucm file?
<hanetzer>
warpme_: honestly I can't. a ucm file is an alsa thingie for configuring stuff. for instance, to get proper audio output on the asus c201/rk3288-veyron-speedy chromebook you need the ucm files. those have made it into upstream alsa but some things haven't
<warpme_>
ah ok. does anybody have working hdmi audio on beelink a1 (or similiar hw) so I can adapt ucm files?
drrty has joined #linux-rockchip
warpme_ has quit [Quit: warpme_]
yann has quit [Ping timeout: 250 seconds]
warpme_ has joined #linux-rockchip
ldevulder has quit [Ping timeout: 246 seconds]
<sphalerite>
warpme_: no, ucm won't help if aplay -l doesn't list any cards
<warpme_>
i’m scrathing my head how to debug further. lsmod shows modules are loaded but aplay -l shows no cards…
ldevulder has joined #linux-rockchip
EmilKarlson has joined #linux-rockchip
warpme_ has quit [Quit: warpme_]
warpme_ has joined #linux-rockchip
<Kwiboo>
warpme_: what device tree are you using, acodec driver is not merged so if you have acodec dai part of a graph card in device tree no card will show up
<warpme_>
Kwiboo: thx alot. ill try with removing from device tree. Give me some time as now I’m building mainline ayufan-rock64 kernel to see how it goes on my A1.
<Kwiboo>
if you only want audio working you should only need one or two patches, the full v5.0.7...rockchip-5.x-hdmi-sound contains most if not all rockchip related dts+clk related patches from v5.1+v5.2, a few other rk drm patches queued for v5.1 and my own commits for improved multi channel hdmi audio and cec
<Kwiboo>
if you want to keep patches down you probably do not want the 140 patches v5.0.7...rockchip-5.x-vpu-v2 to add v4l2 core v5.1/v5.2 + rk vpu mpeg-2 driver ;-)
gaulishcoin has quit [Remote host closed the connection]
<mmind00>
sphalerite: does the dts have a memory node?
<mmind00>
sphalerite: i.e. normally the bootloader is supposed to populate the memory node of the dts ... but depending on what bootloader actually is on the board it may not do that
<mmind00>
in any case such a kernel panic should not happen at all with any dts ... as nothing really board-specific was even used from the dts yet at that point
<mmind00>
sphalerite: just checked ... and didn't find a memory node ... so I guess you're suffering from an outdated bootloader?
stikonas has joined #linux-rockchip
field^Mop has quit [Ping timeout: 246 seconds]
vagrantc has quit [Quit: leaving]
stikonas has quit [Remote host closed the connection]