• Locked Locked
  • Replies 26 replies
  • Subscribers 136 subscribers
  • Views 22467 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
  • Note: This was originally posted on 3rd November 2011 at http://forums.arm.com

    Hi James,

    OK that looks good, there are a few other possibilities I think.

    It must be something fundamental to the very early stages of EGL initialization, so how about the framebuffer. Are you targeting the default Linux framebuffer, /dev/fb0?

    If so does that exist? Do you have the environment variable FRAMEBUFFER set to anything? I would try setting it to /dev/fb0 in case.


    # ls -l /dev/fb0
    crw-rw---- 1 root video 29, 0 2011-10-06 12:10 /dev/fb0
    # export FRAMEBUFFER=/dev/fb0


    If that doesn't help, do you know how your userspace libraries are built? Specifically, they can be built monolithic  where all parts of the driver, EGL, GLESv2 are linked into the same .so file, and all necessary .so files are symlinks to one true file. Sometimes this can cause problems with initialization if the symlinks have become copies of the real file (e.g. on a Windows filesystem not supporting symlinks).

    Also, do you know whether you are using the Unified Memory Provider (UMP)? If so you'd also need a /dev/ump. I think if you are using UMP then you'd have to do:

    insmod ump.ko

    before insmod mali.ko so I suspect you're not but worth checking.

    Cheers, Pete
Reply
  • Note: This was originally posted on 3rd November 2011 at http://forums.arm.com

    Hi James,

    OK that looks good, there are a few other possibilities I think.

    It must be something fundamental to the very early stages of EGL initialization, so how about the framebuffer. Are you targeting the default Linux framebuffer, /dev/fb0?

    If so does that exist? Do you have the environment variable FRAMEBUFFER set to anything? I would try setting it to /dev/fb0 in case.


    # ls -l /dev/fb0
    crw-rw---- 1 root video 29, 0 2011-10-06 12:10 /dev/fb0
    # export FRAMEBUFFER=/dev/fb0


    If that doesn't help, do you know how your userspace libraries are built? Specifically, they can be built monolithic  where all parts of the driver, EGL, GLESv2 are linked into the same .so file, and all necessary .so files are symlinks to one true file. Sometimes this can cause problems with initialization if the symlinks have become copies of the real file (e.g. on a Windows filesystem not supporting symlinks).

    Also, do you know whether you are using the Unified Memory Provider (UMP)? If so you'd also need a /dev/ump. I think if you are using UMP then you'd have to do:

    insmod ump.ko

    before insmod mali.ko so I suspect you're not but worth checking.

    Cheers, Pete
Children
No data