On Mon, 2003-10-06 at 17:38, Vladimir Dergachev wrote: > On Mon, 6 Oct 2003, Michel [ISO-8859-1] Dnzer wrote: > > > A proposal for this has been developed in > > http://bugs.xfree86.org/show_bug.cgi?id=314 (first idea in comment #20, > > refinement inspired by > > http://www.mail-archive.com/[EMAIL PROTECTED]/msg11659.html in comment #27) > > Very interesting, I certainly would be delighted if this was implemented. > > All GATOS drivers need is that framebuffer was moved outside of system > RAM. Nothing more.
Good. > As Keith rightly points out, when one uses ioctl it would be hard to make > 3d driver to understand that the aperture moved. > > I would suggest adding more ioctls: > > 1. Lock the drm driver against future connections from 3d driver(s). > > 2. Return the number of current connections. > > 3. Move the aperture - should only succeed when nothing else is connected. > > Also, when aperture is moved DRM driver can simply refuse connection to > older 3d drivers. Does the aperture ever (have to) move during the X server life though? Our idea would be an ioctl to set the aperture position on startup and (possibly another one) for 3D clients to let the DRM know what they think the aperture position is. Then the DRM could fix up client commands as necessary. This would work with any 3D driver (except probably old incompatible ones from GATOS :). -- Earthling Michel Dänzer \ Debian (powerpc), XFree86 and DRI developer Software libre enthusiast \ http://svcs.affero.net/rm.php?r=daenzer ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
