We should import these changes to our copy of 'nv' (also includes updates to names for existing PCI ids but does not add new ids): CVSROOT: /home/x-cvs Module name: xc Changes by: mvojkovi@public.xfree86.org. 05/09/13 19:28:03 Log message: Fix a potential problem with pixmap cache corruption on GeForce 6xxx and 7xxx parts. Modified files: xc/programs/Xserver/hw/xfree86/drivers/nv/: nv_driver.c nv_hw.c nv_setup.c Revision Changes Path 1.137 +19 -7 xc/programs/Xserver/hw/xfree86/drivers/nv/nv_driver.c 1.16 +39 -12 xc/programs/Xserver/hw/xfree86/drivers/nv/nv_hw.c 1.48 +1 -2 xc/programs/Xserver/hw/xfree86/drivers/nv/nv_setup.c
Created attachment 3304 [details] [review] Diffs from XFree86 CVS
Created attachment 3305 [details] [review] Patch against Xorg CVS head
Correction: It does add two new PCI ids for GeForce 6800 XT cards: + { 0x10DE0048, "GeForce 6800 XT" }, + { 0x10DE00C3, "GeForce 6800 XT" },
Committed to CVS head - should be in Xorg 6.9 RC1: CVSROOT: /cvs/xorg Module name: xc Changes by: alanc@gabe.freedesktop.org 05/09/16 18:37:18 Log message: 2005-09-16 Alan Coopersmith <alan.coopersmith@sun.com> * programs/Xserver/hw/xfree86/drivers/nv/nv_driver.c: Bugzilla #4480 <https://bugs.freedesktop.org/show_bug.cgi?id=4480> Patch #3305 <https://bugs.freedesktop.org/attachment.cgi?id=3305> 13-Sep-2005 nv driver update from Mark Vojkovich: - Adds PCI ids for GeForce 6800 XT cards - Adds names for existing PCI ids for some GeForce 6xxx & 7xxx cards - Fix a potential problem with pixmap cache corruption on GeForce 6xxx and 7xxx parts. (Mark Vojkovich, NVIDIA) Modified files: ./: ChangeLog xc/programs/Xserver/hw/xfree86/drivers/nv/: nv_driver.c nv_hw.c nv_setup.c Revision Changes Path 1.1323 +11 -0 xc/ChangeLog 1.17 +19 -7 xc/programs/Xserver/hw/xfree86/drivers/nv/nv_driver.c 1.8 +39 -12 xc/programs/Xserver/hw/xfree86/drivers/nv/nv_hw.c 1.9 +1 -2 xc/programs/Xserver/hw/xfree86/drivers/nv/nv_setup.c
*** Bug 4523 has been marked as a duplicate of this bug. ***
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.