Alan Hourihane writes:
> There's another issue here.
>
> And that's drmAddress in the 2D DDX drivers.
>
> On 32bit arches it's 32bits, on 64bit arches it's 64bit. And because
> drmAddress is passed in the *DRIRec things break.
>
> The client-side 3D driver gets the *DRIRec and as it's a different size
> things are a mess when using a 32bit client on a 64bit arch.
>
> It looks like the radeon and r128 don't suffer from this but most of
> the other drivers do.
Yep, the mga driver doesn't suffer from this either.
I don't quite see what the purpose of drmAddress is anyway.
It looks like it could just as well be replaced by a drm_handle_t
as it holds the handle to a map optained by addMap() - at least
from what I can tell right now.
Egbert.
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
--
_______________________________________________
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
