steev has quit [Remote host closed the connection]
norris has quit [Remote host closed the connection]
dianders has quit [Remote host closed the connection]
srao has quit [Remote host closed the connection]
ojn has quit [Remote host closed the connection]
cnxsoft has joined #linux-rockchip
johnnyr has quit [Ping timeout: 260 seconds]
johnnyr has joined #linux-rockchip
<naobsd>
on linux-next, dw_hdmi_rockchip.ko is loaded but I cannot see anything in dmesg, is it normal?
robogoat has quit [Ping timeout: 272 seconds]
robogoat has joined #linux-rockchip
markm has joined #linux-rockchip
cnxsoft has quit [Ping timeout: 240 seconds]
kapouer has joined #linux-rockchip
cristian_c has joined #linux-rockchip
<mmind00>
naobsd: are you still on your rk3368? ... there isn't any drm support for it yet
<naobsd>
hm, what's the difference between big and little cores? u-boot set initial freq 816MHz and 600MHz, but RK 3.10 kernel defines max freq is 1008MHz for both
<naobsd>
mmind00: well, sorry, I'm trying drm things on rk3288 boards
<mmind00>
naobsd: big/little: not sure both are a53, but the rockchip kernel I have does specify different frequencies
<naobsd>
I can see vop[bl] and hdmi nodes in rk3288 dtses and multi_v7_defconfig has DRM FB emulation etc
<mmind00>
naobsd: but the drm subsystem probably has not bound
<mmind00>
that patch from sjoerd talks about the drm driver being build as module
<mmind00>
and together with your log looks sensible, as modules get loaded but the probe never seems to finish
<naobsd>
ah
<naobsd>
I thought whole system hangs
<naobsd>
anyway, I'm using modules, patch should be required
<naobsd>
and about rk3368, sorry, I found dvfs tables which defines 1512M for big, 1200M for little
gb_master has joined #linux-rockchip
<naobsd>
about rk3368 dvfs table, voltages are different between b/L on same freq
<naobsd>
hm.
<naobsd>
L cluster should be power efficient of course...
kapouer has quit [Ping timeout: 240 seconds]
<naobsd>
mmind00: btw, rk3368 pll setting seems to be similar to other rk3x
<naobsd>
oops
<naobsd>
I should set lower max freq for rk3288... I often run make -j4 on rk3288, and I get reboot ;)
gb_master has quit [Quit: Leaving]
jas-hacks has joined #linux-rockchip
<naobsd>
mmm...
<naobsd>
nothing seems to be changed with rockchip drm patch...
kapouer has joined #linux-rockchip
<mmind00>
naobsd: can you try to build it in for comparison?
<naobsd>
sure, I'll try
<naobsd>
mmind00: btw is there dmesg with working hdmi?
steev has joined #linux-rockchip
markm has quit [Read error: Connection reset by peer]
markm has joined #linux-rockchip
<mmind00>
naobsd: something along the lines of "dwhdmi-rockchip ff...." telling you it found some sort of controller version
ojn has joined #linux-rockchip
dianders has joined #linux-rockchip
cnxsoft has joined #linux-rockchip
jas-hacks has left #linux-rockchip [#linux-rockchip]
srao has joined #linux-rockchip
cristian_c has quit [Quit: Bye]
cnxsoft has quit [Quit: cnxsoft]
<naobsd>
mmind00: no change in dmesg :(
<naobsd>
CONFIG_DRM_ROCKCHIP=y
<naobsd>
CONFIG_ROCKCHIP_DW_HDMI=y
<mmind00>
naobsd: if you are on -next ... what about CONFIG_ROCKCHIP_PM_DOMAINS ?
<naobsd>
probably io/pm domains are "N"
<naobsd>
CONFIG_ROCKCHIP_PM_DOMAINS
<naobsd>
oops
<naobsd>
# CONFIG_ROCKCHIP_PM_DOMAINS is not set
<mmind00>
try enabling them please
<naobsd>
I see...is there any dts change for it?
norris has joined #linux-rockchip
<naobsd>
ah, rk3288.dtsi has several power-domains = <&power RK3288_PD_VIO> for vop[bl] and hdmi
<naobsd>
mmmmm
<naobsd>
still nothing with CONFIG_ROCKCHIP_PM_DOMAINS=y ...
<naobsd>
nothing with "dmesg | grep power" "dmesg |grep pmu"...?
<naobsd>
pm.c is compiled at least
<naobsd>
and pm_domains.c
jas-hacks has joined #linux-rockchip
jas-hacks has left #linux-rockchip [#linux-rockchip]
cristian_c has joined #linux-rockchip
jas-hacks has joined #linux-rockchip
kapouer has quit [Ping timeout: 252 seconds]
kapouer has joined #linux-rockchip
diego71 has joined #linux-rockchip
<diego71>
Hi. How good is it the support in mainline kernel for rockchip devices? There is a device that can be used as a desktop, and is supported in mainline kernel, for example?
<mmind00>
diego71: anything with a rk3288 cpu is rather well supported [minus device-specific devicetrees that need to be added] ... prime example being the recent avalanche of Rockchip Chromebooks
<diego71>
mmind00: thanks. I was looking at this, but is not clear how well is supported in mainline kernel http://en.t-firefly.com/en/
<mmind00>
diego71: it always depends on what you see as your core functionality ... another example as far as dev-boards go would be Rock2 from Radxa
<mmind00>
diego71: both firefly and rock2 support similar functionality levels
<mmind00>
diego71: including basic graphical output over hdmi
<diego71>
mmind00: basic graphical output over hdmi is good for me. But does they work with mainline kernel?
<diego71>
I'm worried to have some custom kernel, that can't be upgraded in future...
<mmind00>
diego71: and rock2 support is coming into kernel-4.5 (during the merge-window right now)
jas-hacks has left #linux-rockchip [#linux-rockchip]
<diego71>
(some nice wiki page would be nice ;-) )
Xeta has joined #linux-rockchip
<Xeta>
Hi guys, I have a MK 902 II Android box. I'm wondering if it's possible to reinstall it with a Linux OS? If so how do I write and image to the box and which distributations could work?
cristian__c has joined #linux-rockchip
cristian_c has quit [Read error: Connection reset by peer]
libv_ has joined #linux-rockchip
Xeta has quit [Ping timeout: 246 seconds]
libv has quit [Ping timeout: 260 seconds]
cristian__c is now known as cristian_c
mrueg has quit [Remote host closed the connection]
mrueg has joined #linux-rockchip
libv_ is now known as libv
<kapouer>
mmind00: may i ask some help with somewhat-stable ? it outputs a white screen when booting on it on a veyron-speedy
<mmind00>
kapouer: you have the right devicetree, right?
<kapouer>
not sure what this means, however i'm using this build script
<mmind00>
the analogix-stuff seems to have some small panel issues
<kapouer>
white for a second
<kapouer>
then i get some log
<kapouer>
so it works
<mmind00>
great
<kapouer>
the moment it gets white is a bit weird, though
<mmind00>
I see that on jerry too
<mmind00>
I think I remember that the chromeos-people have some boot-off param for the backlight ... that isn't in mainline ... but not 100% sure about that
johnnyr has quit [Ping timeout: 264 seconds]
johnnyr has joined #linux-rockchip
dlezcano has quit [Ping timeout: 250 seconds]
dlezcano has joined #linux-rockchip
c0d3z3r0 has quit [Ping timeout: 240 seconds]
c0d3z3r0 has joined #linux-rockchip
<kapouer>
found root device ! forgot to remember mmcblk1 was mmcblk0 when booting on it
cristian_c has quit [Read error: Connection reset by peer]
cristian_c has joined #linux-rockchip
cristian_c has quit [Read error: Connection reset by peer]
<kapouer>
and finally, i get "Cannot set the DRM interface version" in xorg - otherwise the log is promising
<kapouer>
oh nice, going to try it
<kapouer>
AIGLX enabled, ARMSOC: Driver for ARM Mali... using VT number 1... but then the error i mentioned
<kapouer>
mmind00: the patch do something, but there's still a white flash - much shorter
<mmind00>
I've also just updated the branches to current head state (from the middle of the merge window) ... mmc tuning works nicely ... my uhs1 card at 50MB/s and the emmc at 116MB/s (doubled from before)