05:15 <wens> mmind00: I spot two custom ioctls in armsoc/rockchip that are not in mainline, one for gem creation and one for setting zpos

05:17 <wens> mmind00: seems we should use DRM_IOCTL_MODE_CREATE_DUMB for the former, and use zpos property for the latter?

05:17 <wens> though zpos doesn't seem to be supported by rockchip yet

08:22 <mmind00> wens: there was a bit of controversy about the create_gem ioctl ... create_dumb is not supposed to be used for acceleration

09:28 <wens> why is that?

09:36 <mmind00> wens: I don't remember to clearly and wasn't able to find the old thread on short notice ... but as far as I remember the "dumb" gems are only to be used for dumb outputs not for something where the acceleration is done

09:37 <mmind00> wens: that wasn't something really relating to embedded graphics, but more steming from the real GPUs where these memory types can be different or so

09:52 <wens> right, like on board or on package GDDR RAM, which is somehow mapped into the processor's memory range

14:46 <wens> it shouldn't matter for armsoc though?

15:29 <Ke> let's say I want to help out a bit, is there a resource in understanding what these image formats are

15:30 <Ke> as in which are handled by libswscaler of ffmpeg

15:30 <mmind00> wens: not really, but drm people were very vocal about not using dumb-buffers in xserver - not sure if that changed since then

15:30 <mmind00> wens: and of course the other side - adding the gem_create - ioctl is dubious, as it's probably not needed with panfrost and lima moving forward

16:06 <wens> I assume lima and panfrost would use custom ioctls (from their drm driver) in mesa to create backing buffers for textures, results, etc.

16:06 <wens> not really familiar with drm+mesa stuff

16:10 <wens> in any case, the armsoc driver only uses create_gem for scanout buffers (including the cursor), so it should be fine

19:33 <rasta234> hello, I am a Yundoo Y8 owner who would like to install a Linux distro on it. Yundoo Y8, as far as I know, has only support for android. But knowing that Y8 is very similar to Firefly RK3399, I have tried to install latest firefly Ubuntu build (Firefly-RK3399-ubuntu16.04-20180416112819.tgz) on it

19:34 <rasta234> amd well, blue light comes and I can see some activity, as example in the ethernet. But HDMI doesn't work

19:35 <rasta234> I have the UART log, let me find it

19:35 <vagrantc> you'll probably need to at least pass it an updated device-tree

19:36 <rasta234> https://pastebin.com/raw/Xhx2S9iG

19:36 <rasta234> i can see some errors on the HDMI:

19:36 <rasta234> [ 1.413003] i2c i2c-9: of_i2c: modalias failure on /hdmi@ff940000/ports [ 1.413605] dwhdmi-rockchip ff940000.hdmi: registered DesignWare HDMI I2C bus driver [ 1.414348] dwhdmi-rockchip ff940000.hdmi: Detected HDMI TX controller v2.11a with HDCP (DWC HDMI 2.0 TX PHY) [ 1.415807] rockchip-drm display-subsystem: bound ff940000.hdmi (ops 0xffffff8008cec920) [ 1.765870] dwhdmi-rockchip ff940000.hdmi: PHY PLL failed

19:37 <rasta234> sorry, I am new to RK3399, what "pass it an updated device-tree" means?

19:38 <vagrantc> the description of exactly what hardware you're using

19:38 <vagrantc> in a format that the linux kernel understands

19:39 <rasta234> the dts files, you mean?

19:41 <vagrantc> yes

19:41 <vagrantc> dts device tree source

19:41 <vagrantc> (or maybe stub?)

19:41 <rasta234> I was looking around to see if there is anything published by yundoo... but I can not find

19:42 <rasta234> I found for NanoPC-T4 and RockPro64... but not for yundoo Y8

19:43 <rasta234> I even compiled the kernel for the NanoPC-T4 for seeing in practice the resource.img compiled on my box

19:44 <rasta234> but, can not find yundoo Y8 kernel resository nor anything similar

19:45 <rasta234> Is a same because with these files I could have my Yundoo Y8 running a clean ubuntu 16.04

19:45 <rasta234> just the HDMI fails :-(

19:46 <rasta234> does anybody know where I could find these files?

19:48 <rasta234> sadly, looks like no...

19:49 <beeble> you can try yo extract the dtb from your android image and see how it differs

19:50 <rasta234> I have the resource.img for Yundoo Y8's official android 7.1 build

19:51 <rasta234> I override the resource partition with this image, but then... it doesnt show the blue light :-P

19:51 <rasta234> android dtb is not compatible with linux dtb :-)

19:51 <rasta234> but...

19:52 <rasta234> how I could extract the dts files from the dtb? is that posible?

19:52 <beeble> dtc -I dtb -O dts <yourandroiddtb>

19:52 <rasta234> any tool for this? :-)

19:52 <rasta234> oh... looks handy

19:52 <rasta234> let me try

19:53 <beeble> devicetree-compiler package if you have a debian/ubuntu host

19:53 <rasta234> yes, I have ubuntu host

19:54 <rasta234> this will take some minutes for me... I'll go idle here for a while

19:55 <beeble> the decompiled devicetree will be flat (hence the name) and will have some convience names from the source missing. but you will still be able to look for differences

19:56 <rasta234> so, the idea here is to get the official RK3399 kernel, compile it and see the diffs of the extracted dts files with the final "merged" dts file used to generate the dtb file

19:57 <rasta234> am I correct ?

19:57 <rasta234> then apply the diffs to the individual, original, dts files and recompile

19:58 <beeble> using rockchips 4.4 kernel will be the most straight forward way as the android image will be based on it. if you say it is similar to firefly you could take that as a template and implement the changes you find in the decompiled

19:59 <rasta234> yes, I compiled already the rockchip-kernel 4.4 branch

19:59 <rasta234> https://github.com/rockchip-linux/kernel

19:59 <rasta234> this one I compiled

20:01 <rasta234> since t-firefly.com is down is very hard to find now any documentation

20:04 <rasta234> is this also the 4.4? https://github.com/54shady/firefly_rk3399_kernel

20:05 <beeble> the rockchip-linux one should be fine

20:06 <rasta234> ok, I'll focus in that one, then

20:15 <rasta234> I got some warnings from dtc -I dtb -O dts -o Y8.dts /home/me/rk-kernel-Y8.dtb

20:16 <rasta234> Y8.dts: Warning (unit_address_vs_reg): Node /usb@fe800000 has a unit name, but no reg property

20:16 <rasta234> Y8.dts: Warning (unit_address_vs_reg): Node /usb@fe900000 has a unit name, but no reg property

20:16 <beeble> you can ignore that for now

20:16 <rasta234> ok

20:17 <rasta234> I got a shiny dts file, yes

20:19 <rasta234> what commands should I execute for building the kernel at https://github.com/rockchip-linux/kernel ? sorry for this question :-)

20:20 <beeble> http://opensource.rock-chips.com/wiki_Rockchip_Kernel

20:34 <rasta234> here I have a very good guide: http://wiki.friendlyarm.com/wiki/index.php/NanoPC-T4#Make_Your_Own_OS_Image

20:34 <rasta234> just executing the commands at http://opensource.rock-chips.com/wiki_Rockchip_Kernel

20:35 <rasta234> but the dependencies are nicely explained in friendlyarm's wiki :-)

20:40 <rasta234> I don't think I will have time to finish this task today... If I am not able to compile the kernel 4.4 for Yundoo Y8 with the precious info you have given then I will come back for more, otherwise, if I am able to compile it and make the Yundoo Y8 work with the firefly ubuntu 16.04 + custom resource.img, Then I will document the whole thing here:

20:40 <rasta234> http://freaktab.com/forum/tv-player-support/rockchip-based-tv-players/rk3399-devices/741954-yundoo-y8-ubuntu

20:41 <rasta234> i am that guy (isaauco), so i'll finish that thread when I am done

20:41 <beeble> good luck

20:41 <rasta234> maybe I see you again tomorrow :-)

20:41 <rasta234> thanks for the help and the cheering :-)

20:51 <rasta234> BTW, device-tree-compiler was the package name, but the tools at kernel-rockchip/scripts/dtc folder worked ok :-) thanks again

20:52 <vagrantc> dtc was already packaged in debian as something else entirely

20:53 <rasta234> those packagers... :)

20:55 <rasta234> bye