Firefly New DualBoot Firmware Release（Beta）

Asuuga · Posted at 6/17/2016 17:12:54

This looks cool ! I wiil test it !

Asuuga · Posted at 6/17/2016 22:10:00

Hello Isle,

Thanks for your hard work !

I'd like to ask you some questions :

In this image, the node /dev/dri/card0 exists whereas in the previous ones, it didn't.
What driver is responsible for exporting this node ?

You used armsoc for the X11 graphic driver which is, I believe, an open source driver. Wouldn't the closed source X11 driver from ARM itself work better ?

Also, my screen (hdmi) regularly blacks out, for 1-2 seconds.

Asuuga · Posted at 6/20/2016 18:50:21

So you replaced the userspace DRM library (libdrm) ? Or is it the kernel DRM driver?
Happy that you will open the source code !

I suppose you already tested the ARM driver. Did it work ?

For the HDMI, it is as if the signal was broke for a very small period of time. It is however enough for my screen to lose the signal, and it takes a couple of seconds for the image to get back on the screen. Nothing seems to appear in the kernel logs.

Concerning the VPU, you said that it was not working at full power and that kodi can't work smoothly. Do you know what is the cause of the problem ? If I can help you, I would be very pleased to do so !

Again, thanks for still sworking on this chip !

Asuuga · Posted at 6/24/2016 17:44:59

ujerry Posted at 6/21/2016 11:32
Userspace DRM library and kernel DRM driver are both needed , notice that userspace DRM library nee ...

Hi uJerry,

I don't understand why you say that ARM's driver only support mali4xx. ARM's x11 driver can support the mali76X according this page : http://malideveloper.arm.com/res ... user-space-drivers/ (release r6p0-02rel0 for Firefly). Or I misunderstood ?

I wiil try to monitor udevadm for the HDMI problem and tell you the results.

Also, I experience the same problem than andrewsmithty with the mouse (and also keyboard).

Thanks !

Asuuga · Posted at 6/27/2016 18:47:42

Last edited by Asuuga In 6/27/2016 18:54 Editor

mac-l1 Posted at 6/24/2016 07:11
Hi guys,

Just made a prelimary kodi release for this ubuntu image. This has GPU working at 60 f ...

Hi mac-l1,

I tested your last version of kodi and it's working great !

It succesfully decoded a 1080p hevc video flawlessly. There was just sometime some jitter in the sound.
Audio through HDMI was also working.
I also tested a 4k hevc video, but it didn't work well, as the decoding was very slow.

Hi uJerry,

Ah ok, thank you for the explanation on the graphics stack architecture !
I'm sorry I can't reproduce the mouse and keyboard bug anymore... It is working fine now.

And isle, thank you for releasing the kernel source code

Asuuga · Posted at 6/30/2016 21:10:32

Last edited by Asuuga In 6/30/2016 23:37 Editor

Hi mac-l1,

I also have an original firefly. This is what i get in the kernel logs about hdmi-audio :

ubuntu@firefly:~$ dmesg | grep hdmi
[ 2.930992] rockchip-hdmi-audio hdmi_audio.6: ASoC: CODEC dw-hdmi-audio not registered
[ 2.931010] rockchip-hdmi-audio hdmi_audio.6: register card failed (-517)
[ 2.931017] platform hdmi_audio.6: Driver rockchip-hdmi-audio requests probe deferral
[ 3.974254] rockchip-hdmi-audio hdmi_audio.6: ASoC: CODEC dw-hdmi-audio not registered
[ 3.982201] rockchip-hdmi-audio hdmi_audio.6: register card failed (-517)
[ 3.989004] platform hdmi_audio.6: Driver rockchip-hdmi-audio requests probe deferral
[ 4.019681] rockchip-hdmi-audio hdmi_audio.6: ASoC: CODEC dw-hdmi-audio not registered
[ 4.027607] rockchip-hdmi-audio hdmi_audio.6: register card failed (-517)
[ 4.034414] platform hdmi_audio.6: Driver rockchip-hdmi-audio requests probe deferral
[ 4.060459] dwhdmi-rockchip ff980000.hdmi: Detected HDMI controller 0x20:0xa:0xa0:0xc1
[ 4.068383] dwhdmi-rockchip ff980000.hdmi: Detected HDMI config_id 0xbf:0x22:0xc2:0x0
[ 4.094664] dwhdmi-rockchip ff980000.hdmi: monitor does not support audio
[ 4.101573] dw-hdmi-audio dw-hdmi-audio: hdmi audio init success.
[ 4.107676] rockchip-drm display-subsystem.4: bound ff980000.hdmi (ops dw_hdmi_rockchip_ops)
[ 4.313451] dw-hdmi-audio dw-hdmi-audio: jack report [4]
[ 4.320387] rockchip-hdmi-audio hdmi_audio.6: dw-hdmi-hifi <-> ff890000.i2s mapping ok
[ 4.328780] input: RockchipHDMI HDMI Jack as /devices/hdmi_audio.6/sound/card1/input4
[ 4.345253] rockchip-hdmi-audio hdmi_audio.6: hdmi audio init success.
[ 32.060181] dw-hdmi-audio dw-hdmi-audio: startup.
[ 32.078179] dw-hdmi-audio dw-hdmi-audio: shutdown.
[ 32.088048] dw-hdmi-audio dw-hdmi-audio: startup.
[ 32.097945] dw-hdmi-audio dw-hdmi-audio: [codec_dai]: trigger enable.
[ 37.626900] dw-hdmi-audio dw-hdmi-audio: [codec_dai]: trigger disable.
[ 37.627695] dw-hdmi-audio dw-hdmi-audio: shutdown.

Copy the code

So the driver probes correctly the hardware for me.

Also, you can control audio with pavucontrol.
In the "Configuration" tab, I have 2 items : "RockchipHDMI" (obviously, for hdmi output) and "RK_ES8323" (for jack output). I selected the profile from the first one to "Digital Stereo (HDMI) Output" whereas I set the second one to "Off". If both are activated at the same time, sound is only through the jack output and jitters a lot. So I have to activate only one at a time.

When I activate the profile on RockchipHDMI : the following kernel logs appear :

[ 208.952332] dw-hdmi-audio dw-hdmi-audio: startup.
[ 208.952732] dw-hdmi-audio dw-hdmi-audio: [codec_dai]: trigger enable.

Copy the code

When I deactivate it :

[ 462.242270] dw-hdmi-audio dw-hdmi-audio: [codec_dai]: trigger disable.
[ 462.242973] dw-hdmi-audio dw-hdmi-audio: shutdown.

Copy the code

About the sdcard problem :
There is no firefly-rk3288.dts in arch/arm/boot (in the kernel sources). So I suppose the kernel has been built with the device-tree from firefly-reload (firefly-rk3288-reload.dts), which is present. Am I correct uJerry ?
And if you look in this file, you'll see that the sdmmc node is disabled. So the hardware is never being probed and is thus not available. I wonder why they deactivated it ? Maybe it was not working correctly.

Finally, I noticed another problem : the rtc is not working. But again, there is no node that describes it in the device tree.

ubuntu@firefly:~$ dmesg | grep rtc
[ 4.483768] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)

Copy the code

About the vpu support, do you plan to use the kernel driver located in arch/arm/mach-rockchip/vcodec_service.c ? Or rather use a libhybris solution ?

Asuuga · Posted at 7/5/2016 16:01:47

mac-l1 Posted at 7/2/2016 00:04
hi ujerry, asuuga,

great that you are working on this! tnx!

Hi mac-l1,

Thank you for your answer.
About solution 2, you managed to do your decoding just by looking in the vcodec source code ? Also, I believe that you are aware of this github repository : https://github.com/rockchip-linux/ffmpeg. For what I understood, this code and the libraries given are for Linux (there is even an X11 decode example). But I don't know which kernel drivers are needed. What do you think we are lacking to run this code properly ?

About solution 3, we also need proprietary userspace libraries from Rockchip, correct ?

And a more general question for the Firefly team : why are you using a 3.14 kernel as the development from Rockchip seems to be focusing on 4.4 (https://github.com/rockchip-linux/kernel) ?

Thank you !

Asuuga · Posted at 7/5/2016 20:08:17

isle Posted at 7/5/2016 16:40
Hi Asuuga
we are using 3.14 kernel because It's more stable than 4.4, It is base on rockchip' ...

Ok, thank you isle !