• 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 8th November 2011 at http://forums.arm.com

    Hi James,

    thanks for removing the ZBT, I think it should stay removed. I've checked the Driver Development Kit (DDK) documentation and it suggests you should be using the MMU, in which case the OS_MEMORY region flags should be the MMU ones instead - please change the flags from this:


    {
      .type = OS_MEMORY,
      .description = "OS Memory",
      .base = 0x78000000,
      .size = 0x03000000,
      .alloc_order = 10,
      .flags = _MALI_CPU_WRITEABLE | _MALI_CPU_READABLE | _MALI_PP_READABLE | _MALI_PP_WRITEABLE |_MALI_GP_READABLE | _MALI_GP_WRITEABLE,
      .cpu_usage_adjust = 0x00000000
    },


    to this:


      .flags = _MALI_MMU_WRITEABLE | _MALI_MMU_READABLE,


    and check that you are building the kernel module with MMU exanbled (USING_MMU=1). In fact, can you post your current build command?

    I think you have userspace library binaries from your chip provider, but did you also receive a binary mali.ko kernel module? If so it may be possible to check the configuration options used to build it, and use them again for your kernel module.

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

    Hi James,

    thanks for removing the ZBT, I think it should stay removed. I've checked the Driver Development Kit (DDK) documentation and it suggests you should be using the MMU, in which case the OS_MEMORY region flags should be the MMU ones instead - please change the flags from this:


    {
      .type = OS_MEMORY,
      .description = "OS Memory",
      .base = 0x78000000,
      .size = 0x03000000,
      .alloc_order = 10,
      .flags = _MALI_CPU_WRITEABLE | _MALI_CPU_READABLE | _MALI_PP_READABLE | _MALI_PP_WRITEABLE |_MALI_GP_READABLE | _MALI_GP_WRITEABLE,
      .cpu_usage_adjust = 0x00000000
    },


    to this:


      .flags = _MALI_MMU_WRITEABLE | _MALI_MMU_READABLE,


    and check that you are building the kernel module with MMU exanbled (USING_MMU=1). In fact, can you post your current build command?

    I think you have userspace library binaries from your chip provider, but did you also receive a binary mali.ko kernel module? If so it may be possible to check the configuration options used to build it, and use them again for your kernel module.

    Cheers, Pete
Children
No data