The spec of DTV SoC was release. I got the HW spec. And I found the design was not consider about "shader". Our HW architecture was a VG pipe line, almost like http://www.khronos.org/assets/uploads/apis/openvg_pipeline1.jpg Is this means that it is not make sense to write a Gallium driver for GL/VG state tracker? 2011/4/11 Corbin Simpson <mostawesomed...@gmail.com>
> On Fri, Apr 8, 2011 at 4:17 AM, Awin <awin0...@gmail.com> wrote: > > Hi all, > > I need to write a OpenGL driver for my company's IC, and base on > gallium, > > how do I get start? Is there any document or sample code to reference? > > This is a remarkably candid question. > > In the Mesa tree, the Gallium headers (src/gallium/include/**/*.h) > describe the objects Gallium passes around. There are also Sphinx docs > (src/gallium/docs/) which probably haven't really been maintained in a > bit, but it's nice to think that they are somewhat accurate. > > Gallium is laid out like this: There is a struct called Winsys which > handles talking to your hardware backend (DRM, Windows kernel, etc.), > a struct called Screen which helps to manage your GPU's information > and resources, and a struct called Context which is, well, a rendering > context. > > Which SoC is this? Do you have docs? Are you going to open-source any > of your driver code? > > It's going to be a lot easier to answer your questions in realtime; > there's an IRC channel on Freenode, #dri-devel, which is the general > Gallium channel (among other things), and is a great place to ask > questions. > > Hope this helps somewhat, > ~ C. > > -- > When the facts change, I change my mind. What do you do, sir? ~ Keynes > > Corbin Simpson > <mostawesomed...@gmail.com> >
_______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
