On Tuesday 19 April 2005 12:17, Adam Jackson wrote: > 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.
I've attached a patch to this bug that changes fBPA to a pointer, raises the libdri version number, and bumps the required DRI version in the DDX drivers. This will also require updating the DRI drivers to check for libdri version 5.0. I really don't want to apply this yet because it will break every DRI driver provided from the xorg build (as the Mesa copy in extras/ will look for libdri version 4.x). What's the timeframe for getting a Mesa release with DRI driver source included? Several distros are itching for this. For now I'd even be happy with Mesa snapshots. I can easily modify the script that generates the Xorg tarballs to do Mesa snaps too. - ajax
pgpkkIntXRfJ4.pgp
Description: PGP signature
