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?

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

Pete over 11 years ago

Note: This was originally posted on 8th November 2011 at http://forums.arm.com

Hi James,

without knowing the specifics of that board I can't be certain, but I suspect the config.h you have is not set up correctly for the board's memory layout. In particular, I think the ZBT memory may be causing problems - I'm not sure it's physically present on your board. Since it's been given a lower number in config.h, the driver will use that memory area first. If doing a malloc() in that memory area is failing that might explain the EGL_BAD_ALLOC error message.

Please can you try commenting out that section:

/* removing ZBT { .type = MEMORY, .description = "Mali ZBT", .alloc_order = 5, .base = 0x0FE00000, .size = 0x00100000, .flags = _MALI_CPU_WRITEABLE | _MALI_CPU_READABLE | _MALI_PP_READABLE | _MALI_PP_WRITEABLE | _MALI_GP_READABLE | _MALI_GP_WRITEABLE }, */

The config.h will still give the driver an Operating System (OS) allocation of memory of 0x03000000 (48MB).

The framebuffer validation area looks OK. Are you certain the hardware base addresses are correct? E.g.:

.type = MALI200, .base = 0xC7000000,

.description = "MALI GP2", .base = 0xC7002000,

.type = MMU, .base = 0xC7003000,

Did you get this information from the chip provider? It looks as though the Mali is being initialized correctly by the kernel driver messages but I wanted to check.

Thanks, Pete
Cancel
Up 0 Down

Cancel

Reply

Pete over 11 years ago

Note: This was originally posted on 8th November 2011 at http://forums.arm.com

Hi James,

without knowing the specifics of that board I can't be certain, but I suspect the config.h you have is not set up correctly for the board's memory layout. In particular, I think the ZBT memory may be causing problems - I'm not sure it's physically present on your board. Since it's been given a lower number in config.h, the driver will use that memory area first. If doing a malloc() in that memory area is failing that might explain the EGL_BAD_ALLOC error message.

Please can you try commenting out that section:

/* removing ZBT { .type = MEMORY, .description = "Mali ZBT", .alloc_order = 5, .base = 0x0FE00000, .size = 0x00100000, .flags = _MALI_CPU_WRITEABLE | _MALI_CPU_READABLE | _MALI_PP_READABLE | _MALI_PP_WRITEABLE | _MALI_GP_READABLE | _MALI_GP_WRITEABLE }, */

The config.h will still give the driver an Operating System (OS) allocation of memory of 0x03000000 (48MB).

The framebuffer validation area looks OK. Are you certain the hardware base addresses are correct? E.g.:

.type = MALI200, .base = 0xC7000000,

.description = "MALI GP2", .base = 0xC7002000,

.type = MMU, .base = 0xC7003000,

Did you get this information from the chip provider? It looks as though the Mali is being initialized correctly by the kernel driver messages but I wanted to check.

Thanks, Pete
Cancel
Up 0 Down

Cancel

Children

No data