Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Hardware Video Acceleration for VMWare view client 3.4
30-11-2015, 06:05 PM,
#1
Hardware Video Acceleration for VMWare view client 3.4
Hi Guys,

First of all, your work is awesome! I managed to port your Raspberry Pi last image to Cubieboard succesfully. My main concern is that VMWare Horizon View Client 3.4 defaults to software video acceleration. I've been investigating a little bit, and I think I need a little bit of help with this, because my knowledge of X11 and X.org is not good enough for this challenge I hope...

If someone could help me with this issue I think it would be great for the comunity having PCoIP video accelerated by hardware.

Thanks,
Miguel Amez
Reply
01-12-2015, 03:12 PM,
#2
RE: Hardware Video Acceleration for VMWare view client 3.4
You need that:
http://linux-sunxi.org/Mali_binary_driver
Reply
01-12-2015, 03:57 PM,
#3
RE: Hardware Video Acceleration for VMWare view client 3.4
Hi Admin,

Thanks for your reply!
I've already installed fbdev and got hardware acceleration working, maybe I didn't explain myself very good... The problem is that when you run vmware horizon client, everything works more or less ok, but when you try to play a video, CPU goes to 140% and everything freezes a little bit. Digging a bit in the PCoIP protocol made me look for logs, and I found them under /tmp/teradicci-rpitc/. I found that it falls back to software accelerated, as you can see in the log I'm pasting here (just pasted important info):

11-30 17:20:54.051: DEBUG/tera_event(1674): 99 0 0 cpu_arch_defines_report:-------- Current architecture defines -------------------
11-30 17:20:54.051: DEBUG/tera_event(1674): 99 0 0 cpu_arch_defines_report: not defined - TARGET_X86
11-30 17:20:54.051: DEBUG/tera_event(1674): 99 0 0 cpu_arch_defines_report: defined - TARGET_ARM
11-30 17:20:54.051: DEBUG/tera_event(1674): 99 0 0 cpu_arch_defines_report: not defined - TARGET_OS_IPHONE
11-30 17:20:54.051: DEBUG/tera_event(1674): 99 0 0 cpu_arch_defines_report: not defined - TARGET_OS_ANDROID
11-30 17:20:54.053: DEBUG/tera_event(1674): 99 0 0 cpu_arch_defines_report: not defined - TARGET_OS_MAC
11-30 17:20:54.053: DEBUG/tera_event(1674): 99 0 0 cpu_arch_defines_report: not defined - __i386__
11-30 17:20:54.053: DEBUG/tera_event(1674): 99 0 0 cpu_arch_defines_report: defined - LINUX
11-30 17:20:54.053: DEBUG/tera_event(1674): 99 0 0 cpu_arch_defines_report: defined - __ARM_NEON__
11-30 17:20:54.053: DEBUG/tera_event(1674): 99 0 0 cpu_arch_defines_report: not defined - USE_WMMXT
11-30 17:20:54.053: DEBUG/tera_event(1674): 99 0 0 cpu_arch_defines_report: not defined - WIN32
11-30 17:20:54.055: DEBUG/tera_event(1674): 99 0 0 cpu_arch_defines_report: not defined - TERA_CPU_ID_DISABLE_ALL_CPU_CAPABILITIES
11-30 17:20:54.055: DEBUG/tera_event(1674): 99 0 0 cpu_arch_defines_report:---------------------------------------------------------
11-30 17:20:54.055: DEBUG/tera_event(1674): 99 0 0 cpu_intrinsics_report: =============== Native CPU Capabilities ============
11-30 17:20:54.055: DEBUG/tera_event(1674): 99 0 0 cpu_intrinsics_report: CPU does not support SSE2
11-30 17:20:54.055: DEBUG/tera_event(1674): 99 0 0 cpu_intrinsics_report: CPU does not support SSE3
11-30 17:20:54.055: DEBUG/tera_event(1674): 99 0 0 cpu_intrinsics_report: CPU does not support SSSE3
11-30 17:20:54.055: DEBUG/tera_event(1674): 99 0 0 cpu_intrinsics_report: CPU does not support AES_NI
11-30 17:20:54.055: DEBUG/tera_event(1674): 99 0 0 cpu_intrinsics_report: CPU does not support PADLOCK_ACE
11-30 17:20:54.055: DEBUG/tera_event(1674): 99 0 0 cpu_intrinsics_report: CPU does not support ARM_WMMXT
11-30 17:20:54.055: DEBUG/tera_event(1674): 99 0 0 cpu_intrinsics_report: CPU supports ARM_NEON
11-30 17:20:54.055: DEBUG/tera_event(1674): 99 0 0 cpu_intrinsics_report:
................................................
11-30 17:20:54.119: DEBUG/tera_event(1674): 62 2 0 CODEC: State change from CODEC_INVALID to CODEC_DISABLED
11-30 17:20:54.119: DEBUG/tera_event(1674): 48 3 0 vtimer create: hda_timer_0
11-30 17:20:54.121: DEBUG/tera_event(1674): 61 2 0 Opening audio playback device

I'm thinking about moving to wayland, because this is a serious performance lack. I also have to say that I managed to play films with mplayer and hardware acceleration and they play pretty well, so I'm a little bit worried about Allwinner scene and video acceleration at this point. Any help would be awesome for me!

Thanks,
Miguel Amez
Reply
01-12-2015, 06:12 PM,
#4
RE: Hardware Video Acceleration for VMWare view client 3.4
Umm i dont know, when there is no hardware/video driver available on the OS/System the rendering process is demanded to the CPU. I think Horizon use dri2/dri3 and mesaGL, so, if allwinner/mali have some x11/dri2/mesagl driver you can have some performance gain... but dont expect a miracle.
You can try to use an odroid-xu4 board, the 2.0Ghz CPU clock will give you a great boost! (tested with xfreerdp and i can play 720p video fullscreen without problem)
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)