1. 11 7月, 2007 3 次提交
  2. 08 5月, 2007 1 次提交
    • D
      drm/radeon: upgrade to 1.27 - make PCI GART more flexible · f2b04cd2
      Dave Airlie 提交于
      radeon: make PCI GART aperture size variable, but making table size variable
          This is precursor to getting a TTM backend for this stuff, and also
          allows the PCI table to be allocated at fb 0
      radeon: add support for reverse engineered xpress200m
      
          The IGPGART setup code was traced using mmio-trace on fglrx by myself
          and Phillip Ezolt <phillipezolt@gmail.com> on dri-devel.
      
          This code doesn't let the 3D driver work properly as the card has no
          vertex shader support.
      
          Thanks to Matthew Garrett + Ubuntu for providing me some hardware to do this
          work on.
      Signed-off-by: NDave Airlie <airlied@linux.ie>
      f2b04cd2
  3. 11 3月, 2007 1 次提交
  4. 22 9月, 2006 4 次提交
  5. 24 6月, 2006 1 次提交
  6. 25 3月, 2006 1 次提交
  7. 19 3月, 2006 1 次提交
  8. 25 1月, 2006 1 次提交
  9. 02 1月, 2006 2 次提交
  10. 30 12月, 2005 1 次提交
    • L
      Revert radeon AGP aperture offset changes · 392c14be
      Linus Torvalds 提交于
      This reverts the series of commits
      
      	67dbb4ea
      	281ab031
      	47807ce3
      
      that changed the GART VM start offset.  It fixed some machines, but
      seems to continually interact badly with some X versions.
      
      Quoth Ben Herrenschmidt:
      
        "So I think at this point, the best is that we keep the old bogus code
         that at least is consistent with the bug in the server. I'm working on a
         big patch to X that reworks the memory map stuff completely and fixes
         those issues on the server side, I'll do a DRM patch matching this X fix
         as well so that the memory map is only ever set in one place and with
         what I hope is a correct algorithm..."
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      392c14be
  11. 28 12月, 2005 1 次提交
    • B
      [PATCH] Fix more radeon GART start calculation cases · 67dbb4ea
      Benjamin Herrenschmidt 提交于
      As reported by Jules Villard <jvillard@ens-lyon.fr> and some others, the
      recent GART aperture start reconfiguration causes problems on some
      setups.
      
      What I _think_ might be happening is that the X server is also trying to
      muck around with the card memory map and is forcing it back into a wrong
      setting that also happens to no longer match what the DRM wants to do
      and blows up.  There are bugs all over the place in that code (and still
      some bugs in the DRM as well anyway).
      
      This patch attempts to avoid that by using the largest of the 2 values,
      which I think will cause it to behave as it used to for you and will
      still fix the problem with machines that have an aperture size smaller
      than the video memory.
      Acked-by: NJules Villard <jvillard@ens-lyon.fr>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      67dbb4ea
  12. 19 12月, 2005 1 次提交
  13. 16 12月, 2005 1 次提交
  14. 13 12月, 2005 1 次提交
  15. 10 11月, 2005 1 次提交
    • D
      drm: rename driver hooks more understandably · 22eae947
      Dave Airlie 提交于
      Rename the driver hooks in the DRM to something a little more understandable:
      preinit         ->      load
      postinit        ->      (removed)
      presetup        ->      firstopen
      postsetup       ->      (removed)
      open_helper     ->      open
      prerelease      ->      preclose
      free_filp_priv  ->      postclose
      pretakedown     ->      lastclose
      postcleanup     ->      unload
      release         ->      reclaim_buffers_locked
      version         ->      (removed)
      
      postinit and version were replaced with generic code in the Linux DRM (drivers
      now set their version numbers and description in the driver structure, like on
      BSD).  postsetup wasn't used at all.  Fixes the savage hooks for
      initializing and tearing down mappings at the right times.  Testing involved at
      least starting X, running glxgears, killing glxgears, exiting X, and repeating.
      
      Tested on:      FreeBSD (g200, g400, r200, r128)
                      Linux (r200, savage4)
      
      From: Eric Anholt <anholt@freebsd.org>
      Signed-off-by: NDave Airlie <airlied@linux.ie>
      22eae947
  16. 27 10月, 2005 1 次提交
  17. 30 9月, 2005 1 次提交
  18. 25 9月, 2005 1 次提交
    • D
      drm: lindent the drm directory. · b5e89ed5
      Dave Airlie 提交于
      I've been threatening this for a while, so no point hanging around.
      This lindents the DRM code which was always really bad in tabbing department.
      I've also fixed some misnamed files in comments and removed some trailing
      whitespace.
      Signed-off-by: NDave Airlie <airlied@linux.ie>
      b5e89ed5
  19. 11 9月, 2005 1 次提交
  20. 16 8月, 2005 1 次提交
  21. 05 8月, 2005 1 次提交
    • D
      drm: updated DRM map patch for 32/64 bit systems · d1f2b55a
      Dave Airlie 提交于
      I basically combined Paul's patches with additions that I had made
      for PCI scatter gather.
      I also tried more carefully to avoid problems with the same token
      assigned multiple times while trying to use the base address in the
      token if possible to gain as much backward compatibility as possible
      for broken DRI clients.
      
      From: Paul Mackerras <paulus@samba.org> and Egbert Eich <eich@suse.de>
      Signed-off-by: NDave Airlie <airlied@linux.ie>
      d1f2b55a
  22. 10 7月, 2005 1 次提交
    • D
      drm: cleanup buffer/map code · 836cf046
      Dave Airlie 提交于
      This is a patch from DRM CVS that cleans up some code that was in CVS
      that I never moved to the kernel, this patch produces the result of the
      cleanups and puts it into the kernel drm.
      
      From: Eric Anholt <anholt@freebsd.org>, Jon Smirl, Dave Airlie
      Signed-off-by: NDave Airlie <airlied@linux.ie>
      836cf046
  23. 17 4月, 2005 1 次提交
    • L
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds 提交于
      Initial git repository build. I'm not bothering with the full history,
      even though we have it. We can create a separate "historical" git
      archive of that later if we want to, and in the meantime it's about
      3.2GB when imported into git - space that would just make the early
      git days unnecessarily complicated, when we don't have a lot of good
      infrastructure for it.
      
      Let it rip!
      1da177e4