On Mon, 2004-09-20 at 23:44, Ian Romanick wrote: > Amir Bukhari wrote: > > > I will start on it from now on, but I have a small question. is indirect > > rendering use 3D accelarator for 3D operation or it is all software? > > > > for example glxgear use GLX, is that mean it use indirect rendering? > > > > APP ---> GLX (libglx) ----> DRI ---> Hardware. (indirect rendering) > > APP ---> DRI (libGL) ----> Hardware. (direct rendering) > > > > is this schema correct? > > Not 100% > > Direct rendering: > > APP -> libGL -> DRI driver (*_dri.so) -> DRM (kernel module) -> hardware > > Indirect rendering: > > APP -> libGL -> GLX protocol to X-server -> ? > > In the current implementation "?" is software Mesa. However, in the > future it will likely be " -> DRI driver -> DRM -> hardware". "Direct" > just means that access to the framebuffer and graphics hardware happens > in the address space of the application (i.e., the application directly > accesses the graphics hardware).
that mean all applications, which linked with libglx, will be only software rendered at this moment, when DRI is used. I don't want to talk when using GLX module from nvidia. Nvidia is outside our scope. ------------------------------------------------------- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php -- _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
