Re: Adding DMX to XFree86
On Tue, 22 Jun 2004, Kevin E Martin wrote: We would like to include DMX in the next XFree86 release. 7. Add DMX and GLX Proxy support to Xinerama 9. Add protocol and structures to support GLX Proxy (from SGI) Does GLX Proxy allow hardware accelerated GLX ? Does it allow hardware accelerated GLX from remote machines independent of DMX ? If so GLX Proxy seems desireable on its own account. (I have nothing against DMX, just remote GLX is something I've wished for for nearly a decade). -- Dr. Andrew C. Aitchison Computer Officer, DPMMS, Cambridge [EMAIL PROTECTED] http://www.dpmms.cam.ac.uk/~werdna ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Adding DMX to XFree86
On Wed, Jun 23, 2004 at 11:20:09AM +0100, Dr Andrew C Aitchison wrote: On Tue, 22 Jun 2004, Kevin E Martin wrote: We would like to include DMX in the next XFree86 release. 7. Add DMX and GLX Proxy support to Xinerama 9. Add protocol and structures to support GLX Proxy (from SGI) Does GLX Proxy allow hardware accelerated GLX ? Does it allow hardware accelerated GLX from remote machines independent of DMX ? If so GLX Proxy seems desireable on its own account. GLXProxy is a DMX-specific GLX implementation that acts as a proxy server for GLX protocol. SGI wrote this code and donated it to the DMX project. It takes advantage of any hardware accelerated indirect rendering that is already present on the back-end server to which it attaches, but it won't create hardware accelerated indirect rendering on a system that doesn't already have it. I think many of us would very much like to have hardware accelerated indirect rendering, and from time to time there has been talk of adding it to the DRI project. It's actually been on the to do list for the DRI project from the original design days, but it's a large project and there was little interest in funding it back when I was with PI and VA. I'm still hopeful that it will eventually happen. ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Adding DMX to XFree86
Kevin E Martin wrote: I think many of us would very much like to have hardware accelerated indirect rendering, and from time to time there has been talk of adding it to the DRI project. It's actually been on the to do list for the DRI project from the original design days, but it's a large project and there was little interest in funding it back when I was with PI and VA. I'm still hopeful that it will eventually happen. The current thinking is to, essentially, 'rm -rf xc/programs/Xserver/GL' and re-write it so that libglx.a loads a device-dependent *_dri.so, like the client-side libGL does. The advantage being that only one driver binary will be needed per-device. The support and maintainence advantages should be obvious. Work has been started on an Xlib based DRI driver (something of a contradiction in terms, I know) by Adam Jackson. I've started writing Python scripts to automatically generate GLX protocol handling code (for both client-side and server-side). We're getting closer to starting the real work, but I need to clear a few things off my plate first. My goal is to start a branch in the DRI tree in the next few (3 to 4) months to get this work going. ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Adding DMX to XFree86
On Wed, Jun 23, 2004 at 11:30:38AM -0700, Ian Romanick wrote: Kevin E Martin wrote: I think many of us would very much like to have hardware accelerated indirect rendering, and from time to time there has been talk of adding it to the DRI project. It's actually been on the to do list for the DRI project from the original design days, but it's a large project and there was little interest in funding it back when I was with PI and VA. I'm still hopeful that it will eventually happen. The current thinking is to, essentially, 'rm -rf xc/programs/Xserver/GL' and re-write it so that libglx.a loads a device-dependent *_dri.so, like the client-side libGL does. The advantage being that only one driver binary will be needed per-device. The support and maintainence advantages should be obvious. Exactly. That was the basic approach we were planning to take at PI. FYI, there are several papers (from either HP or SGI, IIRC) that give an overview of various the approaches. I can try to dig up those refs, if it would be helpful. Work has been started on an Xlib based DRI driver (something of a contradiction in terms, I know) by Adam Jackson. I've started writing Python scripts to automatically generate GLX protocol handling code (for both client-side and server-side). We're getting closer to starting the real work, but I need to clear a few things off my plate first. My goal is to start a branch in the DRI tree in the next few (3 to 4) months to get this work going. That's excellent! I look forward to seeing this effort get going. Kevin ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Adding DMX to XFree86
We would like to include DMX in the next XFree86 release. I have created a patch against the head of the current CVS tree with the changes to existing files as well as a tarball with the newly added files. You can view these in XFree86 Bugzilla #1414. Here is the link to the patch for the existing files: http://bugs.xfree86.org/attachment.cgi?id=1239action=view and here is a summary of the changes you will find in this patch: 1. Imakefile and config file changes to build DMX 2. SGI build and config file changes (from SGI) 3. Add DMX support to miinitext.c 4. Allow AbortServer to be called from DMX 5. Add glyph private and picture private support to Render extension 6. Add DMX support to xdpyinfo 7. Add DMX and GLX Proxy support to Xinerama 8. Add support for changing the default VENDOR_RELEASE and VENDOR_STRING 9. Add protocol and structures to support GLX Proxy (from SGI) If there are no objections to adding DMX, I will check in the changes to the CVS tree next week. Note: The patch above does not include the MAXSCREENS changes that we previously submitted since those changes caused a module ABI change. When/if the MAXSCREENS changes are accepted, the code in the patch above will automatically take advantage of it. For those not familiar with the DMX project, it adds support for distributing the multihead capabilities of the X Window System across multiple displays attached to different machines. For example, a simple application would be to provide multihead support using two desktop machines, each of which has a single display device attached to it. This can be scaled up to a large display wall created from multiple projected displays (up to MAXSCREENS displays). Additional information on the DMX project can be found on the project web page: http://dmx.sourceforge.net/ Kevin E. Martin and Rik Faith ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
