Esmil has quit [Remote host closed the connection]
camus has joined #linux-rockchip
kaspter has quit [Read error: Connection reset by peer]
camus is now known as kaspter
camus has joined #linux-rockchip
kaspter has quit [Ping timeout: 240 seconds]
camus is now known as kaspter
camus has joined #linux-rockchip
kaspter has quit [Ping timeout: 240 seconds]
camus is now known as kaspter
ifbizo_ has quit [Remote host closed the connection]
ifbizo_ has joined #linux-rockchip
<wens>
hmm, with 10/22 -next my c201 still shows black screen, except for the mouse cursor, under lightdm login
camus has joined #linux-rockchip
kaspter has quit [Ping timeout: 276 seconds]
camus is now known as kaspter
kaspter has quit [Ping timeout: 268 seconds]
kaspter has joined #linux-rockchip
kaspter has quit [Ping timeout: 240 seconds]
kaspter has joined #linux-rockchip
kaspter has quit [Ping timeout: 240 seconds]
camus has joined #linux-rockchip
camus is now known as kaspter
camus has joined #linux-rockchip
kaspter has quit [Ping timeout: 240 seconds]
camus is now known as kaspter
kaspter has quit [Ping timeout: 240 seconds]
kaspter has joined #linux-rockchip
ifbizo_ has quit [Remote host closed the connection]
ifbizo_ has joined #linux-rockchip
matthias_bgg has joined #linux-rockchip
paulk-leonov has quit [Ping timeout: 240 seconds]
kaspter has quit [Quit: kaspter]
kaspter has joined #linux-rockchip
inode has joined #linux-rockchip
kevery has quit [Ping timeout: 246 seconds]
kevery has joined #linux-rockchip
ldevulder_ is now known as ldevulder
paulk-leonov has joined #linux-rockchip
camus has joined #linux-rockchip
kaspter has quit [Ping timeout: 264 seconds]
camus is now known as kaspter
aalm has quit [Quit: xyz 2.3]
<mmind00>
wens: panfrost-related perhaps? ... I have seen that as well with a specific git state of mesa, but hadn't the time to investigate
nsaenz has quit [Quit: Leaving]
nsaenz has joined #linux-rockchip
<wens>
mmind00: yeah. working it out over on #panfrost
<wens>
did a bisect already. it's related to the runtime PM changes for panfrost
<mmind00>
wens: ok, glad to hear that
kevery has quit [Ping timeout: 252 seconds]
warpme_ has joined #linux-rockchip
field^Mop has joined #linux-rockchip
BenG83 has quit [Ping timeout: 252 seconds]
ldevulder_ has joined #linux-rockchip
ldevulder has quit [Ping timeout: 246 seconds]
BenG83 has joined #linux-rockchip
ldevulder_ is now known as ldevulder
BenG83 has quit [Ping timeout: 240 seconds]
nlhowell has joined #linux-rockchip
BenG83 has joined #linux-rockchip
ldevulder_ has joined #linux-rockchip
aalm has joined #linux-rockchip
ldevulder has quit [Ping timeout: 268 seconds]
ldevulder__ has joined #linux-rockchip
ldevulder_ has quit [Ping timeout: 240 seconds]
kaspter has quit [Quit: kaspter]
kaspter has joined #linux-rockchip
ldevulder__ is now known as ldevulder
jlanda has quit [Quit: jlanda]
jlanda has joined #linux-rockchip
field^Mop has quit [Ping timeout: 265 seconds]
JohnDoe_71Rus has joined #linux-rockchip
vstehle has quit [Quit: WeeChat 2.6]
aalm has quit [Read error: Connection reset by peer]
vstehle has joined #linux-rockchip
ayaka has quit [Read error: Connection reset by peer]
ayaka has joined #linux-rockchip
matthias_bgg has quit [Ping timeout: 265 seconds]
kaspter has quit [Ping timeout: 268 seconds]
kaspter has joined #linux-rockchip
aalm has joined #linux-rockchip
kaspter has quit [Ping timeout: 240 seconds]
kaspter has joined #linux-rockchip
stikonas has joined #linux-rockchip
nsaenz has quit [Ping timeout: 240 seconds]
nsaenz has joined #linux-rockchip
return0e_ has joined #linux-rockchip
return0e has quit [Ping timeout: 268 seconds]
adjtm has quit [Ping timeout: 252 seconds]
nsaenz has quit [Ping timeout: 268 seconds]
vagrantc has joined #linux-rockchip
<vagrantc>
hrm. arm-trusted-firmware v2.2 doesn't seem to work with u-boot 2019.10 on rock64-rk3328 or firefly-rk3399 ... same u-boot with arm-trusted-firmware v2.1 works fine ... hangs at failing to detect MMC :/
* vagrantc
tests rockpro64-rk3399 too
<stikonas>
vagrantc: I haven't tested recently, but I think I had problems with rockpro64-rk3399 too
<stikonas>
but didn't have time to bisect
<stikonas>
commit ace23683beb81354d6edbc61c087ab8c384d0631 is working for me, that's the end of september
<vagrantc>
oh!
<vagrantc>
stikonas: on atf?
<stikonas>
vagrantc: yes
<vagrantc>
that narrows down the bisect considerably...
<stikonas>
and it was already broken for some time
<stikonas>
I think it broke early october for me
<vagrantc>
ok, can confirm it's similarly broken on rockpro64
<stikonas>
so I'm at the moment on that ace236...
<stikonas>
so it's likely that you are seeing the same issue
<vagrantc>
will ... hopefully try to bisect at some point... but right now ... hrm.
<stikonas>
although, I don't remember what exactly was the error message but I think it was mmc
<stikonas>
well, if you do, let me know, or if I do it, I'll let you know
<vagrantc>
thanks
<vagrantc>
there might have been a change at load addresses
<stikonas>
vagrantc: am I supposed to apply a patch to change baudrate to 1500000 when I compile ATF? All other stages use this, but default in ATF is 115200, so makes my debugging harder...
<stikonas>
indeed, that's why I didn't send this upstream...
wbn has joined #linux-rockchip
<mmind00>
stikonas vagrantc: wrong approach for the uarts ... (1) there are a number of platforms (including the rk3399 chromebooks) running at that 115200; (2) ATF for some time has the ability to read the actual uart+baud from the supplied dts
<mmind00>
so if your dts has a chosen node, this shouldn't actually be an issue with recent ATFs