TeamForge : Post

Forum Topic - Software Rasterizer vs. Coral?:

View: as

Malte Mundt(deleted)

08/19/2009 7:37 AM

post36243

Hi,

on my MPC5200 with Coral-P, 6.4.1, I start egl-gears and get:

# egl-gears -info   
GL_RENDERER   = Software Rasterizer
GL_VERSION    = OpenGL ES-CM 1.0
GL_VENDOR     = QNX Software Systems
GL_EXTENSIONS = GL_OES_compressed_paletted_texture GL_OES_vertex_buffer_object GL_OES_query_matrix GL_OES_read_format
156 frames in  5.025 seconds = 31.045 FPS
155 frames in  5.026 seconds = 30.840 FPS

with egl-tunnel on the same hardware, I get:

# egl-tunnel -info
GL_RENDERER   = Fujitsu Coral
GL_VERSION    = OpenGL ES-CM 1.0
GL_VENDOR     = QNX Software Systems
GL_EXTENSIONS = GL_OES_compressed_paletted_texture GL_OES_vertex_buffer_object GL_OES_query_matrix GL_OES_read_format 
GL_QNX
_stippled_lines
53 frames in  5.058 seconds = 10.478 FPS

Why is GL_RENDERER not always 'Fujitsu Coral'?


- Malte

Etienne Belanger(deleted)

08/19/2009 8:45 AM

post36251

Re: Software Rasterizer vs. Coral?

There is a bug in egl-gears. It calls glGetString before eglGetDisplay, eglInitialize, eglCreateContext, 
eglCreate[xyz]Surface, and eglMakeCurrent. Normally, the returned strings in this case should be NULL and the problem 
would have been rectified. However, this implementation of EGL returns the software rasterizer strings until a 
connection to a real OpenGL ES device is established.

The problem was fixed in egl-tunnel.

Malte Mundt(deleted)

08/19/2009 9:02 AM

post36253

Re: Software Rasterizer vs. Coral?

So it actually does use the hardware to render, only prints out wrong information? Ok, glad to hear this. Thanks.


- Malte

Return