SlateDroid.com: Fix for Mali opengl hardware rendering! - SlateDroid.com

Jump to content


Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

Fix for Mali opengl hardware rendering!

#1 User is offline   johnciaccio 

  • Member
  • PipPip
  • Group: Jr. Member
  • Topics: 3
  • Posts: 24
  • Joined: 30-July 10

Posted 03 October 2010 - 11:43 AM

Ok I ahd alot of time again and got accelerated opengl running. Instructions:The kernel driver mali.ko is being inserted to late (after start of VM). I added a line:insmod /system/lib/mali.koat the first insmod section (it was in the second one originally) to the init.tcc92xx file.Follow those instructions. Hopefully someone who has more time then me can put out a new zip files for those less technical.Don't forget to give prop credit though ;)As far as the g-sensor is concerned: The init has the lines commented out and the akmd deamon is missing in the system. Can someone find this somewhere?Also there are 2 other kernel modules missing but are in the init to run. They maybe for the g-sensor or bluetooth. There are alot of stuff in the init. Check out the dmesg.Ok hope this helps.btw it runs really nice now. I just wish I had more time with a internet connectiion to posts some videos. Gonna try it monday.Update: glinfo detects only 1.0
0

#2 User is offline   Asure 

  • Advanced Member
  • PipPipPip
  • Group: Hero Member
  • Topics: 24
  • Posts: 787
  • Joined: 26-May 10

Posted 03 October 2010 - 12:10 PM

Inserting a .so file is impossible, only .ko files can be insmodded maybe a typo ?Do you mean like this then ?
on early-init    device mtd@misc 0460 radio diag    device mtd@tcc 0666 root video    insmod /lib/modules/tcc92x_nand.ko    insmod /lib/modules/viqe.ko    insmod /lib/modules/tcc_sdio.ko    insmod /lib/modules/unifi_sdio.ko    insmod /lib/modules/ufsd.ko    insmod /system/lib/modules/mali.ko
We'd have to edit boot.img for this then (as those files are read-only)Edit: i modded my boot.img for a similar tablet with MALI (hsg-x5a) but i see no improvements at all. Please post your init.tcc92xx file :)
0

#3 User is offline   johnciaccio 

  • Member
  • PipPip
  • Group: Jr. Member
  • Topics: 3
  • Posts: 24
  • Joined: 30-July 10

Posted 04 October 2010 - 07:30 AM

Asure;69890]Inserting a .so file is impossible, on only .ko files can be insmodded maybe a typo ?Do you mean like this then ?[code, said:

on early-init device mtd@misc 0460 radio diag device mtd@tcc 0666 root video insmod /lib/modules/tcc92x_nand.ko insmod /lib/modules/viqe.ko insmod /lib/modules/tcc_sdio.ko insmod /lib/modules/unifi_sdio.ko insmod /lib/modules/ufsd.ko insmod /system/lib/modules/mali.ko[/code]We'd have to edit boot.img for this then (as those files are read-only)Edit: i modded my boot.img for a similar tablet with MALI (hsg-x5a) but i see no improvements at all. Please post your init.tcc92xx file :(
Thats it. Works on gt. I copied mine over in a console with root privs. Have you tried it on the gt??
0

#4 User is offline   manusube 

  • Newbie
  • Pip
  • Group: Jr. Member
  • Topics: 0
  • Posts: 1
  • Joined: 11-September 10

Posted 04 October 2010 - 09:08 AM

Quote

Before use of Mali OpenGL libraries, the device driver mali.ko must be inserted into system, e.g. by "insmod mali.ko" command. When the kernel module is inserted, a device node "/dev/mali" should be created by command "mknod /dev/mali c 241 0", which provides the communication between the OpenGL libraries and the kernel driver
Maybe this could help ;)
0

#5 User is offline   johnciaccio 

  • Member
  • PipPip
  • Group: Jr. Member
  • Topics: 3
  • Posts: 24
  • Joined: 30-July 10

Posted 04 October 2010 - 10:55 AM

Android Device telechips / tcc8900 / Android for Telechips TCC8900 Evaluation Board (US) 2.1-update1 / armeabi-v6OpenGL Version OpenGL ES-CM 1.1OpenGL Vendor ARMOpenGL Renderer Mali-200OpenGL Extensions OES_EGL_image OES_byte_coordinates OES_compressed_ETC1_RGB8_texture OES_compressed_paletted_texture OES_draw_texture OES_fixed_point OES_matrix_get OES_matrix_palette OES_point_size_array OES_point_sprite OES_query_matrix OES_read_format OES_single_precisionLimits OpenGL 1.0 ALIASED_LINE_WIDTH_RANGE = 0,100 ALIASED_POINT_SIZE_RANGE = 1,100 MAX_ELEMENTS_INDICES = 0 MAX_ELEMENTS_VERTICES = 0 MAX_LIGHTS = 8 MAX_MODELVIEW_STACK_DEPTH = 32 MAX_PROJECTION_STACK_DEPTH = 32 MAX_TEXTURE_SIZE = 4096 MAX_TEXTURE_STACK_DEPTH = 32 MAX_TEXTURE_UNITS = 8 MAX_VIEWPORT_DIMS = 4096,4096 SMOOTH_LINE_WIDTH_RANGE = 0,100 SMOOTH_POINT_SIZE_RANGE = 1,100 SUBPIXEL_BITS = 4Limits OpenGL 1.1 MAX_CLIP_PLANES = 1Limits OpenGL 1.1 Ext MAX_COLOR_ATTACHMENTS_OES = 0 MAX_CUBE_MAP_TEXTURE_SIZE = 0 MAX_PALETTE_MATRICES_OES = 32 MAX_RENDERBUFFER_SIZE_OES = 0 MAX_VERTEX_UNITS_OES = 4Display Resolution Pixels = 800 x 480 DPIs = 160.0 x 160.42105Display Configurations Standard 04: R5G6B5 D16 Native 00: R5G6B5 D24 S8 Native 05: R5G6B5 D16 MSAAx4 Native 01: R5G6B5 D24 S8 MSAAx4 Native 03: R5G5B5A1 D24 S8 MSAAx4 Native 07: R8G8B8A8 D24 S8 Native 08: R8G8B8A8 D24 S8 MSAAx4 Native Non Conformant 06: R5G6B5 D16 MSAAx16 Native 02: R5G6B5 D24 S8 MSAAx16 Native 09: R8G8B8A8 D24 S8 MSAAx16 Native Slow 12: R5G6B5 Native 13: R5G6B5 D16 Native 14: R8G8B8 Native 15: R8G8B8 D16 Native 16: R8G8B8A8 Native 17: R8G8B8A8 D16 Native 18: A8 Native 19: A8 D16 NativeCompressed Texture Formats Reported 8b90: PALETTE4_RGB8_OES 8b91: PALETTE4_RGBA8_OES 8b92: PALETTE4_R5_G6_B5_OES 8b93: PALETTE4_RGBA4_OES 8b94: PALETTE4_RGB5_A1_OES 8b95: PALETTE8_RGB8_OES 8b96: PALETTE8_RGBA8_OES 8b97: PALETTE8_R5_G6_B5_OES 8b98: PALETTE8_RGBA4_OES 8b99: PALETTE8_RGB5_A1_OES 8d64: ETC1_RGB8_OESEGL Vendor & Version Android 1.4 Android META-EGLEGL Extensions ANDROID_get_render_buffer ANDROID_image_native_buffer ANDROID_swap_rectangle KHR_image KHR_image_base KHR_image_pixmapGlinfo output it looks like augen had just made a small mistake.
0

#6 User is offline   johnciaccio 

  • Member
  • PipPip
  • Group: Jr. Member
  • Topics: 3
  • Posts: 24
  • Joined: 30-July 10

Posted 04 October 2010 - 10:56 AM

Android Device telechips / tcc8900 / Android for Telechips TCC8900 Evaluation Board (US) 2.1-update1 / armeabi-v6OpenGL Version OpenGL ES-CM 1.1OpenGL Vendor ARMOpenGL Renderer Mali-200OpenGL Extensions OES_EGL_image OES_byte_coordinates OES_compressed_ETC1_RGB8_texture OES_compressed_paletted_texture OES_draw_texture OES_fixed_point OES_matrix_get OES_matrix_palette OES_point_size_array OES_point_sprite OES_query_matrix OES_read_format OES_single_precisionLimits OpenGL 1.0 ALIASED_LINE_WIDTH_RANGE = 0,100 ALIASED_POINT_SIZE_RANGE = 1,100 MAX_ELEMENTS_INDICES = 0 MAX_ELEMENTS_VERTICES = 0 MAX_LIGHTS = 8 MAX_MODELVIEW_STACK_DEPTH = 32 MAX_PROJECTION_STACK_DEPTH = 32 MAX_TEXTURE_SIZE = 4096 MAX_TEXTURE_STACK_DEPTH = 32 MAX_TEXTURE_UNITS = 8 MAX_VIEWPORT_DIMS = 4096,4096 SMOOTH_LINE_WIDTH_RANGE = 0,100 SMOOTH_POINT_SIZE_RANGE = 1,100 SUBPIXEL_BITS = 4Limits OpenGL 1.1 MAX_CLIP_PLANES = 1Limits OpenGL 1.1 Ext MAX_COLOR_ATTACHMENTS_OES = 0 MAX_CUBE_MAP_TEXTURE_SIZE = 0 MAX_PALETTE_MATRICES_OES = 32 MAX_RENDERBUFFER_SIZE_OES = 0 MAX_VERTEX_UNITS_OES = 4Display Resolution Pixels = 800 x 480 DPIs = 160.0 x 160.42105Display Configurations Standard 04: R5G6B5 D16 Native 00: R5G6B5 D24 S8 Native 05: R5G6B5 D16 MSAAx4 Native 01: R5G6B5 D24 S8 MSAAx4 Native 03: R5G5B5A1 D24 S8 MSAAx4 Native 07: R8G8B8A8 D24 S8 Native 08: R8G8B8A8 D24 S8 MSAAx4 Native Non Conformant 06: R5G6B5 D16 MSAAx16 Native 02: R5G6B5 D24 S8 MSAAx16 Native 09: R8G8B8A8 D24 S8 MSAAx16 Native Slow 12: R5G6B5 Native 13: R5G6B5 D16 Native 14: R8G8B8 Native 15: R8G8B8 D16 Native 16: R8G8B8A8 Native 17: R8G8B8A8 D16 Native 18: A8 Native 19: A8 D16 NativeCompressed Texture Formats Reported 8b90: PALETTE4_RGB8_OES 8b91: PALETTE4_RGBA8_OES 8b92: PALETTE4_R5_G6_B5_OES 8b93: PALETTE4_RGBA4_OES 8b94: PALETTE4_RGB5_A1_OES 8b95: PALETTE8_RGB8_OES 8b96: PALETTE8_RGBA8_OES 8b97: PALETTE8_R5_G6_B5_OES 8b98: PALETTE8_RGBA4_OES 8b99: PALETTE8_RGB5_A1_OES 8d64: ETC1_RGB8_OESEGL Vendor & Version Android 1.4 Android META-EGLEGL Extensions ANDROID_get_render_buffer ANDROID_image_native_buffer ANDROID_swap_rectangle KHR_image KHR_image_base KHR_image_pixmapGlinfo output it looks like augen had just made a small mistake.
0

#7 User is offline   onihiro 

  • Advanced Member
  • PipPipPip
  • Group: Jr. Member
  • Topics: 11
  • Posts: 75
  • Joined: 08-August 10

Posted 04 October 2010 - 11:59 AM

paste bin
0

#8 User is offline   marcelol 

  • Advanced Member
  • PipPipPip
  • Group: Jr. Member
  • Topics: 3
  • Posts: 53
  • Joined: 07-August 10

Posted 05 October 2010 - 08:39 PM

care to post a step by step on how to update this......or if they have a boot.img with the mods....?
0

#9 User is offline   johnciaccio 

  • Member
  • PipPip
  • Group: Jr. Member
  • Topics: 3
  • Posts: 24
  • Joined: 30-July 10

Posted 07 October 2010 - 10:09 AM

Sorry , I am limited on internet acess time. I will try to put it in a update.zip. No boot image was needed. Only a modified tcc init file on my system.
0

#10 User is offline   angus1357 

  • Member
  • PipPip
  • Group: Jr. Member
  • Topics: 0
  • Posts: 15
  • Joined: 24-August 10

Posted 13 October 2010 - 07:29 AM

So all we have to do is add the line (...mali.ko) to the TCC init file? Where is that located?
0

#11 User is offline   Asure 

  • Advanced Member
  • PipPipPip
  • Group: Hero Member
  • Topics: 24
  • Posts: 787
  • Joined: 26-May 10

Posted 13 October 2010 - 09:19 AM

For the record, those init files are not editable over adb, even with root privs.They are read-only in the boot.img. So i don't know why this got stickied at first..To prove my point, pull the mali.ko from the system with adb and then delete it. Reboot the system. Run a game. -> no OpenGLPut back the mali.ko in the right place, reboot system -> check differences.I used to think mali was broken on my telechips pads too, but it's actually working fine. Performance isn't that great, but you can certainly see the difference without it running.
0

#12 User is offline   johnciaccio 

  • Member
  • PipPip
  • Group: Jr. Member
  • Topics: 3
  • Posts: 24
  • Joined: 30-July 10

Posted 14 October 2010 - 03:03 PM

Actually they are in the base directory /You can use su from the terminal then copy them to the sdcard to edit them.Then from the terminal mv them back to /It is not hard.
0

#13 User is offline   sifon187 

  • Advanced Member
  • PipPipPip
  • Group: Hero Member
  • Topics: 18
  • Posts: 460
  • Joined: 19-August 10

Posted 14 October 2010 - 04:56 PM

Quote

Actually they are in the base directory /You can use su from the terminal then copy them to the sdcard to edit them.Then from the terminal mv them back to /It is not hard.
Can a post a quick how to for the poeple who want to try this? I know your time online is short, but it would be very helpful in keeping the GT78 community going.
0

#14 User is offline   johnciaccio 

  • Member
  • PipPip
  • Group: Jr. Member
  • Topics: 3
  • Posts: 24
  • Joined: 30-July 10

Posted 15 October 2010 - 02:09 PM

make sure you are rooted and have a es file explorer installed.go Dev Tools>Terminal Emulator (at the bottom of the menu) make sure you are in portrait mode.in terminal type su and hit enterYour system should ask you if you would allow superuser permission hit always.type cd /type mv init.tcc* /sdcardnow you should have the init.tcc92xx.rc in your sdcard directoryopen it up with es file explorer as txt filego down to the line that says "insmod /lib/modules/ufsd.ko"after that lin enter "insmod /system/lib/modules/mali.ko" without the quotes of coursenow you can hit menu key and save the fileNow go back to the terminal and typemv /sdcard/init.tcc* /hit enternow reboot and it should be working.
0

#15 User is offline   Asure 

  • Advanced Member
  • PipPipPip
  • Group: Hero Member
  • Topics: 24
  • Posts: 787
  • Joined: 26-May 10

Posted 15 October 2010 - 03:57 PM

Again, those files are stored inside the boot.img and can not be edited.You need to unpack boot.img with some of the tools out there and add back the init.rc* files. Pushing them may seem like it's ok, but they can't be written. Pull them after pushing, to see what i mean. I'd suggest to close this topic, since it's going nowhere and will not lead to improved mali performance.
0

#16 User is offline   Amblin 

  • Advanced Member
  • PipPipPip
  • Group: Jr. Member
  • Topics: 2
  • Posts: 31
  • Joined: 08-October 10

Posted 15 October 2010 - 04:00 PM

[quote name='Asure;75480] I used to think mali was broken on my telechips pads too' date=' but it's actually working fine. Performance isn't that great, but you can certainly see the difference without it running.[/QUOTE'] I'm curious as to what a working Mali 200 produces in Quadrant Advanced 2d and 3d tests. On my V3 I get 120 and 221 on 2D and 3D respectively - fairly low if you compare to the results of a An3DBench run which gives 5.3K~, higher than the Dell Streak and other high powered mobiles. This an example of not working vs working?
0

#17 User is offline   marcelol 

  • Advanced Member
  • PipPipPip
  • Group: Jr. Member
  • Topics: 3
  • Posts: 53
  • Joined: 07-August 10

Posted 23 October 2010 - 07:04 PM

Bump...
0

Share this topic:


Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

1 User(s) are reading this topic
0 members, 1 guests, 0 anonymous users