• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 99 subscribers
  • Views 678 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

OpenGL ES + OpenVG on OMAP 3530

Mikhail Kulikov
Prodigy 20 points

Other Parts Discussed in Thread: OMAP3530

Is it possible to use API OpenGL (for rendering 3D graphics) and API OpenVG (for rendering 2D graphics over 3D graphics) simultaneously (using the same graphics context)? Also what type of hardware acceleration uses OMAP 3530 in this case? Freescale shows ( http://www.youtube.com/watch?v=qUQzlf2hqQ8 ) two GPU in i.MX 51 for  that purpose. That is just a marketing trick or real hardware design differencies? 

 

  • 0
    TI__Intellectual 1910 points

    Mikhail,

       OpenGL ES and OpenVG rely upon a common EGL driver to allocate drawing surfaces called EGL Surfaces.  Either API can render to a common EGL Surface.  There are also other ways to combine 2D and 3D, such as using Render to Texture techniques or the Display Subsystem feature of OMAP which provides a sort of hardware windowing capability.

    http://processors.wiki.ti.com/index.php/Render_to_Texture_with_OpenGL_ES

    http://processors.wiki.ti.com/index.php/Display_Subsystem

       I doubt the i.MX51 has a separate processor just for OpenVG, but I don't know the details of that architecture.  OpenVG was designed to process 2D vector graphics on 3D cores, which is what we do on OMAP.   i.MX51 does have a separate 2D BitBlt function, but that is not an OpenVG accelerator.  Accelerating OpenVG requires hardware that can do the 2x3 affine transforms that OpenVG is built on.  OpenGL ES cores can do that, such as the PowerVR SGX530 core in OMAP3530.  The PowerVR SGX530 core has 2 internal processing units called USSEs.  A microkernel automatically balances the processing load between the USSEs.  For OpenGL ES, one unit would typically handle geometry processing while the other handles fragment/pixel processing.  When OpenVG, is used with OpenGL ES, one or both of the USSEs will handle the processing for OpenVG.

    Regards, Clay

     

  • 0 in reply to Clay Montgomery
    Prodigy 20 points

    Thanks Clay for detailed answer !