Skip to content
  1. Apr 26, 2007
  2. Apr 12, 2007
  3. Apr 10, 2007
  4. Apr 09, 2007
  5. Feb 27, 2007
    • Ryusuke Konishi's avatar
      [AGPGART] fix compile errors · e047d1cf
      Ryusuke Konishi authored
      
      
      This fixes the following compile failures of agpgart drivers.
      These errors were inserted by the recent AGPGART constification patch.
      
      drivers/char/agp/uninorth-agp.c:492: error: expected '{' before 'const'
      drivers/char/agp/uninorth-agp.c:517: error: expected '{' before 'const'
      drivers/char/agp/uninorth-agp.c: In function 'agp_uninorth_probe':
      drivers/char/agp/uninorth-agp.c:634: error: 'u3_agp_driver' undeclared (first use in this function)
      drivers/char/agp/uninorth-agp.c:634: error: (Each undeclared identifier is reported only once
      drivers/char/agp/uninorth-agp.c:634: error: for each function it appears in.)
      drivers/char/agp/uninorth-agp.c:636: error: 'uninorth_agp_driver' undeclared (first use in this function)
      
      Signed-off-by: default avatarRyusuke Konishi <ryusuke@osrg.net>
      Signed-off-by: default avatarDave Jones <davej@redhat.com>
      e047d1cf
    • Kyle McMartin's avatar
      [PARISC] parisc-agp: Fix thinko const-ifying · fb55a0de
      Kyle McMartin authored
      
      
      Can't really blame davej for mucking this up... static-ify
      it while we're at it, which would have prevented this...
      
      Signed-off-by: default avatarKyle McMartin <kyle@parisc-linux.org>
      fb55a0de
  6. Feb 22, 2007
  7. Feb 20, 2007
  8. Feb 11, 2007
  9. Feb 06, 2007
  10. Feb 05, 2007
  11. Feb 04, 2007
  12. Feb 03, 2007
    • Thomas Hellstrom's avatar
      [AGPGART] Allow drm-populated agp memory types · a030ce44
      Thomas Hellstrom authored
      
      
      This patch allows drm to populate an agpgart structure with pages of its own.
      It's needed for the new drm memory manager which dynamically flips pages in and out of AGP.
      
      The patch modifies the generic functions as well as the intel agp driver. The intel drm driver is
      currently the only one supporting the new memory manager.
      
      Other agp drivers may need some minor fixing up once they have a corresponding memory manager enabled drm driver.
      
      AGP memory types >= AGP_USER_TYPES are not populated by the agpgart driver, but the drm is expected
      to do that, as well as taking care of cache- and tlb flushing when needed.
      
      It's not possible to request these types from user space using agpgart ioctls.
      
      The Intel driver also gets a new memory type for pages that can be bound cached to the intel GTT.
      
      Signed-off-by: default avatarThomas Hellstrom <thomas@tungstengraphics.com>
      Signed-off-by: default avatarDave Jones <davej@redhat.com>
      a030ce44
    • Zwane Mwaikambo's avatar
      [AGPGART] compat ioctl · 0316fe83
      Zwane Mwaikambo authored
      The following video card requires the agpgart driver ioctl
      interface in order to detect video memory.
      
      00:02.0 VGA compatible controller: Intel Corporation Mobile
      945GM/GMS/940GML Express Integrated Graphics Controller (rev 03)
      
      Tested on a Thinkpad Z61t, Xorg.0.log from a 32bit debian Xorg is at;
      
      http://montezuma.homeunix.net/Xorg.0.log
      
      
      
      Signed-off-by: default avatarZwane Mwaikambo <zwane@infradead.org>
      Signed-off-by: default avatarDave Jones <davej@redhat.com>
      0316fe83
  13. Jan 28, 2007
  14. Jan 17, 2007
  15. Jan 03, 2007
  16. Dec 29, 2006
  17. Dec 23, 2006
    • Eric Anholt's avatar
      [AGPGART] fix detection of aperture size versus GTT size on G965 · c41e0deb
      Eric Anholt authored
      
      
      On the G965, the GTT size may be larger than is required to cover the
      aperture.  (In fact, on all hardware we've seen, the GTT is 512KB to the
      aperture's 256MB).  A previous commit forced the aperture size to 512MB on
      G965 to match GTT, which would likely result in hangs at best if users
      tried to rely on agpgart's aperture size information.  Instead, we use the
      resource length for the aperture size and the system's reported GTT size
      when available for the GTT size.
      
      Because the MSAC registers which had been read for aperture size detection
      on i9xx chips just cause a change in the resource size, we can use generic
      code for aperture detection on all i9xx.
      
      Signed-off-by: default avatarEric Anholt <eric@anholt.net>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarDave Jones <davej@redhat.com>
      c41e0deb
    • Thomas Hellstrom's avatar
      [AGPGART] Remove unnecessary flushes when inserting and removing pages. · 5aa80c72
      Thomas Hellstrom authored
      
      
      This patch is to speed up flipping of pages in and out of the AGP aperture as
      needed by the new drm memory manager.
      
      A number of global cache flushes are removed as well as some PCI posting flushes.
      The following guidelines have been used:
      
      1) Memory that is only mapped uncached and that has been subject to a global
      cache flush after the mapping was changed to uncached does not need any more
      cache flushes. Neither before binding to the aperture nor after unbinding.
      
      2) Only do one PCI posting flush after a sequence of writes modifying page
      entries in the GATT.
      
      Signed-off-by: default avatarThomas Hellstrom <thomas@tungstengraphics.com>
      Signed-off-by: default avatarDave Jones <davej@redhat.com>
      5aa80c72
  18. Dec 19, 2006
  19. Dec 12, 2006
  20. Dec 08, 2006
  21. Dec 07, 2006
  22. Nov 22, 2006
    • Linus Torvalds's avatar
      [AGP] Allocate AGP pages with GFP_DMA32 by default · 66c669ba
      Linus Torvalds authored
      
      
      Not all graphic page remappers support physical addresses over the 4GB
      mark for remapping, so while some do (the AMD64 GART always did, and I
      just fixed the i965 to do so properly), we're safest off just forcing
      GFP_DMA32 allocations to make sure graphics pages get allocated in the
      low 32-bit address space by default.
      
      AGP sub-drivers that really care, and can do better, could just choose
      to implement their own allocator (or we could add another "64-bit safe"
      default allocator for their use), but quite frankly, you're not likely
      to care in practice.
      
      So for now, this trivial change means that we won't be allocating pages
      that we can't map correctly by mistake on x86-64.
      
      [ On traditional 32-bit x86, this could never happen, because GFP_KERNEL
        would never allocate any highmem memory anyway ]
      
      Acked-by: default avatarAndi Kleen <ak@suse.de>
      Acked-by: default avatarDave Jones <davej@redhat.com>
      Cc: Eric Anholt <eric@anholt.net>
      Cc: Keith Packard <keithp@keithp.com>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      66c669ba
    • Linus Torvalds's avatar
      [AGP] Fix intel 965 AGP memory mapping function · 7d915a38
      Linus Torvalds authored
      
      
      This introduces a i965-specific "mask_memory()" function that knows
      about the extended physical addresses that the i965 supports.  This
      allows us to correctly map in physical memory in the >4GB range into the
      GTT.
      
      Also simplify/clean-up the i965 case for the aperture sizing by just
      returning the fixed 512kB size from "fetch_size()".  We don't really
      care that not all of the aperture may be visible - the only thing that
      cares about the aperture size is the Intel "stolen memory" calculation,
      which depends on the fixed size.
      
      Cc: Keith Packard <keithp@keithp.com>
      Cc: Eric Anholt <eric@anholt.net>
      Cc: Dave Jones <davej@redhat.com>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      7d915a38
  23. Nov 03, 2006
    • Dave Jones's avatar
      [AGPGART] Fix up misprogrammed bridges with incorrect AGPv2 rates. · 28af24bb
      Dave Jones authored
      Some dumb bridges are programmed to disobey the AGP2 spec.
      This is likely a BIOS misprogramming rather than poweron default, or
      it would be a lot more common.
      
      AGPv2 spec 6.1.9 states:
      
       "The RATE field indicates the data transfer rates supported by this
        device. A.G.P. devices must report all that apply."
      
      Fix them up as best we can.
      
      This will prevent errors like..
      
      agpgart: Found an AGP 3.5 compliant device at 0000:00:00.0.
      agpgart: req mode 1f000201 bridge_agpstat 1f000a14 vga_agpstat 2f000217.
      agpgart: Device is in legacy mode, falling back to 2.x
      agpgart: Putting AGP V2 device at 0000:00:00.0 into 0x mode
      agpgart: Putting AGP V2 device at 0000:01:00.0 into 0x mode
      agpgart: Putting AGP V2 device at 0000:01:00.1 into 0x mode
      
      https://bugs.freedesktop.org/show_bug.cgi?id=8816
      
      
      
      Signed-off-by: default avatarDave Jones <davej@redhat.com>
      28af24bb
  24. Oct 15, 2006
  25. Oct 04, 2006
  26. Sep 28, 2006
  27. Sep 27, 2006
  28. Sep 11, 2006
  29. Sep 06, 2006
  30. Sep 05, 2006
Loading