• Locked Locked
  • Replies 2 replies
  • Subscribers 136 subscribers
  • Views 4564 views
  • Users 0 members are here
Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Unable to benefit from Mali 400 within Android

Derek Gordon
Note: This was originally posted on 19th January 2013 at http://forums.arm.com

We have Linux kernel 2.6.34 compiled with Mali and UMP modules.  We have not had compile errors.  Everything completes fine.  These modules are initialized within the init.rc when Android 4.0.4 starts. 

However, there appears to be no benefit from the GPU.  Applications still rely on the CPU and HD video and games are quite choppy because of this issue.

Could anyone provide me with a starting point for determining what is prohibiting the Mali 400 GPU from being utilized within Android?


Thank you very much in advance.
Parents
  • Note: This was originally posted on 20th January 2013 at http://forums.arm.com


    Hi derekcentrico,


    The kernel space modules (.ko's) only work in conjunction with userspace libraries (.so's) such as libGLESv2.so and libEGL.so, which expose the GLES and EGL APIs respectively. Do your applications use these libraries, and if so are they present on the target device? If your target device is a commercial one such as a phone or tablet then they will ship with these drivers present in the filesystem, but if you are working on a development board or a custom build of Android then this may not be the case. Can I ask what device you are having trouble with?

    Thanks,
    Chris


    Thanks for the quick reply.  First, we're developing the device running Android 4.0.4 and not applications.  Sorry if my short comment implied otherwise.

    As far as EGL drivers, we have the following:
    • [size=2]libEGL_mali.so[/size]
    • [size=2]libEGLS_android.so[/size]
    • [size=2]libEGLSv1_CM_mali.so[/size]
    • [size=2]libEGLv2_mali.so[/size]

    Our egl.cfg provides for:


    #0 0 android
    0 1 mali



    We load the mali.ko and ump.co using init.rc with the following at the very beginning:


    insmod /system/lib/modules/ump.ko
    insmod /system/lib/modules/mali.ko



    The kernel does have mali and ump enabled.

    I'm not sure what else I can provide for. 

    Thanks for any possible advise.
Reply
  • Note: This was originally posted on 20th January 2013 at http://forums.arm.com


    Hi derekcentrico,


    The kernel space modules (.ko's) only work in conjunction with userspace libraries (.so's) such as libGLESv2.so and libEGL.so, which expose the GLES and EGL APIs respectively. Do your applications use these libraries, and if so are they present on the target device? If your target device is a commercial one such as a phone or tablet then they will ship with these drivers present in the filesystem, but if you are working on a development board or a custom build of Android then this may not be the case. Can I ask what device you are having trouble with?

    Thanks,
    Chris


    Thanks for the quick reply.  First, we're developing the device running Android 4.0.4 and not applications.  Sorry if my short comment implied otherwise.

    As far as EGL drivers, we have the following:
    • [size=2]libEGL_mali.so[/size]
    • [size=2]libEGLS_android.so[/size]
    • [size=2]libEGLSv1_CM_mali.so[/size]
    • [size=2]libEGLv2_mali.so[/size]

    Our egl.cfg provides for:


    #0 0 android
    0 1 mali



    We load the mali.ko and ump.co using init.rc with the following at the very beginning:


    insmod /system/lib/modules/ump.ko
    insmod /system/lib/modules/mali.ko



    The kernel does have mali and ump enabled.

    I'm not sure what else I can provide for. 

    Thanks for any possible advise.
Children
No data