<ayaka>
phh, what I know is that, the graphics department have some modification from ARM
<ayaka>
to tuning the performance
afaerber has quit [Quit: Ex-Chat]
nasuga has quit [Ping timeout: 240 seconds]
cnxsoft1 has joined #linux-rockchip
cnxsoft has quit [Ping timeout: 260 seconds]
cnxsoft1 is now known as cnxsoft
cnxsoft has quit [Quit: cnxsoft]
<phh>
so, for veyron suspend, I need to re-power cycle mmc. best way I've found is echo ff0d000.dwmmc > unbind / bind
nasuga has joined #linux-rockchip
nighty has joined #linux-rockchip
matthias_bgg has quit [Quit: Leaving]
afaerber has joined #linux-rockchip
afaerber has quit [Ping timeout: 240 seconds]
afaerber has joined #linux-rockchip
afaerber has quit [Quit: Ex-Chat]
dlezcano has quit [Ping timeout: 260 seconds]
tes has joined #linux-rockchip
tes has left #linux-rockchip [#linux-rockchip]
<akaizen>
phh: these r12p0 user space drivers have a version with Wayland support which is exciting. Does you rk-rootfs-build have an option for wayland or is it x11 only?
<phh>
akaizen: it's quite weird actually. I do see EGL extensions needed for wayland listed, but wayland doesn't work
<phh>
I'll test arm's release to see if wayland works on it
<akaizen>
I'm working on building a new ubuntu 16.04 image for firefly-rk3288 manually, is that repo using build root?
<akaizen>
arm also has a custom kernel, need to diff it against mainline and firefly forks
<phh>
that repo is using deb packages, so you'd be fine to go with it
<phh>
akaizen: the thing is, the arm kernel driver in https://github.com/rockchip-linux/kernel is already using dma-buf, while according to ARM's release it's a new thing of r12. that git mentions it's r9p0. I'm quite lost.
<phh>
I'll check that mali userland on my 4.9-rc4 kernel
<akaizen>
Yea it has x11 stuff in there, is it easy to remove or are there a lot of dependencies? Also what versions are the mali binary drivers? the commit says r9
<akaizen>
seems there some changes from rockchip in that version
<akaizen>
what rk device are you testing with?
<phh>
asus chromebook c201
<akaizen>
and that build root fs is working on it?
<phh>
yup
<akaizen>
ill have to try on firefly-rk3288
<phh>
it has vpu/gpu
<phh>
(though vpu is only h264)
<akaizen>
arm says those binaries should work for asus c201 as well..
<phh>
well I'm guessing rockchip's libmali r12 doesn't check for r12 kernel, but ARM's does
<akaizen>
ah
<akaizen>
it was my understanding it wouldnt work if they didnt match up
<akaizen>
dunno why rk is not using matching kernel + userspace
<akaizen>
also why does build root have gstreamer-vaapi and libva?
<phh>
no clue
<phh>
so, with mali's latest kernel driver, I have the same result as with rockchip's mali kernel (X seem to freeze at startup, but no kernel panic or kernel freeze, though no more usable hid)
<phh>
right the diff between the two versions is really little
<phh>
anyway, now I have my out-of-tree mali_kbase.ko build
* nasuga
longs for tamil driver
<phh>
well, weston and es2gears_wayland works
<phh>
(es2gears_wayland tells me EGL_VERSION = midgard r12p0-04rel0)
<akaizen>
is that wayland direct or wayland on X
<phh>
wayland direct
<akaizen>
awesome sauce
<akaizen>
how is hardware video decoding?
<akaizen>
we might finally have a viable arm platform thats a desktop replacement with a smooth tear free experience
<akaizen>
Btw.. you have build instructions? I'm working on firefly and using my old rootfs and manually patching kernel.. thinking its going to take some time and wondering if theres a faster way
<phh>
I'm not too sure how to test video decoding. i previously was using vlc, but debian's vlc doesn't seem to have a wayland option
<phh>
kwin doesn't work, possibly debian's kwin is built with gl not es...?