[Pkg-Mali-devel] Rockchip t86x drivers

[Wookey]

On 2018-12-19 07:41 +0000, Guillaume Tucker wrote:
> On 19/12/2018 03:22, Wookey wrote:
> > On 2018-12-14 20:57 +0100, Rohan Garg wrote:
> >> * The Firefly RK3399 DTB needs to be adjusted to enable the Mali GPU
> >> * Mali T86x OpenGL libs need to be packaged from here
> >  https://github.com/rockchip-linux/libmali

OK, so I looked at this (a while ago, but got sidetracked).
so they lay out the files like this:
lib/aarch64-linux-gnu:
libmali-midgard-t86x-r13p0-gbm.so
libmali-midgard-t86x-r13p0.so
libmali-midgard-t86x-r13p0-wayland.so
libmali-midgard-t86x-r14p0-fbdev.so
libmali-midgard-t86x-r14p0-gbm.so
libmali-midgard-t86x-r14p0.so
libmali-midgard-t86x-r14p0-wayland.so
libmali-midgard-t86x-r14p0-x11-fbdev.so

lib/arm-linux-gnueabihf:
libmali-midgard-t86x-r13p0-fbdev.so
libmali-midgard-t86x-r13p0.so
libmali-midgard-t86x-r14p0-fbdev.so
libmali-midgard-t86x-r14p0-gbm.so
libmali-midgard-t86x-r14p0.so
libmali-midgard-t86x-r14p0-wayland.so
libmali-midgard-t86x-r14p0-x11-fbdev.so
libmali-midgard-t86x-r9p0.so

whereas the packing I've done mimics the ARM release layout and looks like:
armhf/fbdev:
libEGL.so -> libEGL.so.1
libEGL.so.1 -> libmali.so
libGLESv1_CM.so -> libGLESv1_CM.so.1
libGLESv1_CM.so.1 -> libmali.so
libGLESv2.so -> libGLESv2.so.2
libGLESv2.so.2 -> libmali.so
libOpenCL.so -> libOpenCL.so.1
libOpenCL.so.1 -> libmali.so
libmali.so
liboffline_compiler_api.so

armhf/wayland:
libEGL.so -> libEGL.so.1
libEGL.so.1 -> libmali.so
libGLESv1_CM.so -> libGLESv1_CM.so.1
libGLESv1_CM.so.1 -> libmali.so
libGLESv2.so -> libGLESv2.so.2
libGLESv2.so.2 -> libmali.so
libOpenCL.so -> libOpenCL.so.1
libOpenCL.so.1 -> libmali.so
libgbm.so -> libgbm.so.1
libgbm.so.1 -> libmali.so
libwayland-egl.so -> libwayland-egl.so.1
libwayland-egl.so.1 -> libmali.so
libmali.so
liboffline_compiler_api.so

armhf/X11:
libEGL.so -> libEGL.so.1
libEGL.so.1 -> libmali.so
libGLESv1_CM.so -> libGLESv1_CM.so.1
libGLESv1_CM.so.1 -> libmali.so
libGLESv2.so -> libGLESv2.so.2
libGLESv2.so.2 -> libmali.so
libOpenCL.so -> libOpenCL.so.1
libOpenCL.so.1 -> libmali.so
libmali.so
liboffline_compiler_api.so

I'm struggling a bit to work out which binaries in the rockchip reopo
correspond to the binaries in the ARM layout, and what set of symlinks is correct.
I guesss these:
lib/arm-linux-gnueabihf/libmali-midgard-t86x-r14p0-fbdev.so is
  armhf/fbdev/libmali.so
lib/arm-linux-gnueabihf/libmali-midgard-t86x-r14p0-wayland.so is
  armhf/wayland/libmali.so
Is this one: lib/arm-linux-gnueabihf/libmali-midgard-t86x-r14p0-x11-fbdev.so 
    armhf/X11/libmali.so ?

And what about this: lib/arm-linux-gnueabihf/libmali-midgard-t86x-r14p0-gbm.so ?
libgbm.so is just another symlink to libmali in the ARM release I have, so 
I have no idea what to do with this.

Nor this: lib/arm-linux-gnueabihf/libmali-midgard-t86x-r14p0.so 
This one is bigger (23MB vs 17MB for the others) so maybe this is the real
libmali.so, but in that case what are the others?

And of course same set of questions for arm64 (which seems to have same layout)

So as you can see I am confused. I've not resorted to objdumping to
try and work out what's what. But I got this far and then stopped as
just dumping it into my existing packaging was less straighforward
than I had expected.


Wookey
-- 
Principal hats:  Linaro, Debian, Wookware, ARM
http://wookware.org/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-mali-devel/attachments/20190130/849482e4/attachment.sig>