<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.16.0">
</HEAD>
<BODY>
Hi,<BR>
<BR>
I was analyzing the Mesa code when i need to build Mesa for DRI using make linux-dri.I find that there is some interface files e.g. dri_interface.h using which client program & libGL.so(Mesa-GL) links to the actual 3D driver(vendor provided <hw>_dri.so).<BR>
<BR>
But as there is no standard API defined for DRI ( e.g. creating context/drawable etc), so my question is whoever (vendor) implements their OpenGL implementation for DRI/DRM will they be Mesa compliant?Otherwise, if my program already links to Mesa, then can i use vendor's provided dri.so OR, i have to replace Mesa libGL.so with the vendor provided <hw>_dri.so<BR>
<BR>
Regs,<BR>
Rahaman<BR>
<TABLE CELLSPACING="0" CELLPADDING="0" WIDTH="100%">
<TR>
<TD>
<BR>
</TD>
</TR>
</TABLE>
<BR>
-----Original Message-----<BR>
<B>From</B>: Daniel Stone <<A HREF="mailto:Daniel%20Stone%20%3cdaniel@fooishbar.org%3e">daniel@fooishbar.org</A>><BR>
<B>To</B>: Rahaman <<A HREF="mailto:Rahaman%20%3cmustaf.here@gmail.com%3e">mustaf.here@gmail.com</A>>i,<BR>
<B>Cc</B>: Dave Airlie <<A HREF="mailto:Dave%20Airlie%20%3cairlied@gmail.com%3e">airlied@gmail.com</A>>, <A HREF="mailto:xorg@lists.freedesktop.org">xorg@lists.freedesktop.org</A><BR>
<B>Subject</B>: Re: Reg: AIGLX architecture & it's difference from DRI<BR>
<B>Date</B>: Mon, 1 Sep 2008 14:19:36 +0300<BR>
<BR>
<PRE>
On Mon, Sep 01, 2008 at 02:10:40PM +0530, Rahaman wrote:
> 1>If some one( a vendor) gives me only the OpenGL driver(no DRI/DRM
> functionality) implementation, can i use that and build my DRI/DRM
> modules i.e. Can i write my own dri.so & drm.so and still use the vendor
> provided OpenGL? Excuse me as some of my questions can be abstarct or
> some cases invalid,too as i am new to this area :-(
If you have the source, then yes, you can write a DRI/DRM driver
yourself, given enough time. If you don't have the source, then no.
> 3>Can i get a comparison like pros & cons for both the architecture in
> different context/use cases?
Direct: fast. Indirect: slow.
Cheers,
Daniel
</PRE>
</BODY>
</HTML>