Smitty wrote:
>
> How's it going Jens?
>
> Attached find my "work in progress" of dri_control_flow.
>
> For the X Server "block" in the middle I have used what you told
> me with dri_data_flow and just stuck that in there.
>
> Now the first thing that I can see that isn't right is that there
> is a lonely DRMLib talking to SAREA & Kernel. This is I believe
> is the resource management path coming from the 3D Direct Rendering
> Program (3DDRP). ie there should be a line / path coming from X
> Transport from the 3DDRP into Protocol Decode where it splits with
> one path going to DIX, then XXA & then DDX and the other part /
> path (Resource Management) going to DRI Module (not sure if this
> should still be here) & then to DRMLib.
>
> Input on this please.
Pretty close. You are correct that the resource management path spun
out of protocol decode goes to the DRI module. From there, it can go to
one of two places depending on what needs to be done. First route is to
the DDX driver. The second route is directly to DRMLib. The DDX driver
also call DRMLib. You end up with this inside the X Server:
+------+
| DRI |
+------+
| |
| v
| +-----
| | DDX
| +-----
| |
v v
+--------+
| DRMLib |
+--------+
> Any other incorrect / inaccurate going's on I should know about?
I don't think you need to address this in your diagrams, but it's
interesting to realize that Mesa and the DRI work closely together, but
it's also possible to decouple them. Mesa can be used as a standalone
renderer without X and the DRI--and conversely it's possible to create a
direct rendering 3D driver based on a non-Mesa source base.
> Once this is fixed I will ask about what's happenning in the 3DDRP,
> although I have already speculated about this in my previous email.
>
> btw any little bit that you want added in (eg labels), more detail
> (eg subdivided boxes) or any explanation (eg text) that you feel
> is important or useful for the understanding of the diagram and
> DRI please provide it as I will gladly add it to the diagram and
> / or the text exlpanation of the paths shown.
I've honestly looked at this architecture and representing diagrams so
much over the last 4 years that it's hard for me to abstract the
basics. That's where your fresh perspective and good questions has been
very helpful.
Regards,
Jens
-- /\
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?source=osdntextlink
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
