Please document how exactly a latest RK3399 Ubuntu rootfs is built

cb182d

Please document how exactly a latest RK3399 Ubuntu rootfs is built

Currently there is a page related to RK3399 rootfs (http://wiki.t-firefly.com/index. ... Build_Ubuntu_rfs/en ) but this is severely out-dated. Following this guide, a system with nearly no working device will be built.

I tried the latest official Xubuntu image and it works well, but when I built my own rootfs with the official document, none of the following devices work properly:
1. Bluetooth
    Possibly missing firmware and /usr/local/bin/enable_bt ?
2. WiFi
    Firmware missing
3. GPU (OpenGL ES, libmali)
    I can see libmali-rk-midgard-dev and libmali-rk-midgard-4th-r13p0 in official Xubuntu rootfs, but copying libEGL.so/libGLESv2.so/etc. to my own rootfs results in "EGLUT: Failed to initialize EGL display" when running es2gears. doing a dpkg-repack results the same.
    Where can I download/create the libmali-rk-midgard-dev & libmali-rk-midgard-4th-r13p0 deb packages? How should them be installed?
4. Sound (rt5640)
    Device shows up, but no sound output.
5. Hardware video decoding

Adding rockchip firmware overlay (https://github.com/rockchip-linux/rk-rootfs-build) on GitHub will get WiFi working, but I googled for hours with no luck for other devices.

cb182d

luvings Posted at 12/12/2017 17:54
The above bug is based on the original rootfs made some changes

I managed to get sound working by restoring an "asound.state" provided by a friend of mine. Others are still not working.
That's not what an open source platform should be like. Everything should be well documented instead of a single Xubuntu img.
I'm also stuck at getting mainline u-boot & u-boot spl working so that I can use extlinux (which is significantly easier to play with & updating mainline kernel) instead of the heavily modified firefly u-boot, and I wonder if I could find some related doc or guide to get this working.
I saw firefly-rk3399 related packages in Debian and openSUSE repos, but there's not even a single doc/guide.

cb182d

Rudis Posted at 12/14/2017 16:02
About GPU (OpenGL ES)
You should link libmali.so\libEGL.so to libmali-rk-midgard-4th-r13p0.so

The "EGLUT: Failed to initialize EGL display" error only ocurred when I linked both files. if I don't do that, it will either use mesa EGL and software rendering, or show an error indicating it cannot load libEGL, if no mesa libEGL is present.

cb182d

Rudis Posted at 12/14/2017 16:02
About GPU (OpenGL ES)
You should link libmali.so\libEGL.so to libmali-rk-midgard-4th-r13p0.so

Actually glmark2-es2-drm is working (full screen), but glmark2-es2 fails with EGLUT 0x3003, which means the display is not initialized, so I think that's some issue related to X11 DDX.

cb182d

Rudis Posted at 12/14/2017 16:02
About GPU (OpenGL ES)
You should link libmali.so\libEGL.so to libmali-rk-midgard-4th-r13p0.so

Well, I found that the official Xubuntu image is using custom X11 server. Maybe missing the (rockchip modified) X11 is the root cause.