1. 08 2月, 2007 3 次提交
  2. 07 12月, 2006 1 次提交
  3. 26 10月, 2006 1 次提交
  4. 22 9月, 2006 6 次提交
  5. 23 4月, 2006 1 次提交
    • D
      drm: possible cleanups · 5d23fafb
      Dave Airlie 提交于
      This patch contains the following possible cleanups:
      - make the following needlessly global function static:
       - drm_bufs.c: drm_addbufs_fb()
      - remove the following unused EXPORT_SYMBOL's:
       - drm_agpsupport.c: drm_agp_bind_memory
       - drm_bufs.c: drm_rmmap_locked
       - drm_bufs.c: drm_rmmap
       - drm_stub.c: drm_get_dev
      Signed-off-by: NAdrian Bunk <bunk@stusta.de>
      Signed-off-by: NDave Airlie <airlied@linux.ie>
      5d23fafb
  6. 19 3月, 2006 1 次提交
  7. 02 2月, 2006 1 次提交
  8. 11 1月, 2006 1 次提交
  9. 02 1月, 2006 1 次提交
  10. 24 10月, 2005 1 次提交
  11. 30 9月, 2005 1 次提交
  12. 25 9月, 2005 2 次提交
  13. 05 9月, 2005 2 次提交
  14. 20 8月, 2005 1 次提交
    • D
      drm: fixes for powerpc · 88f399cd
      Dave Airlie 提交于
      Remove a bogus check on whether an area is memory (we need a better interface)
      also change pgprot flags for powerpc
      don't check on x86-64 either
      
      From: Paul Mackerras <paulus@samba.org>
      Signed-off-by: NDave Airlie <airlied@linux.ie>
      88f399cd
  15. 07 8月, 2005 1 次提交
  16. 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
  17. 10 7月, 2005 8 次提交
  18. 07 7月, 2005 1 次提交
  19. 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
  20. 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