Bug 3987 - Workaround for 512 Meg video cards
Summary: Workaround for 512 Meg video cards
Status: RESOLVED FIXED
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/nVidia (open) (show other bugs)
Version: git
Hardware: x86 (IA32) All
: high normal
Assignee: Alan Coopersmith
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-08-05 13:47 UTC by Alan Coopersmith
Modified: 2005-08-04 03:53 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments

Description Alan Coopersmith 2005-08-05 13:47:23 UTC 
Mark Vojkovich has made the following fix to the open source nv driver which 
should be imported into the Xorg copy:

CVSROOT:	/home/x-cvs
Module name:	xc
Changes by:	mvojkovi@public.xfree86.org.	05/08/03 10:39:31

Log message:
    Workaround for 512 Meg video cards (can only map 256 Meg of it).

Modified files:
      xc/programs/Xserver/hw/xfree86/drivers/nv/:
        nv_setup.c 
  
  Revision      Changes    Path
  1.47          +4 -1      xc/programs/Xserver/hw/xfree86/drivers/nv/nv_setup.c
Comment 1 Alan Coopersmith 2005-08-05 13:49:18 UTC 
Created attachment 3264 [details]
xorg configuration file
Comment 2 Alan Coopersmith 2005-08-05 13:53:53 UTC 
Fix committed to CVS head for Xorg 6.9/7.0 RC1:

CVSROOT:	/cvs/xorg
Module name:	xc
Changes by:	alanc@gabe.freedesktop.org	05/08/04 20:52:28

Log message:
  2005-08-04  Alan Coopersmith  <alan.coopersmith@sun.com>
  
  	* programs/Xserver/hw/xfree86/drivers/nv/nv_setup.c:
  	Bug #3987 <https://bugs.freedesktop.org/show_bug.cgi?id=3987>
  	Patch #3264 <https://bugs.freedesktop.org/attachment.cgi?id=3264>
  	Workaround for 512 Meg video cards (can only map 256 Meg of it).
  	(Mark Vojkovich)

Modified files:
      ./:
        ChangeLog 
      xc/programs/Xserver/hw/xfree86/drivers/nv/:
        nv_setup.c 
  
  Revision      Changes    Path
  1.1178        +8 -0      xc/ChangeLog
  1.8           +4 -1      xc/programs/Xserver/hw/xfree86/drivers/nv/nv_setup.c

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.