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
vagrantc has quit [Quit: leaving]
stikonas has quit [Ping timeout: 272 seconds]
vagrantc has joined #linux-rockchip
drrty has quit [Remote host closed the connection]
_whitelogger has joined #linux-rockchip
vstehle has quit [Ping timeout: 260 seconds]
chewitt has quit [Read error: Connection reset by peer]
chewitt has joined #linux-rockchip
chewitt has quit [Remote host closed the connection]
JohnDoe_71Rus has joined #linux-rockchip
vagrantc has quit [Quit: leaving]
vstehle has joined #linux-rockchip
archetech has quit [Quit: Konversation terminated!]
kevery has joined #linux-rockchip
warpme_ has joined #linux-rockchip
field^Mop has joined #linux-rockchip
stikonas has joined #linux-rockchip
vicencb has joined #linux-rockchip
JohnDoe_71Rus has quit [Ping timeout: 272 seconds]
cyteen has joined #linux-rockchip
chewitt has joined #linux-rockchip
lkcl has joined #linux-rockchip
Xalius has joined #linux-rockchip
lkcl has quit [Ping timeout: 240 seconds]
lkcl has joined #linux-rockchip
Xalius has quit [Quit: Leaving]
kevery has quit [Ping timeout: 272 seconds]
alpernebbi has joined #linux-rockchip
nlhowell has quit [Ping timeout: 260 seconds]
LargePrime has joined #linux-rockchip
lkcl has quit [Ping timeout: 265 seconds]
stikonas has quit [Remote host closed the connection]
stikonas has joined #linux-rockchip
lkcl has joined #linux-rockchip
elektirnis has quit [Read error: Connection reset by peer]
elektirnis has joined #linux-rockchip
return0e has quit [Ping timeout: 240 seconds]
tuxd3v has joined #linux-rockchip
<tchebb> eballetbo: That looks like it's just the timeout for trying to load DP firmware. I imagine it was arbitrarily set to something that seemed long enough that it would never interfere with a working firmware load. Although 64 seconds does seem excessive...
<tchebb> lvrp16: RK3399's BootROM at least has no way to reorder or override the boot sequence. It'll always go through the devices in the order the TRM shows and boot the first one that works
alpernebbi has quit [Quit: alpernebbi]
return0e has joined #linux-rockchip
aalm has quit [Ping timeout: 240 seconds]
aalm has joined #linux-rockchip
LargePrime has quit [Ping timeout: 272 seconds]
LargePrime has joined #linux-rockchip
lkcl has quit [Ping timeout: 256 seconds]
stikonas has quit [Remote host closed the connection]
stikonas has joined #linux-rockchip
field^Mop has quit [Ping timeout: 256 seconds]
elektrinis has joined #linux-rockchip
elektirnis has quit [Ping timeout: 256 seconds]
tuxd3v has quit [Remote host closed the connection]
tuxd3v has joined #linux-rockchip