1. 07 2月, 2008 1 次提交
  2. 05 11月, 2007 1 次提交
  3. 15 10月, 2007 2 次提交
  4. 11 7月, 2007 5 次提交
  5. 08 5月, 2007 2 次提交
    • M
      radeon: Don't mess up page flipping when a file descriptor is closed. · 453ff94c
      Michel Dänzer 提交于
      There can still be other contexts that may use page flipping later on, so do
      just unilaterally 'clean it up', which could lead to the wrong page being
      displayed, e.g. when running 3D apps with a GLX compositing manager such as
      compiz using page flipping.
      Signed-off-by: NDave Airlie <airlied@linux.ie>
      453ff94c
    • 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
  6. 15 12月, 2006 1 次提交
  7. 22 9月, 2006 5 次提交
  8. 24 6月, 2006 2 次提交
  9. 25 3月, 2006 1 次提交
  10. 19 3月, 2006 3 次提交
  11. 18 2月, 2006 1 次提交
  12. 03 1月, 2006 1 次提交
  13. 02 1月, 2006 1 次提交
  14. 16 12月, 2005 1 次提交
  15. 23 11月, 2005 1 次提交
  16. 11 11月, 2005 1 次提交
  17. 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
  18. 30 9月, 2005 2 次提交
  19. 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
  20. 11 9月, 2005 2 次提交
  21. 16 8月, 2005 1 次提交
  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. 23 6月, 2005 1 次提交
    • D
      drm: 32/64-bit DRM ioctl compatibility patch · 9a186645
      Dave Airlie 提交于
      The patch is against a 2.6.11 kernel tree.  I am running this with a
      32-bit X server (compiled up from X.org CVS as of a couple of weeks
      ago) and 32-bit DRI libraries and clients.  All the userland stuff is
      identical to what I am using under a 32-bit kernel on my G4 powerbook
      (which is a 32-bit machine of course).  I haven't tried compiling up a
      64-bit X server or clients yet.
      
      In the compatibility routines I have assumed that the kernel can
      safely access user addresses after set_fs(KERNEL_DS).  That is, where
      an ioctl argument structure contains pointers to other structures, and
      those other structures are already compatible between the 32-bit and
      64-bit ABIs (i.e. they only contain things like chars, shorts or
      ints), I just check the address with access_ok() and then pass it
      through to the 64-bit ioctl code.  I believe this approach may not
      work on sparc64, but it does work on ppc64 and x86_64 at least.
      
      One tricky area which may need to be revisited is the question of how
      to handle the handles which we pass back to userspace to identify
      mappings.  These handles are generated in the ADDMAP ioctl and then
      passed in as the offset value to mmap.  However, offset values for
      mmap seem to be generated in other ways as well, particularly for AGP
      mappings.
      
      The approach I have ended up with is to generate a fake 32-bit handle
      only for _DRM_SHM mappings.  The handles for other mappings (AGP, REG,
      FB) are physical addresses which are already limited to 32 bits, and
      generating fake handles for them created all sorts of problems in the
      mmap/nopage code.
      
      This patch has been updated to use the new compatibility ioctls.
      
      From: Paul Mackerras <paulus@samba.org>
      Signed-off-by: NDave Airlie <airlied@linux.ie>
      9a186645
  24. 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