• Locked Locked
  • Replies 26 replies
  • Subscribers 136 subscribers
  • Views 22455 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 9th November 2011 at http://forums.arm.com

    Hi James,

    I agree, the framebuffer looks like it is working as expected.

    That's interesting news about the config.h though, I think that means the config.h you are editing is not the one being used by the build system.

    Can you run the following command in the driver kernel module source tree:


    find . -name "config.h"


    to find where all the files named config.h are in the source tree?

    If there are several, perhaps you can add a different  #error string to each, then rebuild (probably do a clean before, as well) to see which file is being used. Then you can make the changes to that config.h file and check the log output from insmod.

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

    Hi James,

    I agree, the framebuffer looks like it is working as expected.

    That's interesting news about the config.h though, I think that means the config.h you are editing is not the one being used by the build system.

    Can you run the following command in the driver kernel module source tree:


    find . -name "config.h"


    to find where all the files named config.h are in the source tree?

    If there are several, perhaps you can add a different  #error string to each, then rebuild (probably do a clean before, as well) to see which file is being used. Then you can make the changes to that config.h file and check the log output from insmod.

    Cheers, Pete
Children
No data