ChanServ changed the topic of #linux-rockchip to: Rockchip development discussion | IRC log | Community GH | Rockchip GH | ML
vagrantc has quit [Ping timeout: 252 seconds]
vagrantc has joined #linux-rockchip
vstehle has quit [Ping timeout: 252 seconds]
vicencb has quit [Quit: Leaving.]
adjtm has quit [Read error: Connection reset by peer]
adjtm has joined #linux-rockchip
cnxsoft has joined #linux-rockchip
vagrantc has quit [Quit: leaving]
return0xe has quit [Ping timeout: 244 seconds]
return0e has joined #linux-rockchip
vstehle has joined #linux-rockchip
<wens> mmind00: I spot two custom ioctls in armsoc/rockchip that are not in mainline, one for gem creation and one for setting zpos
<wens> mmind00: seems we should use DRM_IOCTL_MODE_CREATE_DUMB for the former, and use zpos property for the latter?
<wens> though zpos doesn't seem to be supported by rockchip yet
kaspter has quit [Remote host closed the connection]
kaspter has joined #linux-rockchip
ganbold has quit [Ping timeout: 272 seconds]
kaspter has quit [Remote host closed the connection]
<mmind00> wens: there was a bit of controversy about the create_gem ioctl ... create_dumb is not supposed to be used for acceleration
kaspter has joined #linux-rockchip
<wens> why is that?
<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
<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
<wens> right, like on board or on package GDDR RAM, which is somehow mapped into the processor's memory range
lkcl has joined #linux-rockchip
adjtm has quit [Ping timeout: 252 seconds]
adjtm has joined #linux-rockchip
_whitelogger has joined #linux-rockchip
LargePrime has joined #linux-rockchip
cnxsoft has quit [Quit: cnxsoft]
JohnDoe_71Rus has joined #linux-rockchip
vicencb has joined #linux-rockchip
<wens> it shouldn't matter for armsoc though?
LargePrime has quit [Ping timeout: 244 seconds]
vicencb has quit [Quit: Leaving.]
cnxsoft has joined #linux-rockchip
LargePrime has joined #linux-rockchip
cnxsoft has quit [Quit: cnxsoft]
LargePrime has quit [Quit: Leaving]
_whitelogger has joined #linux-rockchip
<Ke> let's say I want to help out a bit, is there a resource in understanding what these image formats are
<Ke> as in which are handled by libswscaler of ffmpeg
<mmind00> wens: not really, but drm people were very vocal about not using dumb-buffers in xserver - not sure if that changed since then
<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
lkcl has quit [Ping timeout: 252 seconds]
<wens> I assume lima and panfrost would use custom ioctls (from their drm driver) in mesa to create backing buffers for textures, results, etc.
<wens> not really familiar with drm+mesa stuff
<wens> in any case, the armsoc driver only uses create_gem for scanout buffers (including the cursor), so it should be fine
lkcl has joined #linux-rockchip
JohnDoe_71Rus has quit [Ping timeout: 252 seconds]
return0e has quit [Remote host closed the connection]
vagrantc has joined #linux-rockchip
adjtm has quit [Remote host closed the connection]
adjtm has joined #linux-rockchip
adjtm has quit [Ping timeout: 272 seconds]
vicencb has joined #linux-rockchip
rasta234 has joined #linux-rockchip
<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
<rasta234> amd well, blue light comes and I can see some activity, as example in the ethernet. But HDMI doesn't work
<rasta234> I have the UART log, let me find it
<vagrantc> you'll probably need to at least pass it an updated device-tree
<rasta234> i can see some errors on the HDMI:
<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
<rasta234> sorry, I am new to RK3399, what "pass it an updated device-tree" means?
<vagrantc> the description of exactly what hardware you're using
<vagrantc> in a format that the linux kernel understands
<rasta234> the dts files, you mean?
<vagrantc> yes
<vagrantc> dts device tree source
<vagrantc> (or maybe stub?)
<rasta234> I was looking around to see if there is anything published by yundoo... but I can not find
<rasta234> I found for NanoPC-T4 and RockPro64... but not for yundoo Y8
<rasta234> I even compiled the kernel for the NanoPC-T4 for seeing in practice the resource.img compiled on my box
<rasta234> but, can not find yundoo Y8 kernel resository nor anything similar
<rasta234> Is a same because with these files I could have my Yundoo Y8 running a clean ubuntu 16.04
<rasta234> just the HDMI fails :-(
<rasta234> does anybody know where I could find these files?
<rasta234> sadly, looks like no...
<beeble> you can try yo extract the dtb from your android image and see how it differs
<rasta234> I have the resource.img for Yundoo Y8's official android 7.1 build
<rasta234> I override the resource partition with this image, but then... it doesnt show the blue light :-P
<rasta234> android dtb is not compatible with linux dtb :-)
<rasta234> but...
<rasta234> how I could extract the dts files from the dtb? is that posible?
<beeble> dtc -I dtb -O dts <yourandroiddtb>
<rasta234> any tool for this? :-)
<rasta234> oh... looks handy
<rasta234> let me try
<beeble> devicetree-compiler package if you have a debian/ubuntu host
<rasta234> yes, I have ubuntu host
<rasta234> this will take some minutes for me... I'll go idle here for a while
<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
<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
<rasta234> am I correct ?
<rasta234> then apply the diffs to the individual, original, dts files and recompile
<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
<rasta234> yes, I compiled already the rockchip-kernel 4.4 branch
<rasta234> this one I compiled
<rasta234> since is down is very hard to find now any documentation
<rasta234> is this also the 4.4?
<beeble> the rockchip-linux one should be fine
<rasta234> ok, I'll focus in that one, then
<rasta234> I got some warnings from dtc -I dtb -O dts -o Y8.dts /home/me/rk-kernel-Y8.dtb
<rasta234> Y8.dts: Warning (unit_address_vs_reg): Node /usb@fe800000 has a unit name, but no reg property
return0e has joined #linux-rockchip
<rasta234> Y8.dts: Warning (unit_address_vs_reg): Node /usb@fe900000 has a unit name, but no reg property
<beeble> you can ignore that for now
<rasta234> ok
<rasta234> I got a shiny dts file, yes
<rasta234> what commands should I execute for building the kernel at ? sorry for this question :-)
lkcl has quit [Read error: Connection reset by peer]
lkcl has joined #linux-rockchip
<rasta234> just executing the commands at
<rasta234> but the dependencies are nicely explained in friendlyarm's wiki :-)
<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:
<rasta234> i am that guy (isaauco), so i'll finish that thread when I am done
<beeble> good luck
<rasta234> maybe I see you again tomorrow :-)
<rasta234> thanks for the help and the cheering :-)
adjtm has joined #linux-rockchip
<rasta234> BTW, device-tree-compiler was the package name, but the tools at kernel-rockchip/scripts/dtc folder worked ok :-) thanks again
<vagrantc> dtc was already packaged in debian as something else entirely
<rasta234> those packagers... :)
<rasta234> bye
rasta234 has quit [Quit: Page closed]
lkcl has quit [Ping timeout: 252 seconds]
asciilifeform has joined #linux-rockchip