OpenCL driver issue with Samsung Chromebook

Hi krrishnarraj,

I just built the opencl.c he links to with "arm-linux-gnueabihf-gcc clInfo.c -I../../include -L../../lib -lOpenCL -o clinfo" and it runs fine for me, no out of memory errors. I notice that in the output in that blog, the PLUGIN output (see below) is not present, which seems to imply there's something dodgy about the way he's got his libraries set up.

Here's my output:

Found 1 platform(s).

platform[0x76ec1c30]: profile: FULL_PROFILE

platform[0x76ec1c30]: version: OpenCL 1.1

platform[0x76ec1c30]: name: ARM Platform

platform[0x76ec1c30]: vendor: ARM

platform[0x76ec1c30]: extensions: cl_khr_int64_base_atomics cl_khr_int64_extended_atomics cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_byte_addressable_store cl_arm_core_id cl_khr_egl_event cl_khr_egl_image

platform[0x76ec1c30]: Found 1 device(s).

[PLUGIN INFO] Plugin initializing

[PLUGIN DEBUG]  './override.instr_config' not found, trying to open the process config file

[PLUGIN DEBUG]  './clinfo.instr_config' not found, trying to open the default config file

[PLUGIN INFO] No configuration file found, attempting to use environment

[PLUGIN INFO] CINSTR GENERAL: Output directory set to: .

[PLUGIN INFO] No instrumentation features requested.

  device[0x76eaf218]: NAME: Mali-T604

  device[0x76eaf218]: VENDOR: ARM

  device[0x76eaf218]: PROFILE: FULL_PROFILE

  device[0x76eaf218]: VERSION: OpenCL 1.1

  device[0x76eaf218]: EXTENSIONS: cl_khr_int64_base_atomics cl_khr_int64_extended_atomics cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_byte_addressable_store cl_arm_core_id cl_khr_egl_event cl_khr_egl_image

  device[0x76eaf218]: DRIVER_VERSION: 1.1

  device[0x76eaf218]: Type: GPU

  device[0x76eaf218]: EXECUTION_CAPABILITIES: Kernel

  device[0x76eaf218]: GLOBAL_MEM_CACHE_TYPE: Read-Write (2)

  device[0x76eaf218]: CL_DEVICE_LOCAL_MEM_TYPE: Global (2)

  device[0x76eaf218]: SINGLE_FP_CONFIG: 0x3f

  device[0x76eaf218]: QUEUE_PROPERTIES: 0x3

  device[0x76eaf218]: VENDOR_ID: 1767243777

  device[0x76eaf218]: MAX_COMPUTE_UNITS: 4

  device[0x76eaf218]: MAX_WORK_ITEM_DIMENSIONS: 3

  device[0x76eaf218]: MAX_WORK_GROUP_SIZE: 256

  device[0x76eaf218]: PREFERRED_VECTOR_WIDTH_CHAR: 16

  device[0x76eaf218]: PREFERRED_VECTOR_WIDTH_SHORT: 8

  device[0x76eaf218]: PREFERRED_VECTOR_WIDTH_INT: 4

  device[0x76eaf218]: PREFERRED_VECTOR_WIDTH_LONG: 2

  device[0x76eaf218]: PREFERRED_VECTOR_WIDTH_FLOAT: 4

  device[0x76eaf218]: PREFERRED_VECTOR_WIDTH_DOUBLE: 0

  device[0x76eaf218]: MAX_CLOCK_FREQUENCY: 533

  device[0x76eaf218]: ADDRESS_BITS: 64

  device[0x76eaf218]: MAX_MEM_ALLOC_SIZE: 525569024

  device[0x76eaf218]: IMAGE_SUPPORT: 1

  device[0x76eaf218]: MAX_READ_IMAGE_ARGS: 128

  device[0x76eaf218]: MAX_WRITE_IMAGE_ARGS: 8

  device[0x76eaf218]: IMAGE2D_MAX_WIDTH: 65536

  device[0x76eaf218]: IMAGE2D_MAX_HEIGHT: 65536

  device[0x76eaf218]: IMAGE3D_MAX_WIDTH: 65536

  device[0x76eaf218]: IMAGE3D_MAX_HEIGHT: 65536

  device[0x76eaf218]: IMAGE3D_MAX_DEPTH: 65536

  device[0x76eaf218]: MAX_SAMPLERS: 16

  device[0x76eaf218]: MAX_PARAMETER_SIZE: 1024

  device[0x76eaf218]: MEM_BASE_ADDR_ALIGN: 1024

  device[0x76eaf218]: MIN_DATA_TYPE_ALIGN_SIZE: 128

  device[0x76eaf218]: GLOBAL_MEM_CACHELINE_SIZE: 64

  device[0x76eaf218]: GLOBAL_MEM_CACHE_SIZE: 131072

  device[0x76eaf218]: GLOBAL_MEM_SIZE: 2102276096

  device[0x76eaf218]: MAX_CONSTANT_BUFFER_SIZE: 65536

  device[0x76eaf218]: MAX_CONSTANT_ARGS: 8

  device[0x76eaf218]: LOCAL_MEM_SIZE: 32768

  device[0x76eaf218]: ERROR_CORRECTION_SUPPORT: 0

  device[0x76eaf218]: PROFILING_TIMER_RESOLUTION: 1000

  device[0x76eaf218]: ENDIAN_LITTLE: 1

  device[0x76eaf218]: AVAILABLE: 1

  device[0x76eaf218]: COMPILER_AVAILABLE: 1

BTW that was my blog! I had put libraries in ~/mali/fbdev as suggested. Moving it to /usr/lib/ doesn't make any difference. Even egl drivers are not working. I believe problem here is with my kernel. I had compiled 3.8.11 as suggested with the right patches. Can you please elaborate what kernel you tested it with and how you built it. Or just if its possible, could you upload your kernel (kernel.itb) and its modules here

Thanks

Chris,

Have you got the wifi working with OpenCL BSP?

~Amit

Have left for the day so will check tomorrow, but its the same kernel to my knowledge just with the mali driver changed, so any wifi issue I´d guess would be userspace related. What is the output of ¨ip a¨?

Bizarre, git clone git://git.linaro.org/arm/xorg/driver/xf86-video-armsoc.git works fine for me at home.

"ip a" gives me:

1: lo <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN

     link/loopback 00:00..

     inet 127.0.0.1/8 scope host lo

     inet6 ::1/128 scope host

     valid_lft forever preferred_lft forever

Did you use root account to execute OpenCL codes?

I found that only root account could execute the OpenCL sample codes in my case.

Does anyone know if there is a way to solve this? Thanks.

Running any program as sudo works I can live with that. Thanks for the hint

Hi j.c.,

This is because mali is set up as a misc device, and therefore under /dev/mali0 only root has rw permission. It might be possible to change the group of /dev/mali0, give that group rw permission to it, and add yourself to that group, but as you have discovered sudo also works . We're noting all these things down for future releases so thanks for the feedback!

Thanks,

Chris

Hi Amit,

I think we've spoken over email, but for the benefit of others we believe this is due to the udev daemon not being able to pick up the wifi card, probably due to an outdated version. You can either use a USB ethernet dongle, or try a more recent root filesystem, such as Arch or Ubuntu 13.04. We have it working on Arch in the office. It may also be possible to get it working on the existing rootfs we suggest in the guide, but I can't say for sure.

Thanks,

Chris

chmod & chown changes are not persistent over reboot. You can use udev rules. Create a file say '10-mali.rules' in /etc/udev/rules.d/ and add this

KERNEL=="mali[0-9]", GROUP="video" MODE="0660"

and add yourself to video group, or change mode to 0666

This way you have rw permissions to /dev/mali0

--Krishnaraj