mali r5p0-06rel0 odroidxu3

Hi moon.linux,

The general rule for upgrading the Mali driver from an existing BSP is as follows:

• Obtain the Kernel source-code for the device you are targeting (Odroid XU3 in your instance)
• Pull the integration platform files from the Mali Kernel side component of the kernel sources
  • Location and file names may vary so cannot be described here. Roughly speaking, you should find it in a folder called 'platform' within the mali directory in the kernel
• Remove the existing Mali Kernel side component from the kernel sources
• Replace it with the Mali Kernel side component that matches your desired Driver Version from here (r5p0-06rel0 in your instance):
  • Mali Drivers
• Reintegrate the Mali Kernel side component using the integration platform files you previously obtained
• Rebuild the kernel and optional modules needed
  • WARNING! Some further patching may be required at this stage to build Mali successfully...
• Flash the new kernel and replace any kernel modules (if applicable)
• Replace the existing Mali Userspace component (usually libGLES_mali.so or similar) with the matching Driver Version obtained from here:
  • Mali GPU User-Space Binary Drivers

Basically the Kernel Side and User Side components of the Mali Driver 'should' match, and must be for the targeted GPU and OS.

In your instance, you are looking for the Mali-T628 drivers, for Linux. (We do not currently provide Android versions for that GPU)

You also mention that you use the 'chromebook-platform' patch... I cannot say for certain if this will work for the XU3 as it was specifically for the Chromebooks, and hasn't been tested.

If you have specific issues, please give us as much information as you can, and we can try help further.

I hope this overview is sufficient for you to progress however.

Kind Regards,

Michael McGeagh

Regarding your first question about clk_mali, I will ask our resident expert guillaume.tucker if he has any suggestions regarding this.

Regarding your patch question, that depends on what the patch affects. For example if it is a patch in our Mali Kernel Side component, then we should look into that. If however it affects the kernel, or the integration files, then you should contact Hard Kernel in this instance.

Kind Regards,

Michael McGeagh

ARM-software/linux at odroidxu3-3.10.y-mali-midgard-r5p0 · GitHub

It's good to hear that ODROID-XU3 is getting into mainline although I don't expect this to have the Mali GPU driver integrated, unless it's on a HardKernel branch, so the easiest thing to do is still to stick to this 3.10 kernel.

Best regards,

Guillaume

https://review.tizen.org/git/?p=platform/kernel/linux-exynos.git;a=summary

I know tizen 3.0 binary developing is released daily as snapshot binary.

http://download.tizen.org/snapshots/tizen

I used tizen 3.0 tv profile binary for odroid xu3 board.

http://download.tizen.org/snapshots/tizen/tv/latest/

You need to use tizen u-boot to run tizen on odroid xu3 board

Please refer sandbox/songinha/tizen branch of tizen u-boot git

https://review.tizen.org/git/?p=platform/kernel/u-boot.git;a=summary

I cannot find any guide page for tizen on odroid xu3, but there is the page for odroid u3

https://wiki.tizen.org/wiki/How_to_Build_and_Load_Tizen_on_Odroid_U3

Already there is devfreq feature on mali r5p0-06rel0 for mali dvfs and i modified some,

but i didn't test on odroidxu3 yet.

Thanks.

User Space Drivers

Best wishes,

Guillaume

I may be wrote a silly thing but hardKernel has provided in its tools to update this script

Allowing the update DDX Mali for his boards

https://github.com/mdrjr/odroid-utility/blob/master/armsoc.sh

(https://github.com/ARM-software/linux/tree/odroidxu3-3.10.y-mali-midgard-r5p0)

The kernel builds & boots successfully, and the mali_kbase module loads without complaint, but when I try and run any OpenCL code the application terminates with an Unknown OpenCL error.

With strace I have narrowed this down to a missing /dev/mali0 sysfs handle, which doesn't make much sense as the kernel module is clearly loaded (according to lsmod anyway).

The kernel module was built with the odroidxu3_defconfig file available and has options configured like so:

$ grep MALI .config

CONFIG_MALI_MIDGARD=m

CONFIG_MALI_GATOR_SUPPORT=y

CONFIG_MALI_MIDGARD_DVFS=y

CONFIG_MALI_MIDGARD_RT_PM=y

# CONFIG_MALI_MIDGARD_ENABLE_TRACE is not set

CONFIG_MALI_MIDGARD_DEBUG_SYS=y

CONFIG_MALI_EXPERT=y

# CONFIG_MALI_DEVFREQ is not set

CONFIG_MALI_DEBUG_SHADER_SPLIT_FS=y

CONFIG_MALI_PLATFORM_FAKE=y

CONFIG_MALI_PLATFORM_THIRDPARTY=y

CONFIG_MALI_PLATFORM_THIRDPARTY_NAME="5422"

# CONFIG_MALI_DEBUG is not set

# CONFIG_MALI_NO_MALI is not set

# CONFIG_MALI_TRACE_TIMELINE is not set

# CONFIG_MALI_SYSTEM_TRACE is not set

# CONFIG_MALI_GPU_TRACEPOINTS is not set

I've tried a couple of combinations of options, but I can't seem to get /dev/mali0 to show up in the sysfs tree, despite the module clearly being loaded:

$ lsmod | grep mali

mali_kbase 236932 0

I have the appropriate binary drivers for the T62X (r5p0-06rel0) installed.

Neither the X11 or fbdev versions make any difference. I don't imagine either of those have any chance of working with the /dev/mali0 device missing.

Does anyone have any further suggestions for what I can try?

There are these two potentially relevant message relating to the Mali device in dmesg:

[    7.895860] [c6] mali 11800000.mali: Invalid irq res name: '/mali'

[    7.900908] [c6] mali: probe of 11800000.mali failed with error -22

Thanks.