How to enable Imagination Technologies's PowerVR SGX 540 driver?

211 views
Skip to first unread message

Mr.32

unread,
Feb 10, 2012, 1:39:50 AM2/10/12
to JetDroid
When i boot android with my linux kernel with some patches

shows following log

D/libEGL ( 2200): loaded /vendor/lib/egl/
libGLESv1_CM_POWERVR_SGX540_120.so
D/libEGL ( 2200): loaded /vendor/lib/egl/
libGLESv2_POWERVR_SGX540_120.so
W/libEGL ( 2200): 0: eglInitialize(0x1) failed (EGL_BAD_ALLOC)
I/SurfaceFlinger( 2200): EGL informations:
I/SurfaceFlinger( 2200): # of configs : 8
I/SurfaceFlinger( 2200): vendor : Android
I/SurfaceFlinger( 2200): version : 1.4 Android META-EGL
I/SurfaceFlinger( 2200): extensions: EGL_KHR_image EGL_KHR_image_base
EGL_KHR_image_pixmap EGL_ANDROID_image_native_buffer
EGL_ANDROID_swap_rectangle
I/SurfaceFlinger( 2200): Client API: OpenGL ES
I/SurfaceFlinger( 2200): EGLSurface: 8-8-8-0, config=0x2
I/SurfaceFlinger( 2200): OpenGL informations:
I/SurfaceFlinger( 2200): vendor : Android
I/SurfaceFlinger( 2200): renderer : Android PixelFlinger 1.4
I/SurfaceFlinger( 2200): version : OpenGL ES-CM 1.0
I/SurfaceFlinger( 2200): extensions: GL_OES_byte_coordinates
GL_OES_fixed_point GL_OES_single_precision GL_OES_read_format
GL_OES_compressed_paletted_textur
I/SurfaceFlinger( 2200): GL_MAX_TEXTURE_SIZE = 4096
I/SurfaceFlinger( 2200): GL_MAX_VIEWPORT_DIMS = 4096
I/SurfaceFlinger( 2200): flags = 000c0000
D/SensorService( 2200): nuSensorService starting...
E/SensorService( 2200): couldn't load sensors module (No such file or
directory)
I/sysproc ( 2200): System server: starting Android runtime.
I/sysproc ( 2200): System server: starting Android services.
I/sysproc ( 2200): System server: entering thread pool.


here i want following log

I/SurfaceFlinger( 1663): EGL informations:
I/SurfaceFlinger( 1663): # of configs : 36
I/SurfaceFlinger( 1663): vendor : Android
I/SurfaceFlinger( 1663): version : 1.4 Android META-EGL
I/SurfaceFlinger( 1663): extensions: EGL_KHR_image EGL_KHR_image_base
EGL_KHR_image_pixmap EGL_ANDROID_image_native_buffer
EGL_ANDROID_swap_rectangle
I/SurfaceFlinger( 1663): Client API: OpenGL ES
I/SurfaceFlinger( 1663): EGLSurface: 8-8-8-0, config=0x7
I/SurfaceFlinger( 1663): OpenGL informations:
I/SurfaceFlinger( 1663): vendor : Imagination Technologies
I/SurfaceFlinger( 1663): renderer : PowerVR SGX 540
I/SurfaceFlinger( 1663): version : OpenGL ES-CM 1.1
I/SurfaceFlinger( 1663): extensions: GL_OES_byte_coordinates
GL_OES_fixed_point GL_OES_single_precision GL_OES_matrix_get
GL_OES_read_format GL_OES_compressed_paletted_texture
GL_OES_point_sprite GL_OES_point_size_array GL_OES_matrix_palette
GL_OES_draw_texture GL_OES_query_matrix GL_OES_texture_env_crossbar
GL_OES_texture_mirrored_repeat GL_OES_texture_cube_map
GL_OES_blend_subtract GL_OES_blend_func_separate
GL_OES_blend_equation_separate GL_OES_stencil_wrap
GL_OES_extended_matrix_palette GL_OES_framebuffer_object
GL_OES_rgb8_rgba8 GL_OES_depth24 GL_OES_stencil8
GL_OES_compressed_ETC1_RGB8_texture GL_OES_mapbuffer GL_OES_EGL_image
GL_EXT_multi_draw_arrays GL_OES_required_internalformat
GL_IMG_read_format GL_IMG_texture_compression_pvrtc
GL_IMG_texture_format_BGRA8888 GL_EXT_texture_format_BGRA8888
GL_IMG_texture_stream GL_OES_egl_sync GL_IMG_vertex_array_object


i want to load PowerVR SGX 540 of Imagination Technologies instead
of Android's Android PixelFlinger 1.4 so how can i do that? what
should i eneble in mu linux kernel code?

wakey

unread,
Jan 15, 2013, 2:23:36 PM1/15/13
to jetd...@googlegroups.com
As far as i understand it, that is not possible, but i might be wrong.
Afaik the Jet's cpu is a S3C6410, which is a Soc with a own integrated gpu, which is not compatible with the PowerVR drivers.
PixelFlinger on the other hand seems to be a generic driver (like window's standard vga driver), and therefore works with the chip, but does not deliver the wanted performance.
The Galaxy Spica has the required S3C6410 driver, but Samsung realy messed it up (just like it's Windows Mobile pendant), it simply sucks.
Someone tried to do a complete own "from-scratch" version of this driver for the Galaxy Spica and Omnia2Droid (Android for Omnia II and Pro), but i dont know if it ever was finished to a usable degree.

If you are not interested in it just for technical reasons, i would say save some bucks for the cheapest android device available, as even such a device will be faster, more reliable and superior in many other aspects nowadays.
Reply all
Reply to author
Forward
0 new messages