Hi Vishal,
I'm now looking at the logcat output of Samsung Arndale Android image, and found:
D/libEGL ( 2167): No GPU support detected. Fallback to software renderer. D/libEGL ( 2167): loaded /system/lib/egl/libGLES_android.so
Then:
W/gralloc ( 2166): page flipping not supported (yres_virtual=720, requested=1440) I/gralloc ( 2166): using (fd=12) I/gralloc ( 2166): id = I/gralloc ( 2166): xres = 1280 px I/gralloc ( 2166): yres = 720 px I/gralloc ( 2166): xres_virtual = 1280 px I/gralloc ( 2166): yres_virtual = 720 px I/gralloc ( 2166): bpp = 16 I/gralloc ( 2166): r = 11:5 I/gralloc ( 2166): g = 5:6 I/gralloc ( 2166): b = 0:5 I/gralloc ( 2166): width = 1280 mm (25.400000 dpi) I/gralloc ( 2166): height = 720 mm (25.400000 dpi) I/gralloc ( 2166): refresh rate = 60.00 Hz I/iptables( 2164): iptables terminated by exit(3) E/Netd ( 2164): exec() res=0, status=768 for /system/bin/iptables -t filter -N bw_INPUT I/ip6tables( 2164): ip6tables terminated by exit(3) E/Netd ( 2164): exec() res=0, status=768 for /system/bin/ip6tables -t filter -N bw_INPUT I/iptables( 2164): iptables terminated by exit(3) E/Netd ( 2164): exec() res=0, status=768 for /system/bin/iptables -t filter -A INPUT -j bw_INPUT I/ip6tables( 2164): ip6tables terminated by exit(3) E/Netd ( 2164): exec() res=0, status=768 for /system/bin/ip6tables -t filter -A INPUT -j bw_INPUT I/iptables( 2164): iptables terminated by exit(3) E/Netd ( 2164): exec() res=0, status=768 for /system/bin/iptables -t filter -N fw_INPUT I/SurfaceFlinger( 2166): Using composer version 1.0 W/SurfaceFlinger( 2166): getting VSYNC period from fb HAL: 16666666 W/SurfaceFlinger( 2166): no suitable EGLConfig found, trying a simpler query W/SurfaceFlinger( 2166): EGL_SLOW_CONFIG selected! I/SurfaceFlinger( 2166): EGL informations: I/SurfaceFlinger( 2166): vendor : Android I/SurfaceFlinger( 2166): version : 1.4 Android META-EGL I/SurfaceFlinger( 2166): extensions: EGL_KHR_get_all_proc_addresses EGL_ANDROID_presentation_time EGL_KHR_image_base EGL_KHR_fence_sync EGL_A I/SurfaceFlinger( 2166): Client API: OpenGL_ES I/SurfaceFlinger( 2166): EGLSurface: 5-6-5-0, config=0x0 I/SurfaceFlinger( 2166): OpenGL ES informations: I/SurfaceFlinger( 2166): vendor : Android I/SurfaceFlinger( 2166): renderer : Android PixelFlinger 1.4 I/SurfaceFlinger( 2166): version : OpenGL ES-CM 1.0 I/SurfaceFlinger( 2166): extensions: GL_EXT_debug_marker GL_OES_byte_coordinates GL_OES_fixed_point GL_OES_single_precision GL_OES_read_forma I/SurfaceFlinger( 2166): GL_MAX_TEXTURE_SIZE = 4096 I/SurfaceFlinger( 2166): GL_MAX_VIEWPORT_DIMS = 4096
As we know the Arndale board integrates dual-core A15 CPU and ARM Mali-T604 GPU. If as the log described, "No GPU support detected", then does it mean that all the graphic work now is done by the dual-core A15 CPU itself? Though the speed for navigation among screens is fast and 0xBenchmark test looks good as well.
I may be wrong but in this condition, the board seems can't be considered as "Hardware Accelerated", at least not "GPU Hardware Accelerated". Also, as I know, "Android PixelFlinger" is a software renderer.
Do you know more information about this?
Thank you.
Best Regards Botao Sun
Hi Botao,
There is no hw acceleration on arndale board.
On 21 March 2014 17:53, Botao Sun botao.sun@linaro.org wrote:
Hi Vishal,
I'm now looking at the logcat output of Samsung Arndale Android image, and found:
D/libEGL ( 2167): No GPU support detected. Fallback to software renderer. D/libEGL ( 2167): loaded /system/lib/egl/libGLES_android.so
Then:
W/gralloc ( 2166): page flipping not supported (yres_virtual=720, requested=1440) I/gralloc ( 2166): using (fd=12) I/gralloc ( 2166): id = I/gralloc ( 2166): xres = 1280 px I/gralloc ( 2166): yres = 720 px I/gralloc ( 2166): xres_virtual = 1280 px I/gralloc ( 2166): yres_virtual = 720 px I/gralloc ( 2166): bpp = 16 I/gralloc ( 2166): r = 11:5 I/gralloc ( 2166): g = 5:6 I/gralloc ( 2166): b = 0:5 I/gralloc ( 2166): width = 1280 mm (25.400000 dpi) I/gralloc ( 2166): height = 720 mm (25.400000 dpi) I/gralloc ( 2166): refresh rate = 60.00 Hz I/iptables( 2164): iptables terminated by exit(3) E/Netd ( 2164): exec() res=0, status=768 for /system/bin/iptables -t filter -N bw_INPUT I/ip6tables( 2164): ip6tables terminated by exit(3) E/Netd ( 2164): exec() res=0, status=768 for /system/bin/ip6tables -t filter -N bw_INPUT I/iptables( 2164): iptables terminated by exit(3) E/Netd ( 2164): exec() res=0, status=768 for /system/bin/iptables -t filter -A INPUT -j bw_INPUT I/ip6tables( 2164): ip6tables terminated by exit(3) E/Netd ( 2164): exec() res=0, status=768 for /system/bin/ip6tables -t filter -A INPUT -j bw_INPUT I/iptables( 2164): iptables terminated by exit(3) E/Netd ( 2164): exec() res=0, status=768 for /system/bin/iptables -t filter -N fw_INPUT I/SurfaceFlinger( 2166): Using composer version 1.0 W/SurfaceFlinger( 2166): getting VSYNC period from fb HAL: 16666666 W/SurfaceFlinger( 2166): no suitable EGLConfig found, trying a simpler query W/SurfaceFlinger( 2166): EGL_SLOW_CONFIG selected! I/SurfaceFlinger( 2166): EGL informations: I/SurfaceFlinger( 2166): vendor : Android I/SurfaceFlinger( 2166): version : 1.4 Android META-EGL I/SurfaceFlinger( 2166): extensions: EGL_KHR_get_all_proc_addresses EGL_ANDROID_presentation_time EGL_KHR_image_base EGL_KHR_fence_sync EGL_A I/SurfaceFlinger( 2166): Client API: OpenGL_ES I/SurfaceFlinger( 2166): EGLSurface: 5-6-5-0, config=0x0 I/SurfaceFlinger( 2166): OpenGL ES informations: I/SurfaceFlinger( 2166): vendor : Android I/SurfaceFlinger( 2166): renderer : Android PixelFlinger 1.4 I/SurfaceFlinger( 2166): version : OpenGL ES-CM 1.0 I/SurfaceFlinger( 2166): extensions: GL_EXT_debug_marker GL_OES_byte_coordinates GL_OES_fixed_point GL_OES_single_precision GL_OES_read_forma I/SurfaceFlinger( 2166): GL_MAX_TEXTURE_SIZE = 4096 I/SurfaceFlinger( 2166): GL_MAX_VIEWPORT_DIMS = 4096
As we know the Arndale board integrates dual-core A15 CPU and ARM Mali-T604 GPU. If as the log described, "No GPU support detected", then does it mean that all the graphic work now is done by the dual-core A15 CPU itself? Though the speed for navigation among screens is fast and 0xBenchmark test looks good as well.
I may be wrong but in this condition, the board seems can't be considered as "Hardware Accelerated", at least not "GPU Hardware Accelerated". Also, as I know, "Android PixelFlinger" is a software renderer.
Do you know more information about this?
Thank you.
Best Regards Botao Sun
To be more clear. The board supports accelerated graphics but the LT kernel doesn't have the drivers to have accelerated graphics support.
On 21 March 2014 19:49, Vishal Bhoj vishal.bhoj@linaro.org wrote:
Hi Botao,
There is no hw acceleration on arndale board.
On 21 March 2014 17:53, Botao Sun botao.sun@linaro.org wrote:
Hi Vishal,
I'm now looking at the logcat output of Samsung Arndale Android image, and found:
D/libEGL ( 2167): No GPU support detected. Fallback to software renderer. D/libEGL ( 2167): loaded /system/lib/egl/libGLES_android.so
Then:
W/gralloc ( 2166): page flipping not supported (yres_virtual=720, requested=1440) I/gralloc ( 2166): using (fd=12) I/gralloc ( 2166): id = I/gralloc ( 2166): xres = 1280 px I/gralloc ( 2166): yres = 720 px I/gralloc ( 2166): xres_virtual = 1280 px I/gralloc ( 2166): yres_virtual = 720 px I/gralloc ( 2166): bpp = 16 I/gralloc ( 2166): r = 11:5 I/gralloc ( 2166): g = 5:6 I/gralloc ( 2166): b = 0:5 I/gralloc ( 2166): width = 1280 mm (25.400000 dpi) I/gralloc ( 2166): height = 720 mm (25.400000 dpi) I/gralloc ( 2166): refresh rate = 60.00 Hz I/iptables( 2164): iptables terminated by exit(3) E/Netd ( 2164): exec() res=0, status=768 for /system/bin/iptables -t filter -N bw_INPUT I/ip6tables( 2164): ip6tables terminated by exit(3) E/Netd ( 2164): exec() res=0, status=768 for /system/bin/ip6tables -t filter -N bw_INPUT I/iptables( 2164): iptables terminated by exit(3) E/Netd ( 2164): exec() res=0, status=768 for /system/bin/iptables -t filter -A INPUT -j bw_INPUT I/ip6tables( 2164): ip6tables terminated by exit(3) E/Netd ( 2164): exec() res=0, status=768 for /system/bin/ip6tables -t filter -A INPUT -j bw_INPUT I/iptables( 2164): iptables terminated by exit(3) E/Netd ( 2164): exec() res=0, status=768 for /system/bin/iptables -t filter -N fw_INPUT I/SurfaceFlinger( 2166): Using composer version 1.0 W/SurfaceFlinger( 2166): getting VSYNC period from fb HAL: 16666666 W/SurfaceFlinger( 2166): no suitable EGLConfig found, trying a simpler query W/SurfaceFlinger( 2166): EGL_SLOW_CONFIG selected! I/SurfaceFlinger( 2166): EGL informations: I/SurfaceFlinger( 2166): vendor : Android I/SurfaceFlinger( 2166): version : 1.4 Android META-EGL I/SurfaceFlinger( 2166): extensions: EGL_KHR_get_all_proc_addresses EGL_ANDROID_presentation_time EGL_KHR_image_base EGL_KHR_fence_sync EGL_A I/SurfaceFlinger( 2166): Client API: OpenGL_ES I/SurfaceFlinger( 2166): EGLSurface: 5-6-5-0, config=0x0 I/SurfaceFlinger( 2166): OpenGL ES informations: I/SurfaceFlinger( 2166): vendor : Android I/SurfaceFlinger( 2166): renderer : Android PixelFlinger 1.4 I/SurfaceFlinger( 2166): version : OpenGL ES-CM 1.0 I/SurfaceFlinger( 2166): extensions: GL_EXT_debug_marker GL_OES_byte_coordinates GL_OES_fixed_point GL_OES_single_precision GL_OES_read_forma I/SurfaceFlinger( 2166): GL_MAX_TEXTURE_SIZE = 4096 I/SurfaceFlinger( 2166): GL_MAX_VIEWPORT_DIMS = 4096
As we know the Arndale board integrates dual-core A15 CPU and ARM Mali-T604 GPU. If as the log described, "No GPU support detected", then does it mean that all the graphic work now is done by the dual-core A15 CPU itself? Though the speed for navigation among screens is fast and 0xBenchmark test looks good as well.
I may be wrong but in this condition, the board seems can't be considered as "Hardware Accelerated", at least not "GPU Hardware Accelerated". Also, as I know, "Android PixelFlinger" is a software renderer.
Do you know more information about this?
Thank you.
Best Regards Botao Sun
The GWG does have a LSK kernel branch with Mali support. (IE accelerated graphics)
We haven't targeted Android as of yet but in the grand scheme things should be reasonably close. Show can say for certain but we'd need a rebase on linux-linaro-lsk-v3.10-android at a minimum.
I'm a little unclear how interesting the LSK android kernel is for the Android team. One of my buffered questions for Khasim.
On Fri, Mar 21, 2014 at 9:20 AM, Vishal Bhoj vishal.bhoj@linaro.org wrote:
To be more clear. The board supports accelerated graphics but the LT kernel doesn't have the drivers to have accelerated graphics support.
On 21 March 2014 19:49, Vishal Bhoj vishal.bhoj@linaro.org wrote:
Hi Botao,
There is no hw acceleration on arndale board.
On 21 March 2014 17:53, Botao Sun botao.sun@linaro.org wrote:
Hi Vishal,
I'm now looking at the logcat output of Samsung Arndale Android image, and found:
D/libEGL ( 2167): No GPU support detected. Fallback to software renderer. D/libEGL ( 2167): loaded /system/lib/egl/libGLES_android.so
Then:
W/gralloc ( 2166): page flipping not supported (yres_virtual=720, requested=1440) I/gralloc ( 2166): using (fd=12) I/gralloc ( 2166): id = I/gralloc ( 2166): xres = 1280 px I/gralloc ( 2166): yres = 720 px I/gralloc ( 2166): xres_virtual = 1280 px I/gralloc ( 2166): yres_virtual = 720 px I/gralloc ( 2166): bpp = 16 I/gralloc ( 2166): r = 11:5 I/gralloc ( 2166): g = 5:6 I/gralloc ( 2166): b = 0:5 I/gralloc ( 2166): width = 1280 mm (25.400000 dpi) I/gralloc ( 2166): height = 720 mm (25.400000 dpi) I/gralloc ( 2166): refresh rate = 60.00 Hz I/iptables( 2164): iptables terminated by exit(3) E/Netd ( 2164): exec() res=0, status=768 for /system/bin/iptables -t filter -N bw_INPUT I/ip6tables( 2164): ip6tables terminated by exit(3) E/Netd ( 2164): exec() res=0, status=768 for /system/bin/ip6tables -t filter -N bw_INPUT I/iptables( 2164): iptables terminated by exit(3) E/Netd ( 2164): exec() res=0, status=768 for /system/bin/iptables -t filter -A INPUT -j bw_INPUT I/ip6tables( 2164): ip6tables terminated by exit(3) E/Netd ( 2164): exec() res=0, status=768 for /system/bin/ip6tables -t filter -A INPUT -j bw_INPUT I/iptables( 2164): iptables terminated by exit(3) E/Netd ( 2164): exec() res=0, status=768 for /system/bin/iptables -t filter -N fw_INPUT I/SurfaceFlinger( 2166): Using composer version 1.0 W/SurfaceFlinger( 2166): getting VSYNC period from fb HAL: 16666666 W/SurfaceFlinger( 2166): no suitable EGLConfig found, trying a simpler query W/SurfaceFlinger( 2166): EGL_SLOW_CONFIG selected! I/SurfaceFlinger( 2166): EGL informations: I/SurfaceFlinger( 2166): vendor : Android I/SurfaceFlinger( 2166): version : 1.4 Android META-EGL I/SurfaceFlinger( 2166): extensions: EGL_KHR_get_all_proc_addresses EGL_ANDROID_presentation_time EGL_KHR_image_base EGL_KHR_fence_sync EGL_A I/SurfaceFlinger( 2166): Client API: OpenGL_ES I/SurfaceFlinger( 2166): EGLSurface: 5-6-5-0, config=0x0 I/SurfaceFlinger( 2166): OpenGL ES informations: I/SurfaceFlinger( 2166): vendor : Android I/SurfaceFlinger( 2166): renderer : Android PixelFlinger 1.4 I/SurfaceFlinger( 2166): version : OpenGL ES-CM 1.0 I/SurfaceFlinger( 2166): extensions: GL_EXT_debug_marker GL_OES_byte_coordinates GL_OES_fixed_point GL_OES_single_precision GL_OES_read_forma I/SurfaceFlinger( 2166): GL_MAX_TEXTURE_SIZE = 4096 I/SurfaceFlinger( 2166): GL_MAX_VIEWPORT_DIMS = 4096
As we know the Arndale board integrates dual-core A15 CPU and ARM Mali-T604 GPU. If as the log described, "No GPU support detected", then does it mean that all the graphic work now is done by the dual-core A15 CPU itself? Though the speed for navigation among screens is fast and 0xBenchmark test looks good as well.
I may be wrong but in this condition, the board seems can't be considered as "Hardware Accelerated", at least not "GPU Hardware Accelerated". Also, as I know, "Android PixelFlinger" is a software renderer.
Do you know more information about this?
Thank you.
Best Regards Botao Sun
linaro-android mailing list linaro-android@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-android
Hi all,
On 21 March 2014 19:58, Tom Gall tom.gall@linaro.org wrote:
The GWG does have a LSK kernel branch with Mali support. (IE accelerated graphics)
We haven't targeted Android as of yet but in the grand scheme things should be reasonably close. Show can say for certain but we'd need a rebase on linux-linaro-lsk-v3.10-android at a minimum.
I'm a little unclear how interesting the LSK android kernel is for the Android team. One of my buffered questions for Khasim.
We do have requests from members to support / maintain Android on LSK. I
would let Vishal look at integration, if we find any issues then we can jump in to fix specific issues.
Regards, Khasim
On Fri, Mar 21, 2014 at 9:20 AM, Vishal Bhoj vishal.bhoj@linaro.org wrote:
To be more clear. The board supports accelerated graphics but the LT
kernel
doesn't have the drivers to have accelerated graphics support.
On 21 March 2014 19:49, Vishal Bhoj vishal.bhoj@linaro.org wrote:
Hi Botao,
There is no hw acceleration on arndale board.
On 21 March 2014 17:53, Botao Sun botao.sun@linaro.org wrote:
Hi Vishal,
I'm now looking at the logcat output of Samsung Arndale Android image, and found:
D/libEGL ( 2167): No GPU support detected. Fallback to software renderer. D/libEGL ( 2167): loaded /system/lib/egl/libGLES_android.so
Then:
W/gralloc ( 2166): page flipping not supported (yres_virtual=720, requested=1440) I/gralloc ( 2166): using (fd=12) I/gralloc ( 2166): id = I/gralloc ( 2166): xres = 1280 px I/gralloc ( 2166): yres = 720 px I/gralloc ( 2166): xres_virtual = 1280 px I/gralloc ( 2166): yres_virtual = 720 px I/gralloc ( 2166): bpp = 16 I/gralloc ( 2166): r = 11:5 I/gralloc ( 2166): g = 5:6 I/gralloc ( 2166): b = 0:5 I/gralloc ( 2166): width = 1280 mm (25.400000 dpi) I/gralloc ( 2166): height = 720 mm (25.400000 dpi) I/gralloc ( 2166): refresh rate = 60.00 Hz I/iptables( 2164): iptables terminated by exit(3) E/Netd ( 2164): exec() res=0, status=768 for /system/bin/iptables -t filter -N bw_INPUT I/ip6tables( 2164): ip6tables terminated by exit(3) E/Netd ( 2164): exec() res=0, status=768 for /system/bin/ip6tables
-t
filter -N bw_INPUT I/iptables( 2164): iptables terminated by exit(3) E/Netd ( 2164): exec() res=0, status=768 for /system/bin/iptables -t filter -A INPUT -j bw_INPUT I/ip6tables( 2164): ip6tables terminated by exit(3) E/Netd ( 2164): exec() res=0, status=768 for /system/bin/ip6tables
-t
filter -A INPUT -j bw_INPUT I/iptables( 2164): iptables terminated by exit(3) E/Netd ( 2164): exec() res=0, status=768 for /system/bin/iptables -t filter -N fw_INPUT I/SurfaceFlinger( 2166): Using composer version 1.0 W/SurfaceFlinger( 2166): getting VSYNC period from fb HAL: 16666666 W/SurfaceFlinger( 2166): no suitable EGLConfig found, trying a simpler query W/SurfaceFlinger( 2166): EGL_SLOW_CONFIG selected! I/SurfaceFlinger( 2166): EGL informations: I/SurfaceFlinger( 2166): vendor : Android I/SurfaceFlinger( 2166): version : 1.4 Android META-EGL I/SurfaceFlinger( 2166): extensions: EGL_KHR_get_all_proc_addresses EGL_ANDROID_presentation_time EGL_KHR_image_base EGL_KHR_fence_sync
EGL_A
I/SurfaceFlinger( 2166): Client API: OpenGL_ES I/SurfaceFlinger( 2166): EGLSurface: 5-6-5-0, config=0x0 I/SurfaceFlinger( 2166): OpenGL ES informations: I/SurfaceFlinger( 2166): vendor : Android I/SurfaceFlinger( 2166): renderer : Android PixelFlinger 1.4 I/SurfaceFlinger( 2166): version : OpenGL ES-CM 1.0 I/SurfaceFlinger( 2166): extensions: GL_EXT_debug_marker GL_OES_byte_coordinates GL_OES_fixed_point GL_OES_single_precision GL_OES_read_forma I/SurfaceFlinger( 2166): GL_MAX_TEXTURE_SIZE = 4096 I/SurfaceFlinger( 2166): GL_MAX_VIEWPORT_DIMS = 4096
As we know the Arndale board integrates dual-core A15 CPU and ARM Mali-T604 GPU. If as the log described, "No GPU support detected",
then does
it mean that all the graphic work now is done by the dual-core A15 CPU itself? Though the speed for navigation among screens is fast and 0xBenchmark test looks good as well.
I may be wrong but in this condition, the board seems can't be
considered
as "Hardware Accelerated", at least not "GPU Hardware Accelerated".
Also, as
I know, "Android PixelFlinger" is a software renderer.
Do you know more information about this?
Thank you.
Best Regards Botao Sun
linaro-android mailing list linaro-android@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-android
-- Regards, Tom
"Where's the kaboom!? There was supposed to be an earth-shattering kaboom!" Marvin Martian Tech Lead, Graphics Working Group | Linaro.org │ Open source software for ARM SoCs w) tom.gall att linaro.org h) tom_gall att mac.com
linaro-android mailing list linaro-android@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-android
On 21 March 2014 20:02, Khasim Syed Mohammed khasim.mohammed@linaro.orgwrote:
Hi all,
On 21 March 2014 19:58, Tom Gall tom.gall@linaro.org wrote:
The GWG does have a LSK kernel branch with Mali support. (IE accelerated graphics)
We haven't targeted Android as of yet but in the grand scheme things should be reasonably close. Show can say for certain but we'd need a rebase on linux-linaro-lsk-v3.10-android at a minimum.
I'm a little unclear how interesting the LSK android kernel is for the Android team. One of my buffered questions for Khasim.
We do have requests from members to support / maintain Android on LSK. I
would let Vishal look at integration, if we find any issues then we can jump in to fix specific issues.
We do validate Android version of the LSK on ARMv7 and ARMv8 architecture. Coming back to the support for Mali on LSK for Arndale, It would be interesting to try that out if GWG is planning to support the same.
From what I know, the current LSK tree doesn't have complete support for
Arndale board and hence we don't have Arndale as one of the target for validating LSK.
Regards, Khasim
On Fri, Mar 21, 2014 at 9:20 AM, Vishal Bhoj vishal.bhoj@linaro.org wrote:
To be more clear. The board supports accelerated graphics but the LT
kernel
doesn't have the drivers to have accelerated graphics support.
On 21 March 2014 19:49, Vishal Bhoj vishal.bhoj@linaro.org wrote:
Hi Botao,
There is no hw acceleration on arndale board.
On 21 March 2014 17:53, Botao Sun botao.sun@linaro.org wrote:
Hi Vishal,
I'm now looking at the logcat output of Samsung Arndale Android image, and found:
D/libEGL ( 2167): No GPU support detected. Fallback to software renderer. D/libEGL ( 2167): loaded /system/lib/egl/libGLES_android.so
Then:
W/gralloc ( 2166): page flipping not supported (yres_virtual=720, requested=1440) I/gralloc ( 2166): using (fd=12) I/gralloc ( 2166): id = I/gralloc ( 2166): xres = 1280 px I/gralloc ( 2166): yres = 720 px I/gralloc ( 2166): xres_virtual = 1280 px I/gralloc ( 2166): yres_virtual = 720 px I/gralloc ( 2166): bpp = 16 I/gralloc ( 2166): r = 11:5 I/gralloc ( 2166): g = 5:6 I/gralloc ( 2166): b = 0:5 I/gralloc ( 2166): width = 1280 mm (25.400000 dpi) I/gralloc ( 2166): height = 720 mm (25.400000 dpi) I/gralloc ( 2166): refresh rate = 60.00 Hz I/iptables( 2164): iptables terminated by exit(3) E/Netd ( 2164): exec() res=0, status=768 for /system/bin/iptables
-t
filter -N bw_INPUT I/ip6tables( 2164): ip6tables terminated by exit(3) E/Netd ( 2164): exec() res=0, status=768 for /system/bin/ip6tables
-t
filter -N bw_INPUT I/iptables( 2164): iptables terminated by exit(3) E/Netd ( 2164): exec() res=0, status=768 for /system/bin/iptables
-t
filter -A INPUT -j bw_INPUT I/ip6tables( 2164): ip6tables terminated by exit(3) E/Netd ( 2164): exec() res=0, status=768 for /system/bin/ip6tables
-t
filter -A INPUT -j bw_INPUT I/iptables( 2164): iptables terminated by exit(3) E/Netd ( 2164): exec() res=0, status=768 for /system/bin/iptables
-t
filter -N fw_INPUT I/SurfaceFlinger( 2166): Using composer version 1.0 W/SurfaceFlinger( 2166): getting VSYNC period from fb HAL: 16666666 W/SurfaceFlinger( 2166): no suitable EGLConfig found, trying a simpler query W/SurfaceFlinger( 2166): EGL_SLOW_CONFIG selected! I/SurfaceFlinger( 2166): EGL informations: I/SurfaceFlinger( 2166): vendor : Android I/SurfaceFlinger( 2166): version : 1.4 Android META-EGL I/SurfaceFlinger( 2166): extensions: EGL_KHR_get_all_proc_addresses EGL_ANDROID_presentation_time EGL_KHR_image_base EGL_KHR_fence_sync
EGL_A
I/SurfaceFlinger( 2166): Client API: OpenGL_ES I/SurfaceFlinger( 2166): EGLSurface: 5-6-5-0, config=0x0 I/SurfaceFlinger( 2166): OpenGL ES informations: I/SurfaceFlinger( 2166): vendor : Android I/SurfaceFlinger( 2166): renderer : Android PixelFlinger 1.4 I/SurfaceFlinger( 2166): version : OpenGL ES-CM 1.0 I/SurfaceFlinger( 2166): extensions: GL_EXT_debug_marker GL_OES_byte_coordinates GL_OES_fixed_point GL_OES_single_precision GL_OES_read_forma I/SurfaceFlinger( 2166): GL_MAX_TEXTURE_SIZE = 4096 I/SurfaceFlinger( 2166): GL_MAX_VIEWPORT_DIMS = 4096
As we know the Arndale board integrates dual-core A15 CPU and ARM Mali-T604 GPU. If as the log described, "No GPU support detected",
then does
it mean that all the graphic work now is done by the dual-core A15 CPU itself? Though the speed for navigation among screens is fast and 0xBenchmark test looks good as well.
I may be wrong but in this condition, the board seems can't be
considered
as "Hardware Accelerated", at least not "GPU Hardware Accelerated".
Also, as
I know, "Android PixelFlinger" is a software renderer.
Do you know more information about this?
Thank you.
Best Regards Botao Sun
linaro-android mailing list linaro-android@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-android
-- Regards, Tom
"Where's the kaboom!? There was supposed to be an earth-shattering kaboom!" Marvin Martian Tech Lead, Graphics Working Group | Linaro.org │ Open source software for ARM SoCs w) tom.gall att linaro.org h) tom_gall att mac.com
linaro-android mailing list linaro-android@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-android
Hi Vishal,
On Fri, Mar 21, 2014 at 9:40 AM, Vishal Bhoj vishal.bhoj@linaro.org wrote:
On 21 March 2014 20:02, Khasim Syed Mohammed khasim.mohammed@linaro.org wrote:
Hi all,
On 21 March 2014 19:58, Tom Gall tom.gall@linaro.org wrote:
The GWG does have a LSK kernel branch with Mali support. (IE accelerated graphics)
We haven't targeted Android as of yet but in the grand scheme things should be reasonably close. Show can say for certain but we'd need a rebase on linux-linaro-lsk-v3.10-android at a minimum.
I'm a little unclear how interesting the LSK android kernel is for the Android team. One of my buffered questions for Khasim.
We do have requests from members to support / maintain Android on LSK. I would let Vishal look at integration, if we find any issues then we can jump in to fix specific issues.
Cool.
We do validate Android version of the LSK on ARMv7 and ARMv8 architecture. Coming back to the support for Mali on LSK for Arndale, It would be interesting to try that out if GWG is planning to support the same.
Yes we are. We have an epic devoted to Mali support on the LSK.
From what I know, the current LSK tree doesn't have complete support for Arndale board and hence we don't have Arndale as one of the target for validating LSK.
I can't speak to all the features of the board. But I can say Show has accelerated Graphics with Mali + patches we obtained from the Samsung LT up and working on Arndale.
So like I mentioned I think a rebase of Show's branch with the LSK android tree might be quite quite close, least for something with a functional accelerated graphics stack.
Show would it be possible to give this is try?
Regards, Khasim
On Fri, Mar 21, 2014 at 9:20 AM, Vishal Bhoj vishal.bhoj@linaro.org wrote:
To be more clear. The board supports accelerated graphics but the LT kernel doesn't have the drivers to have accelerated graphics support.
On 21 March 2014 19:49, Vishal Bhoj vishal.bhoj@linaro.org wrote:
Hi Botao,
There is no hw acceleration on arndale board.
On 21 March 2014 17:53, Botao Sun botao.sun@linaro.org wrote:
Hi Vishal,
I'm now looking at the logcat output of Samsung Arndale Android image, and found:
D/libEGL ( 2167): No GPU support detected. Fallback to software renderer. D/libEGL ( 2167): loaded /system/lib/egl/libGLES_android.so
Then:
W/gralloc ( 2166): page flipping not supported (yres_virtual=720, requested=1440) I/gralloc ( 2166): using (fd=12) I/gralloc ( 2166): id = I/gralloc ( 2166): xres = 1280 px I/gralloc ( 2166): yres = 720 px I/gralloc ( 2166): xres_virtual = 1280 px I/gralloc ( 2166): yres_virtual = 720 px I/gralloc ( 2166): bpp = 16 I/gralloc ( 2166): r = 11:5 I/gralloc ( 2166): g = 5:6 I/gralloc ( 2166): b = 0:5 I/gralloc ( 2166): width = 1280 mm (25.400000 dpi) I/gralloc ( 2166): height = 720 mm (25.400000 dpi) I/gralloc ( 2166): refresh rate = 60.00 Hz I/iptables( 2164): iptables terminated by exit(3) E/Netd ( 2164): exec() res=0, status=768 for /system/bin/iptables -t filter -N bw_INPUT I/ip6tables( 2164): ip6tables terminated by exit(3) E/Netd ( 2164): exec() res=0, status=768 for /system/bin/ip6tables -t filter -N bw_INPUT I/iptables( 2164): iptables terminated by exit(3) E/Netd ( 2164): exec() res=0, status=768 for /system/bin/iptables -t filter -A INPUT -j bw_INPUT I/ip6tables( 2164): ip6tables terminated by exit(3) E/Netd ( 2164): exec() res=0, status=768 for /system/bin/ip6tables -t filter -A INPUT -j bw_INPUT I/iptables( 2164): iptables terminated by exit(3) E/Netd ( 2164): exec() res=0, status=768 for /system/bin/iptables -t filter -N fw_INPUT I/SurfaceFlinger( 2166): Using composer version 1.0 W/SurfaceFlinger( 2166): getting VSYNC period from fb HAL: 16666666 W/SurfaceFlinger( 2166): no suitable EGLConfig found, trying a simpler query W/SurfaceFlinger( 2166): EGL_SLOW_CONFIG selected! I/SurfaceFlinger( 2166): EGL informations: I/SurfaceFlinger( 2166): vendor : Android I/SurfaceFlinger( 2166): version : 1.4 Android META-EGL I/SurfaceFlinger( 2166): extensions: EGL_KHR_get_all_proc_addresses EGL_ANDROID_presentation_time EGL_KHR_image_base EGL_KHR_fence_sync EGL_A I/SurfaceFlinger( 2166): Client API: OpenGL_ES I/SurfaceFlinger( 2166): EGLSurface: 5-6-5-0, config=0x0 I/SurfaceFlinger( 2166): OpenGL ES informations: I/SurfaceFlinger( 2166): vendor : Android I/SurfaceFlinger( 2166): renderer : Android PixelFlinger 1.4 I/SurfaceFlinger( 2166): version : OpenGL ES-CM 1.0 I/SurfaceFlinger( 2166): extensions: GL_EXT_debug_marker GL_OES_byte_coordinates GL_OES_fixed_point GL_OES_single_precision GL_OES_read_forma I/SurfaceFlinger( 2166): GL_MAX_TEXTURE_SIZE = 4096 I/SurfaceFlinger( 2166): GL_MAX_VIEWPORT_DIMS = 4096
As we know the Arndale board integrates dual-core A15 CPU and ARM Mali-T604 GPU. If as the log described, "No GPU support detected", then does it mean that all the graphic work now is done by the dual-core A15 CPU itself? Though the speed for navigation among screens is fast and 0xBenchmark test looks good as well.
I may be wrong but in this condition, the board seems can't be considered as "Hardware Accelerated", at least not "GPU Hardware Accelerated". Also, as I know, "Android PixelFlinger" is a software renderer.
Do you know more information about this?
Thank you.
Best Regards Botao Sun
linaro-android mailing list linaro-android@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-android
-- Regards, Tom
"Where's the kaboom!? There was supposed to be an earth-shattering kaboom!" Marvin Martian Tech Lead, Graphics Working Group | Linaro.org │ Open source software for ARM SoCs w) tom.gall att linaro.org h) tom_gall att mac.com
linaro-android mailing list linaro-android@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-android
Hi Tom,
On Fri, Mar 21, 2014 at 10:54 PM, Tom Gall tom.gall@linaro.org wrote:
Hi Vishal,
On Fri, Mar 21, 2014 at 9:40 AM, Vishal Bhoj vishal.bhoj@linaro.org wrote:
On 21 March 2014 20:02, Khasim Syed Mohammed <khasim.mohammed@linaro.org
wrote:
Hi all,
On 21 March 2014 19:58, Tom Gall tom.gall@linaro.org wrote:
The GWG does have a LSK kernel branch with Mali support. (IE accelerated graphics)
We haven't targeted Android as of yet but in the grand scheme things should be reasonably close. Show can say for certain but we'd need a rebase on linux-linaro-lsk-v3.10-android at a minimum.
I'm a little unclear how interesting the LSK android kernel is for the Android team. One of my buffered questions for Khasim.
We do have requests from members to support / maintain Android on LSK. I would let Vishal look at integration, if we find any issues then we can
jump
in to fix specific issues.
Cool.
We do validate Android version of the LSK on ARMv7 and ARMv8
architecture.
Coming back to the support for Mali on LSK for Arndale, It would be interesting to try that out if GWG is planning to support the same.
Yes we are. We have an epic devoted to Mali support on the LSK.
From what I know, the current LSK tree doesn't have complete support for Arndale board and hence we don't have Arndale as one of the target for validating LSK.
I can't speak to all the features of the board. But I can say Show has accelerated Graphics with Mali + patches we obtained from the Samsung LT up and working on Arndale.
So like I mentioned I think a rebase of Show's branch with the LSK android tree might be quite quite close, least for something with a functional accelerated graphics stack.
Show would it be possible to give this is try?
Sure. I might be have a try for this.
But I don't have arndale on hand now. So I cannot have a test for it. Can I try this next Monday?
Regards, Khasim
On Fri, Mar 21, 2014 at 9:20 AM, Vishal Bhoj vishal.bhoj@linaro.org wrote:
To be more clear. The board supports accelerated graphics but the LT kernel doesn't have the drivers to have accelerated graphics support.
On 21 March 2014 19:49, Vishal Bhoj vishal.bhoj@linaro.org wrote:
Hi Botao,
There is no hw acceleration on arndale board.
On 21 March 2014 17:53, Botao Sun botao.sun@linaro.org wrote: > > Hi Vishal, > > I'm now looking at the logcat output of Samsung Arndale Android > image, > and found: > > D/libEGL ( 2167): No GPU support detected. Fallback to software > renderer. > D/libEGL ( 2167): loaded /system/lib/egl/libGLES_android.so > > Then: > > W/gralloc ( 2166): page flipping not supported (yres_virtual=720, > requested=1440) > I/gralloc ( 2166): using (fd=12) > I/gralloc ( 2166): id = > I/gralloc ( 2166): xres = 1280 px > I/gralloc ( 2166): yres = 720 px > I/gralloc ( 2166): xres_virtual = 1280 px > I/gralloc ( 2166): yres_virtual = 720 px > I/gralloc ( 2166): bpp = 16 > I/gralloc ( 2166): r = 11:5 > I/gralloc ( 2166): g = 5:6 > I/gralloc ( 2166): b = 0:5 > I/gralloc ( 2166): width = 1280 mm (25.400000 dpi) > I/gralloc ( 2166): height = 720 mm (25.400000 dpi) > I/gralloc ( 2166): refresh rate = 60.00 Hz > I/iptables( 2164): iptables terminated by exit(3) > E/Netd ( 2164): exec() res=0, status=768 for
/system/bin/iptables
> -t > filter -N bw_INPUT > I/ip6tables( 2164): ip6tables terminated by exit(3) > E/Netd ( 2164): exec() res=0, status=768 for
/system/bin/ip6tables
> -t > filter -N bw_INPUT > I/iptables( 2164): iptables terminated by exit(3) > E/Netd ( 2164): exec() res=0, status=768 for
/system/bin/iptables
> -t > filter -A INPUT -j bw_INPUT > I/ip6tables( 2164): ip6tables terminated by exit(3) > E/Netd ( 2164): exec() res=0, status=768 for
/system/bin/ip6tables
> -t > filter -A INPUT -j bw_INPUT > I/iptables( 2164): iptables terminated by exit(3) > E/Netd ( 2164): exec() res=0, status=768 for
/system/bin/iptables
> -t > filter -N fw_INPUT > I/SurfaceFlinger( 2166): Using composer version 1.0 > W/SurfaceFlinger( 2166): getting VSYNC period from fb HAL: 16666666 > W/SurfaceFlinger( 2166): no suitable EGLConfig found, trying a > simpler > query > W/SurfaceFlinger( 2166): EGL_SLOW_CONFIG selected! > I/SurfaceFlinger( 2166): EGL informations: > I/SurfaceFlinger( 2166): vendor : Android > I/SurfaceFlinger( 2166): version : 1.4 Android META-EGL > I/SurfaceFlinger( 2166): extensions: EGL_KHR_get_all_proc_addresses > EGL_ANDROID_presentation_time EGL_KHR_image_base EGL_KHR_fence_sync > EGL_A > I/SurfaceFlinger( 2166): Client API: OpenGL_ES > I/SurfaceFlinger( 2166): EGLSurface: 5-6-5-0, config=0x0 > I/SurfaceFlinger( 2166): OpenGL ES informations: > I/SurfaceFlinger( 2166): vendor : Android > I/SurfaceFlinger( 2166): renderer : Android PixelFlinger 1.4 > I/SurfaceFlinger( 2166): version : OpenGL ES-CM 1.0 > I/SurfaceFlinger( 2166): extensions: GL_EXT_debug_marker > GL_OES_byte_coordinates GL_OES_fixed_point GL_OES_single_precision > GL_OES_read_forma > I/SurfaceFlinger( 2166): GL_MAX_TEXTURE_SIZE = 4096 > I/SurfaceFlinger( 2166): GL_MAX_VIEWPORT_DIMS = 4096 > > As we know the Arndale board integrates dual-core A15 CPU and ARM > Mali-T604 GPU. If as the log described, "No GPU support detected", > then does > it mean that all the graphic work now is done by the dual-core A15 > CPU > itself? Though the speed for navigation among screens is fast and > 0xBenchmark test looks good as well. > > I may be wrong but in this condition, the board seems can't be > considered > as "Hardware Accelerated", at least not "GPU Hardware Accelerated". > Also, as > I know, "Android PixelFlinger" is a software renderer. > > Do you know more information about this? > > Thank you. > > > Best Regards > Botao Sun
linaro-android mailing list linaro-android@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-android
-- Regards, Tom
"Where's the kaboom!? There was supposed to be an earth-shattering kaboom!" Marvin Martian Tech Lead, Graphics Working Group | Linaro.org │ Open source software for ARM SoCs w) tom.gall att linaro.org h) tom_gall att mac.com
linaro-android mailing list linaro-android@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-android
-- Regards, Tom
"Where's the kaboom!? There was supposed to be an earth-shattering kaboom!" Marvin Martian Tech Lead, Graphics Working Group | Linaro.org │ Open source software for ARM SoCs w) tom.gall att linaro.org h) tom_gall att mac.com
So Vishal / Khasim, would you want me to report a bug based on the current status of Arndale hardware acceleration?
I ask because we do have test cases cover this feature, and test result in spreadsheet.
Thanks.
Best Regards Botao Sun
On 22 March 2014 02:14, Show Liu show.liu@linaro.org wrote:
Hi Tom,
On Fri, Mar 21, 2014 at 10:54 PM, Tom Gall tom.gall@linaro.org wrote:
Hi Vishal,
On Fri, Mar 21, 2014 at 9:40 AM, Vishal Bhoj vishal.bhoj@linaro.org wrote:
On 21 March 2014 20:02, Khasim Syed Mohammed <
khasim.mohammed@linaro.org>
wrote:
Hi all,
On 21 March 2014 19:58, Tom Gall tom.gall@linaro.org wrote:
The GWG does have a LSK kernel branch with Mali support. (IE accelerated graphics)
We haven't targeted Android as of yet but in the grand scheme things should be reasonably close. Show can say for certain but we'd need a rebase on linux-linaro-lsk-v3.10-android at a minimum.
I'm a little unclear how interesting the LSK android kernel is for the Android team. One of my buffered questions for Khasim.
We do have requests from members to support / maintain Android on LSK.
I
would let Vishal look at integration, if we find any issues then we
can jump
in to fix specific issues.
Cool.
We do validate Android version of the LSK on ARMv7 and ARMv8
architecture.
Coming back to the support for Mali on LSK for Arndale, It would be interesting to try that out if GWG is planning to support the same.
Yes we are. We have an epic devoted to Mali support on the LSK.
From what I know, the current LSK tree doesn't have complete support for Arndale board and hence we don't have Arndale as one of the target for validating LSK.
I can't speak to all the features of the board. But I can say Show has accelerated Graphics with Mali + patches we obtained from the Samsung LT up and working on Arndale.
So like I mentioned I think a rebase of Show's branch with the LSK android tree might be quite quite close, least for something with a functional accelerated graphics stack.
Show would it be possible to give this is try?
Sure. I might be have a try for this.
But I don't have arndale on hand now. So I cannot have a test for it. Can I try this next Monday?
Regards, Khasim
On Fri, Mar 21, 2014 at 9:20 AM, Vishal Bhoj vishal.bhoj@linaro.org wrote:
To be more clear. The board supports accelerated graphics but the LT kernel doesn't have the drivers to have accelerated graphics support.
On 21 March 2014 19:49, Vishal Bhoj vishal.bhoj@linaro.org wrote: > > Hi Botao, > > There is no hw acceleration on arndale board. > > > On 21 March 2014 17:53, Botao Sun botao.sun@linaro.org wrote: >> >> Hi Vishal, >> >> I'm now looking at the logcat output of Samsung Arndale Android >> image, >> and found: >> >> D/libEGL ( 2167): No GPU support detected. Fallback to software >> renderer. >> D/libEGL ( 2167): loaded /system/lib/egl/libGLES_android.so >> >> Then: >> >> W/gralloc ( 2166): page flipping not supported (yres_virtual=720, >> requested=1440) >> I/gralloc ( 2166): using (fd=12) >> I/gralloc ( 2166): id = >> I/gralloc ( 2166): xres = 1280 px >> I/gralloc ( 2166): yres = 720 px >> I/gralloc ( 2166): xres_virtual = 1280 px >> I/gralloc ( 2166): yres_virtual = 720 px >> I/gralloc ( 2166): bpp = 16 >> I/gralloc ( 2166): r = 11:5 >> I/gralloc ( 2166): g = 5:6 >> I/gralloc ( 2166): b = 0:5 >> I/gralloc ( 2166): width = 1280 mm (25.400000 dpi) >> I/gralloc ( 2166): height = 720 mm (25.400000 dpi) >> I/gralloc ( 2166): refresh rate = 60.00 Hz >> I/iptables( 2164): iptables terminated by exit(3) >> E/Netd ( 2164): exec() res=0, status=768 for
/system/bin/iptables
>> -t >> filter -N bw_INPUT >> I/ip6tables( 2164): ip6tables terminated by exit(3) >> E/Netd ( 2164): exec() res=0, status=768 for
/system/bin/ip6tables
>> -t >> filter -N bw_INPUT >> I/iptables( 2164): iptables terminated by exit(3) >> E/Netd ( 2164): exec() res=0, status=768 for
/system/bin/iptables
>> -t >> filter -A INPUT -j bw_INPUT >> I/ip6tables( 2164): ip6tables terminated by exit(3) >> E/Netd ( 2164): exec() res=0, status=768 for
/system/bin/ip6tables
>> -t >> filter -A INPUT -j bw_INPUT >> I/iptables( 2164): iptables terminated by exit(3) >> E/Netd ( 2164): exec() res=0, status=768 for
/system/bin/iptables
>> -t >> filter -N fw_INPUT >> I/SurfaceFlinger( 2166): Using composer version 1.0 >> W/SurfaceFlinger( 2166): getting VSYNC period from fb HAL:
16666666
>> W/SurfaceFlinger( 2166): no suitable EGLConfig found, trying a >> simpler >> query >> W/SurfaceFlinger( 2166): EGL_SLOW_CONFIG selected! >> I/SurfaceFlinger( 2166): EGL informations: >> I/SurfaceFlinger( 2166): vendor : Android >> I/SurfaceFlinger( 2166): version : 1.4 Android META-EGL >> I/SurfaceFlinger( 2166): extensions:
EGL_KHR_get_all_proc_addresses
>> EGL_ANDROID_presentation_time EGL_KHR_image_base
EGL_KHR_fence_sync
>> EGL_A >> I/SurfaceFlinger( 2166): Client API: OpenGL_ES >> I/SurfaceFlinger( 2166): EGLSurface: 5-6-5-0, config=0x0 >> I/SurfaceFlinger( 2166): OpenGL ES informations: >> I/SurfaceFlinger( 2166): vendor : Android >> I/SurfaceFlinger( 2166): renderer : Android PixelFlinger 1.4 >> I/SurfaceFlinger( 2166): version : OpenGL ES-CM 1.0 >> I/SurfaceFlinger( 2166): extensions: GL_EXT_debug_marker >> GL_OES_byte_coordinates GL_OES_fixed_point GL_OES_single_precision >> GL_OES_read_forma >> I/SurfaceFlinger( 2166): GL_MAX_TEXTURE_SIZE = 4096 >> I/SurfaceFlinger( 2166): GL_MAX_VIEWPORT_DIMS = 4096 >> >> As we know the Arndale board integrates dual-core A15 CPU and ARM >> Mali-T604 GPU. If as the log described, "No GPU support detected", >> then does >> it mean that all the graphic work now is done by the dual-core A15 >> CPU >> itself? Though the speed for navigation among screens is fast and >> 0xBenchmark test looks good as well. >> >> I may be wrong but in this condition, the board seems can't be >> considered >> as "Hardware Accelerated", at least not "GPU Hardware
Accelerated".
>> Also, as >> I know, "Android PixelFlinger" is a software renderer. >> >> Do you know more information about this? >> >> Thank you. >> >> >> Best Regards >> Botao Sun > >
linaro-android mailing list linaro-android@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-android
-- Regards, Tom
"Where's the kaboom!? There was supposed to be an earth-shattering kaboom!" Marvin Martian Tech Lead, Graphics Working Group | Linaro.org │ Open source software for ARM SoCs w) tom.gall att linaro.org h) tom_gall att mac.com
linaro-android mailing list linaro-android@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-android
-- Regards, Tom
"Where's the kaboom!? There was supposed to be an earth-shattering kaboom!" Marvin Martian Tech Lead, Graphics Working Group | Linaro.org │ Open source software for ARM SoCs w) tom.gall att linaro.org h) tom_gall att mac.com
linaro-android mailing list linaro-android@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-android
A bug has been reported:
https://bugs.launchpad.net/linaro-android/+bug/1298151
Thanks.
Best Regards Botao Sun
On 22 March 2014 15:04, Botao Sun botao.sun@linaro.org wrote:
So Vishal / Khasim, would you want me to report a bug based on the current status of Arndale hardware acceleration?
I ask because we do have test cases cover this feature, and test result in spreadsheet.
Thanks.
Best Regards Botao Sun
On 22 March 2014 02:14, Show Liu show.liu@linaro.org wrote:
Hi Tom,
On Fri, Mar 21, 2014 at 10:54 PM, Tom Gall tom.gall@linaro.org wrote:
Hi Vishal,
On Fri, Mar 21, 2014 at 9:40 AM, Vishal Bhoj vishal.bhoj@linaro.org wrote:
On 21 March 2014 20:02, Khasim Syed Mohammed <
khasim.mohammed@linaro.org>
wrote:
Hi all,
On 21 March 2014 19:58, Tom Gall tom.gall@linaro.org wrote:
The GWG does have a LSK kernel branch with Mali support. (IE accelerated graphics)
We haven't targeted Android as of yet but in the grand scheme things should be reasonably close. Show can say for certain but we'd need a rebase on linux-linaro-lsk-v3.10-android at a minimum.
I'm a little unclear how interesting the LSK android kernel is for
the
Android team. One of my buffered questions for Khasim.
We do have requests from members to support / maintain Android on
LSK. I
would let Vishal look at integration, if we find any issues then we
can jump
in to fix specific issues.
Cool.
We do validate Android version of the LSK on ARMv7 and ARMv8
architecture.
Coming back to the support for Mali on LSK for Arndale, It would be interesting to try that out if GWG is planning to support the same.
Yes we are. We have an epic devoted to Mali support on the LSK.
From what I know, the current LSK tree doesn't have complete support
for
Arndale board and hence we don't have Arndale as one of the target for validating LSK.
I can't speak to all the features of the board. But I can say Show has accelerated Graphics with Mali + patches we obtained from the Samsung LT up and working on Arndale.
So like I mentioned I think a rebase of Show's branch with the LSK android tree might be quite quite close, least for something with a functional accelerated graphics stack.
Show would it be possible to give this is try?
Sure. I might be have a try for this.
But I don't have arndale on hand now. So I cannot have a test for it. Can I try this next Monday?
Regards, Khasim
On Fri, Mar 21, 2014 at 9:20 AM, Vishal Bhoj <vishal.bhoj@linaro.org
wrote: > To be more clear. The board supports accelerated graphics but the
LT
> kernel > doesn't have the drivers to have accelerated graphics support. > > > On 21 March 2014 19:49, Vishal Bhoj vishal.bhoj@linaro.org
wrote:
>> >> Hi Botao, >> >> There is no hw acceleration on arndale board. >> >> >> On 21 March 2014 17:53, Botao Sun botao.sun@linaro.org wrote: >>> >>> Hi Vishal, >>> >>> I'm now looking at the logcat output of Samsung Arndale Android >>> image, >>> and found: >>> >>> D/libEGL ( 2167): No GPU support detected. Fallback to software >>> renderer. >>> D/libEGL ( 2167): loaded /system/lib/egl/libGLES_android.so >>> >>> Then: >>> >>> W/gralloc ( 2166): page flipping not supported (yres_virtual=720, >>> requested=1440) >>> I/gralloc ( 2166): using (fd=12) >>> I/gralloc ( 2166): id = >>> I/gralloc ( 2166): xres = 1280 px >>> I/gralloc ( 2166): yres = 720 px >>> I/gralloc ( 2166): xres_virtual = 1280 px >>> I/gralloc ( 2166): yres_virtual = 720 px >>> I/gralloc ( 2166): bpp = 16 >>> I/gralloc ( 2166): r = 11:5 >>> I/gralloc ( 2166): g = 5:6 >>> I/gralloc ( 2166): b = 0:5 >>> I/gralloc ( 2166): width = 1280 mm (25.400000 dpi) >>> I/gralloc ( 2166): height = 720 mm (25.400000 dpi) >>> I/gralloc ( 2166): refresh rate = 60.00 Hz >>> I/iptables( 2164): iptables terminated by exit(3) >>> E/Netd ( 2164): exec() res=0, status=768 for
/system/bin/iptables
>>> -t >>> filter -N bw_INPUT >>> I/ip6tables( 2164): ip6tables terminated by exit(3) >>> E/Netd ( 2164): exec() res=0, status=768 for
/system/bin/ip6tables
>>> -t >>> filter -N bw_INPUT >>> I/iptables( 2164): iptables terminated by exit(3) >>> E/Netd ( 2164): exec() res=0, status=768 for
/system/bin/iptables
>>> -t >>> filter -A INPUT -j bw_INPUT >>> I/ip6tables( 2164): ip6tables terminated by exit(3) >>> E/Netd ( 2164): exec() res=0, status=768 for
/system/bin/ip6tables
>>> -t >>> filter -A INPUT -j bw_INPUT >>> I/iptables( 2164): iptables terminated by exit(3) >>> E/Netd ( 2164): exec() res=0, status=768 for
/system/bin/iptables
>>> -t >>> filter -N fw_INPUT >>> I/SurfaceFlinger( 2166): Using composer version 1.0 >>> W/SurfaceFlinger( 2166): getting VSYNC period from fb HAL:
16666666
>>> W/SurfaceFlinger( 2166): no suitable EGLConfig found, trying a >>> simpler >>> query >>> W/SurfaceFlinger( 2166): EGL_SLOW_CONFIG selected! >>> I/SurfaceFlinger( 2166): EGL informations: >>> I/SurfaceFlinger( 2166): vendor : Android >>> I/SurfaceFlinger( 2166): version : 1.4 Android META-EGL >>> I/SurfaceFlinger( 2166): extensions:
EGL_KHR_get_all_proc_addresses
>>> EGL_ANDROID_presentation_time EGL_KHR_image_base
EGL_KHR_fence_sync
>>> EGL_A >>> I/SurfaceFlinger( 2166): Client API: OpenGL_ES >>> I/SurfaceFlinger( 2166): EGLSurface: 5-6-5-0, config=0x0 >>> I/SurfaceFlinger( 2166): OpenGL ES informations: >>> I/SurfaceFlinger( 2166): vendor : Android >>> I/SurfaceFlinger( 2166): renderer : Android PixelFlinger 1.4 >>> I/SurfaceFlinger( 2166): version : OpenGL ES-CM 1.0 >>> I/SurfaceFlinger( 2166): extensions: GL_EXT_debug_marker >>> GL_OES_byte_coordinates GL_OES_fixed_point
GL_OES_single_precision
>>> GL_OES_read_forma >>> I/SurfaceFlinger( 2166): GL_MAX_TEXTURE_SIZE = 4096 >>> I/SurfaceFlinger( 2166): GL_MAX_VIEWPORT_DIMS = 4096 >>> >>> As we know the Arndale board integrates dual-core A15 CPU and ARM >>> Mali-T604 GPU. If as the log described, "No GPU support
detected",
>>> then does >>> it mean that all the graphic work now is done by the dual-core
A15
>>> CPU >>> itself? Though the speed for navigation among screens is fast and >>> 0xBenchmark test looks good as well. >>> >>> I may be wrong but in this condition, the board seems can't be >>> considered >>> as "Hardware Accelerated", at least not "GPU Hardware
Accelerated".
>>> Also, as >>> I know, "Android PixelFlinger" is a software renderer. >>> >>> Do you know more information about this? >>> >>> Thank you. >>> >>> >>> Best Regards >>> Botao Sun >> >> > > > _______________________________________________ > linaro-android mailing list > linaro-android@lists.linaro.org > http://lists.linaro.org/mailman/listinfo/linaro-android >
-- Regards, Tom
"Where's the kaboom!? There was supposed to be an earth-shattering kaboom!" Marvin Martian Tech Lead, Graphics Working Group | Linaro.org │ Open source software for ARM SoCs w) tom.gall att linaro.org h) tom_gall att mac.com
linaro-android mailing list linaro-android@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-android
-- Regards, Tom
"Where's the kaboom!? There was supposed to be an earth-shattering kaboom!" Marvin Martian Tech Lead, Graphics Working Group | Linaro.org │ Open source software for ARM SoCs w) tom.gall att linaro.org h) tom_gall att mac.com
linaro-android mailing list linaro-android@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-android
linaro-android@lists.linaro.org
-
Botao Sun -
Khasim Syed Mohammed -
Show Liu -
Tom Gall -
Vishal Bhoj