
Originally Posted by
Agent D
Does your RTOS already have an OpenGL(R) implementation or OpenGL(R)-like library? There must be some documentation about driver development (the library and the RTOS). You might want to contact the vendor of the library and/or the RTOS. How much of the library is implemented in software? Maybe you just need to copy pixels into video memory, maybe you have to send rendering commands to the graphics core. What concept of graphics does your RTOS have anyway? In this case you just need to find the right documentation.
If you don't have an OpenGL(R) like library, you need to write the library yourself. Depending on what the controller does, you send a stream of rendering commands at some time. If the graphics core is just a dumb display driver, you will have to write an entire software rasterizer. Especially in the later case, I would advice against aiming for full OpenGL(R) compatibillity (except if that is an explicit design goal). Maybe just something OpenGL(R) 1.x similar minus everything you don't use. (Since you already wrote software for the OpenGL(R) specification)