Liam,

Did you see the flow chart at
http://dri.sourceforge.net/doc/control_flow_poster.jpg

Smitty wrote:
> 
> Howzit?
> 
> I would like to confirm my understanding of the various data paths between 
>applications (both direct and indirect rendering) and the graphics hardware.
> 
> First I have the path of 3D data between the 3D direct rendering program and the 
>graphics hardware which is pretty simple.
> 
> Direct rendering program (3D stuff)
>       |
> Direct rendering (3D data)
>       |
>    3D data
>       |
> Graphics hardware
> 
> Second I have the path of 2D data between the 3D direct rendering program and the 
>graphics hardware. Here I would like some clarification where I have question marks.
> 
> Direct rendering program (2D stuff)
>      |
> X protocol encode (2D data)
>      |
>   2D data
>      |
> ? X-server ?
> ? Decode and dispatch ?
> ? DDX Driver ?
>      |
>   2D data
>      |
> Graphics hardware
> 
> Third I have the path of 2D data between the 3D indirect rendering program and the 
>graphics hardware. Again I would like some clarification where I have put question 
>marks.
> 
> Indirect rendering program (2D stuff)
>      |
> X protocol encode (2D data)
>      |
>   2D data
>      |
> ? X-server ?
> ? Decode and dispatch ?
> ? DDX Driver ?
>      |
>   2D data
>      |
> Graphics hardware
> 
> Lastly I have the path of 3D data between the 3D indirect rendering program and the 
>graphics hardware. Again more clarification where there are question marks.
> 
> Indirect rendering program (3D stuff)
>      |
> OpenGL encode (3D data)
>      |
>   3D data
>      |
> ? X-server ?
> ? Decode and dispatch ?
> ? DDX Driver ?
>      |
>   2D data
>      |
> Graphics hardware
> 
> Are the, ????? encode , lines "processes" ie they create / produce the 2D (X 
>Protocol encoding) or 3D (OpenGl encoding) data?
> 
> The main thing I want to know is what happens between the Encoding and the Graphics 
>hardware.
> 
> Please point out any errors.
> 
> This information will be used as part of the documentation for DRI in the form of a 
>flow chart.
> 
> cheers
> Liam
> 
> _______________________________________________________________
> 
> Don't miss the 2002 Sprint PCS Application Developer's Conference
> August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
> 
> _______________________________________________
> Dri-devel mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/dri-devel

--                             /\
         Jens Owen            /  \/\ _    
  [EMAIL PROTECTED]  /    \ \ \   Steamboat Springs, Colorado

_______________________________________________________________

Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm

_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel

Reply via email to