The server-side DRI support defined frameBufferPhysicalAddress as a CARD32.  
This is wrong for 64-bit systems where the framebuffer could be mapped above 
4G.  The problem is that frameBufferPhysicalAddress is smack in the middle of 
the DRIInfoRec, and on LP64 systems changing it to a pointer will change the 
location of everything else in that struct.

The proposed fix is something like the patch in 

https://bugs.freedesktop.org/show_bug.cgi?id=3066

but with the additional step of bumping the major version number of libdri.

Are there any other known LP64 issues in DRI we should be taking care of at 
the same time?  We're allowed to break ABIs for this if it makes a cleaner 
solution.

- ajax

Attachment: pgpOvNKvna7yN.pgp
Description: PGP signature

Reply via email to