ldevulder has quit [Read error: Connection reset by peer]
ldevulder has joined #linux-rockchip
ldevulder has quit [Read error: Connection reset by peer]
stikonas has quit [Ping timeout: 250 seconds]
stikonas has joined #linux-rockchip
ldevulder has joined #linux-rockchip
stikonas has quit [Remote host closed the connection]
kaspter has joined #linux-rockchip
anarsoul|2 has quit [Remote host closed the connection]
vstehle has quit [Ping timeout: 250 seconds]
nsaenz has quit [Ping timeout: 246 seconds]
nsaenz has joined #linux-rockchip
field^Zzz1 has joined #linux-rockchip
field^Mop has quit [Ping timeout: 250 seconds]
tlwoerner has quit [Quit: Leaving]
tlwoerner has joined #linux-rockchip
chewitt has quit [Ping timeout: 250 seconds]
vstehle has joined #linux-rockchip
chewitt has joined #linux-rockchip
chewitt has quit [Client Quit]
quark_ has joined #linux-rockchip
maz has joined #linux-rockchip
matthias_bgg has joined #linux-rockchip
nsaenz has quit [Remote host closed the connection]
nsaenz has joined #linux-rockchip
vagrantc has quit [Ping timeout: 252 seconds]
BenG83 has quit [Quit: Leaving]
kaspter has quit [Read error: Connection reset by peer]
kaspter has joined #linux-rockchip
BenG83 has joined #linux-rockchip
Kwiboo has quit [Ping timeout: 244 seconds]
Kwiboo has joined #linux-rockchip
aalm has quit [Ping timeout: 250 seconds]
vicencb has joined #linux-rockchip
hanetzer has quit [Ping timeout: 245 seconds]
hanetzer has joined #linux-rockchip
chewitt has joined #linux-rockchip
sb35 has joined #linux-rockchip
kaspter has quit [Read error: Connection reset by peer]
kaspter has joined #linux-rockchip
aalm has joined #linux-rockchip
ldevulder_ has joined #linux-rockchip
ldevulder has quit [Ping timeout: 268 seconds]
JohnDoe_71Rus has joined #linux-rockchip
ldevulder_ is now known as ldevulder
kaspter has quit [Read error: Connection reset by peer]
kaspter has joined #linux-rockchip
<DuClare>
Hm, it appears there's no driver for rk3288 dmc in mainline kernel.. am I smoking chips or suffering seriously limited performance without it? :|
<shadeslayer>
Hey, does anyone have notes on how to build a debian mainline image for the Firefly RK3399?
<shadeslayer>
I've built a img file with the right packages, just not sure how to configure flash-kernel
ldevulder has quit [Read error: Connection reset by peer]
stikonas has quit [Remote host closed the connection]
stikonas has joined #linux-rockchip
matthias_bgg has quit [Ping timeout: 250 seconds]
<mmind00>
DuClare: dmc - normally your bootloader _should_ already bring up the ram in an optimal config ... so dmc is more or less interesting for scaling down the ram frequency, aka power-savings
<vagrantc>
so, i managed to finally get a working arm-trusted-firmware+u-boot build with firefly-rk3399 ... but it only works from eMMC, not microSD
<vagrantc>
and on the remaining board, i think i somehow shorted the eMMC or something in my many attempts to get it working over time
<mmind00>
vagrantc: so spl -> atf -> uboot I guess, does nothing work or does it stop at some point in the middle?
adjtm has quit [Remote host closed the connection]
<mmind00>
DuClare: hmm ... not sure what you're doing, but with mainline uboot, extlinux-config to load kernel+dtb there shouldn't be any issues at all
<vagrantc>
mmind00: yes, ... it seems to load SPL and then nothing
<vagrantc>
mmind00: it used to enter into an abort loop of some kind
adjtm has joined #linux-rockchip
<stikonas>
vagrantc: any instructions?
<stikonas>
I didn't manage to boot on rockpro64
<vagrantc>
U-Boot SPL board init
<vagrantc>
that's as far as i got
<stikonas>
oh ok
<stikonas>
oh, so it didn't boot?
<vagrantc>
well, on another, i installed it to eMMC and it booted
<stikonas>
well, I have eMMC... on my board but I didn't manage to boot :(
<stikonas>
hmm, how does SPL find ATF?
<stikonas>
btw, what kind of RAM is in firefly-rk3399?
<stikonas>
rockpro64 has LPDDR4, so I need another blob to initialize RAM :(
<vagrantc>
i don't recall off the top of my head
<vagrantc>
i couldn't get upstream arm-trusted-firmware to build on a recent Debian toolchain, but it worked fine with Debian stretch's toolchain
<vagrantc>
filed a bug in tf-issues about it on github ... PMUSRAM too large or something like that
<vagrantc>
[ARM-software/tf-issues] rk3399 fails to build: region PMUSRAM overflowed (#650)
<vagrantc>
also some licensing issues: [ARM-software/tf-issues] rk3399: licensing of hdcp.bin (#651)
<vagrantc>
what is hdcp.bin used for?
<vagrantc>
i am inconsistantly able to boot from microSD using miniloader and all that
<stikonas>
yes, I used debian stretch chroot tree. Didn'd see that hdcp.bin issue though
<stikonas>
well, I didn't use that miniloader, I use u-boot spl
<vagrantc>
stikonas: are there patches from rockpro64 submitted upstream to u-boot?