• Locked Locked
  • Replies 26 replies
  • Subscribers 137 subscribers
  • Views 23665 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

How could I make sure the driver work success?

Bor-Yih Chiang
Note: This was originally posted on 3rd November 2011 at http://forums.arm.com

Dear all,

I'm trying to build linux Mali200 driver in arm system.
I build mali.ko and insert it success in linux.
The attachment is log when I insert module.
It always told me "Mali device driver r2p2-03rel0 loaded".

Would you please tell me how could I make sure the driver work success?
Because I try to run the SimpleProject.
It always get the error message "Error: No EGL Display available at src/egl_runtime.c:64"

thanks.

James
Parents
  • Arm Employee Badge
    Note: This was originally posted on 9th November 2011 at http://forums.arm.com

    Hi James,

    the build command and config.h both look OK. I will look into the driver source to check other possible causes of EGL_BAD_ALLOC during eglInitialize().

    Have you checked that the config.h you are editing is the  file being used for compilation? You could check by temporarily adding an error:


    #error "Checking config.h"


    Do you know the framebuffer is working OK? For example, if you do:


    cat /bin/sh > /dev/fb


    do you see random colors appear on the display?

    If mtekvision have supplied the userspace binary library files (lib*.so) are they also able to provide you with a known working driver kernel module (mali.ko)?

    Cheers, Pete
Reply
  • Arm Employee Badge
    Note: This was originally posted on 9th November 2011 at http://forums.arm.com

    Hi James,

    the build command and config.h both look OK. I will look into the driver source to check other possible causes of EGL_BAD_ALLOC during eglInitialize().

    Have you checked that the config.h you are editing is the  file being used for compilation? You could check by temporarily adding an error:


    #error "Checking config.h"


    Do you know the framebuffer is working OK? For example, if you do:


    cat /bin/sh > /dev/fb


    do you see random colors appear on the display?

    If mtekvision have supplied the userspace binary library files (lib*.so) are they also able to provide you with a known working driver kernel module (mali.ko)?

    Cheers, Pete
Children
No data