ChanServ changed the topic of #linux-rockchip to: Rockchip development discussion
vagrantc has quit [Quit: leaving]
stikonas has quit [Ping timeout: 252 seconds]
kevery1 has joined #linux-rockchip
kevery has quit [Ping timeout: 272 seconds]
kevery1 is now known as kevery
camus has quit [Quit: camus]
camus has joined #linux-rockchip
kevery1 has joined #linux-rockchip
kevery has quit [Ping timeout: 255 seconds]
kevery1 is now known as kevery
Daanct12 has joined #linux-rockchip
kevery1 has joined #linux-rockchip
kevery has quit [Ping timeout: 250 seconds]
kevery1 is now known as kevery
dlezcano has quit [Ping timeout: 276 seconds]
Daanct12 has quit [Remote host closed the connection]
dlezcano has joined #linux-rockchip
lurchi__ has joined #linux-rockchip
lurchi_ has quit [Ping timeout: 250 seconds]
hanetzer has joined #linux-rockchip
camus1 has joined #linux-rockchip
camus has quit [Ping timeout: 250 seconds]
camus1 is now known as camus
kevery1 has joined #linux-rockchip
kevery has quit [Ping timeout: 250 seconds]
kevery1 is now known as kevery
tor has joined #linux-rockchip
jagan has quit [Ping timeout: 272 seconds]
kevery1 has joined #linux-rockchip
kevery has quit [Remote host closed the connection]
kevery1 is now known as kevery
ldevulder has quit [Quit: Leaving]
ldevulder has joined #linux-rockchip
kevery1 has joined #linux-rockchip
kevery has quit [Ping timeout: 250 seconds]
kevery1 is now known as kevery
Daanct12 has joined #linux-rockchip
Daaanct12 has joined #linux-rockchip
warpme___ has joined #linux-rockchip
Daanct12 has quit [Ping timeout: 250 seconds]
kevery has quit [Ping timeout: 272 seconds]
kevery has joined #linux-rockchip
kevery1 has joined #linux-rockchip
kevery has quit [Ping timeout: 272 seconds]
kevery1 is now known as kevery
stikonas has joined #linux-rockchip
macromorgan has quit [Read error: Connection reset by peer]
mort has joined #linux-rockchip
<mort> does anyone know what happened to the rockchip-linux github org?
<mort> or, why certain repos were deleted I mean; such as the tools repo
camus has quit [Ping timeout: 240 seconds]
camus has joined #linux-rockchip
<CounterPumpkin> They updated some stuff recently, namely kernel and rkbin, they might've done a spring cleaning in the process
naoki has quit [Quit: naoki]
naoki has joined #linux-rockchip
kevery has quit [Ping timeout: 240 seconds]
kevery has joined #linux-rockchip
minimal has joined #linux-rockchip
kevery1 has joined #linux-rockchip
kevery has quit [Ping timeout: 250 seconds]
kevery1 is now known as kevery
a1batross has joined #linux-rockchip
kevery1 has joined #linux-rockchip
kevery has quit [Ping timeout: 250 seconds]
kevery1 is now known as kevery
jagan has joined #linux-rockchip
macromorgan has joined #linux-rockchip
kevery1 has joined #linux-rockchip
kevery has quit [Ping timeout: 260 seconds]
kevery1 is now known as kevery
kevery1 has joined #linux-rockchip
kevery has quit [Ping timeout: 260 seconds]
kevery1 is now known as kevery
jagan has quit [Ping timeout: 240 seconds]
vagrantc has joined #linux-rockchip
kevery has quit [Ping timeout: 272 seconds]
kevery has joined #linux-rockchip
digetx has quit [Ping timeout: 250 seconds]
digetx has joined #linux-rockchip
tor has quit [Quit: Leaving]
minimal has quit [Quit: Leaving]
<CounterPumpkin> macromorgan: did you see someone's post on the mailing list about dsi troubles?
<macromorgan> yes, I responded. It's an unset PLL_VPLL clock most likely (if you don't set it, it runs at 24MHz)
<macromorgan> pixel clock on the Pi panel is ~26MHz. So need to set PLL_VPLL to a supported frequency that has a factor very close to the pixel clock of the panel and that should fix it
<macromorgan> happens on mainline because mainline is forbidden to change the parent clock, while the BSP driver has no such restriction
<macromorgan> I tried to roll that back and was told it's not broken, since you shouldn't be able to change a PLL clock like that... was told the correct solution was to hard code the PLL_VPLL rate so that's what I do (and what needs to be done here)
<CounterPumpkin> yeah I generally agree with that commit's reasoning
<macromorgan> yep... I have no opinion one way or the other, as a novice I just do what I'm told by the big boys and girls ;-)
kevery1 has joined #linux-rockchip
kevery has quit [Read error: Connection reset by peer]
kevery1 is now known as kevery
kevery1 has joined #linux-rockchip
kevery has quit [Ping timeout: 240 seconds]
kevery1 is now known as kevery
kevery1 has joined #linux-rockchip
kevery has quit [Remote host closed the connection]
kevery1 is now known as kevery
kevery1 has joined #linux-rockchip
kevery has quit [Remote host closed the connection]
kevery1 is now known as kevery
Danct12 has quit [Remote host closed the connection]
kevery has quit [Ping timeout: 240 seconds]
kevery has joined #linux-rockchip
kevery1 has joined #linux-rockchip
kevery has quit [Remote host closed the connection]
kevery1 is now known as kevery
minimal has joined #linux-rockchip
Danct12 has joined #linux-rockchip