Re: DRM map design

2005-07-01 Thread Jon Smirl
I've attached my current diffs to DRM. I am coverting DRM so that the server does not have to run as root. The attached code allows this. Most of the changes are in AddMap. 1) sarea is prebuilt 2) agp maps are allowed from non-root master but checked to make sure they are within allocated agp spa

Re: DRM map design

2005-07-01 Thread Paul Mackerras
Jon Smirl writes: > Don't the maps always contain the physical address of the object? That > would provide a unique handle. No, for _DRM_SHM and _DRM_SCATTER_GATHER maps the offset is a kernel virtual address (at least at present). It's only by luck that we don't see collisions. Also, using a p

Re: [r300] r300 driver locks up with Xglx

2005-07-01 Thread Lorenzo Colitti
Nicolai Haehnle wrote: According to lspci, it's an "ATI Technologies Inc RV350 [Mobility Radeon 9600 M10]" That chip is actually known to work fine. Have you tried to run ordinary OpenGL applications within the normal X.Org server (e.g. Glean, TuxRacer, Cube, ...)? Are you seeing lockups ther

Re: [r300] r300 driver locks up with Xglx

2005-07-01 Thread Jon Smirl
On 7/1/05, Nicolai Haehnle <[EMAIL PROTECTED]> wrote: > If it's a bug on our (i.e. the driver's) side, we should fix it, whether or > not Xglx itself is in a usable state. It's likely that Xglx hits code paths > that aren't used by most programs. Xglx is working pretty well. I'd suggest using it a

Re: [R300] drm driver: merge upstream, security, etc

2005-07-01 Thread Michel Dänzer
On Fri, 2005-07-01 at 03:24 +0300, Aapo Tahkola wrote: > On Sun, 26 Jun 2005 23:48:11 -0400 > Michel Dänzer <[EMAIL PROTECTED]> wrote: > > > On Sun, 2005-06-26 at 18:05 -0700, Eric Anholt wrote: > > > On Mon, 2005-06-27 at 01:19 +0100, Alan Cox wrote: > > > > > > > Disagree also about axing the c

Re: [r300] r300 driver locks up with Xglx

2005-07-01 Thread Nicolai Haehnle
On Friday 01 July 2005 16:31, Lorenzo Colitti wrote: > Peter Zubaj wrote: > > Some of r300 driver lockups are card dependant (and for now I have > > only these card dependand lockups). Cards which will lock (soon or > > later) are 9500 Pro (maybe 9500 too), 9700, 9800. What card do you have ? >

Re: DRM map design

2005-07-01 Thread Jon Smirl
Don't the maps always contain the physical address of the object? That would provide a unique handle. Where does the handle get used in user space? After I GetMap() to find the map I need, I pass the offset back into drmMap() not the handle. Offset is the physical address in most cases. -- Jon S

Re: [r300] r300 driver locks up with Xglx

2005-07-01 Thread Lorenzo Colitti
Peter Zubaj wrote: Some of r300 driver lockups are card dependant (and for now I have only these card dependand lockups). Cards which will lock (soon or later) are 9500 Pro (maybe 9500 too), 9700, 9800. What card do you have ? According to lspci, it's an "ATI Technologies Inc RV350 [Mobility R

Re: ioctl32 on amd64

2005-07-01 Thread Egbert Eich
Ian Romanick writes: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Egbert Eich wrote: > > > @@ -612,8 +612,7 @@ > > _tnl_allow_pixel_fog( ctx, GL_FALSE ); > > _tnl_allow_vertex_fog( ctx, GL_TRUE ); > > > > - mmesa->primary_offset = mmesa->mgaScreen->primary.handle;

Re: DRM map design

2005-07-01 Thread Egbert Eich
Paul Mackerras writes: > Keith Whitwell writes: > > > In general I'd prefer that the values passed to clients (and back again) > > to be abstract tokens rather than actual addresses or offsets into some > > unspecified address space. > > > > Which should mean that 32 bits is more than am

Re: ioctl32 on amd64

2005-07-01 Thread Egbert Eich
Alan Hourihane writes: > It'd be nice to do something. Using RedHat EL4 the DRM CVS fails to > build because the .compat_ioctl doesn't exist in 2.6.9. > > Or, at the very least, we'll need to check if compat_ioctl exists before > allowing compilation. Well, that may be the way to go. The cod

Re: DRM map design

2005-07-01 Thread Keith Whitwell
Paul Mackerras wrote: Keith Whitwell writes: In general I'd prefer that the values passed to clients (and back again) to be abstract tokens rather than actual addresses or offsets into some unspecified address space. Which should mean that 32 bits is more than ample to contain them... Th

Re: DRM map design

2005-07-01 Thread Paul Mackerras
Keith Whitwell writes: > In general I'd prefer that the values passed to clients (and back again) > to be abstract tokens rather than actual addresses or offsets into some > unspecified address space. > > Which should mean that 32 bits is more than ample to contain them... The problem that we

Re: GLX 1.3 support?

2005-07-01 Thread Roland Scheidegger
Aric Cyr wrote: I had originally posted this on the xorg-devel mailing list, but didn't get much response, so thought I'd try my luck here... I was just wondering if there was any progress or planned work to update the server's GLX implementation to 1.3.? It looks like about half of the work is