1. 27 Sep, 2009 1 commit
  2. 08 Sep, 2009 1 commit
    • Jerome Glisse's avatar
      drm/radeon/kms: add r600 KMS support · 3ce0a23d
      Jerome Glisse authored
      This adds the r600 KMS + CS support to the Linux kernel.
      
      The r600 TTM support is quite basic and still needs more
      work esp around using interrupts, but the polled fencing
      should work okay for now.
      
      Also currently TTM is using memcpy to do VRAM moves,
      the code is here to use a 3D blit to do this, but
      isn't fully debugged yet.
      
      Authors:
      Alex Deucher <alexdeucher@gmail.com>
      Dave Airlie <airlied@redhat.com>
      Jerome Glisse <jglisse@redhat.com>
      Signed-off-by: default avatarJerome Glisse <jglisse@redhat.com>
      Signed-off-by: default avatarDave Airlie <airlied@redhat.com>
      3ce0a23d
  3. 01 Sep, 2009 1 commit
  4. 20 Aug, 2009 1 commit
  5. 19 Aug, 2009 1 commit
  6. 29 Jul, 2009 3 commits
    • Dave Airlie's avatar
      drm/radeon/kms: vram sizing on certain r100 chips needs workaround. · 7a50f01a
      Dave Airlie authored
      If an rn50/r100/m6/m7 GPU has < 64MB RAM, i.e. 8/16/32, the
      aperture used to calculate the MC_FB_LOCATION needs to be worked
      out from the CONFIG_APER_SIZE register, and not the actual vram size.
      
      TTM VRAM size was also being initialised wrong, use actual vram size
      to initialise it.
      Signed-off-by: default avatarDave Airlie <airlied@redhat.com>
      7a50f01a
    • Michel Dänzer's avatar
      drm/radeon: Fall back to evicting BOs with memcpy if necessary. · 1ab2e105
      Michel Dänzer authored
      Otherwise if there's no GTT space we would fail the eviction, leading to
      cascaded failure.
      Signed-off-by: default avatarMichel Dänzer <daenzer@vmware.com>
      Signed-off-by: default avatarDave Airlie <airlied@redhat.com>
      1ab2e105
    • Dave Airlie's avatar
      drm/radeon/kms: add initial colortiling support. · e024e110
      Dave Airlie authored
      This adds new set/get tiling interfaces where the pitch
      and macro/micro tiling enables can be set. Along with
      a flag to decide if this object should have a surface when mapped.
      
      The only thing we need to allocate with a mapped surface should be
      the frontbuffer. Note rotate scanout shouldn't require one, and
      back/depth shouldn't either, though mesa needs some fixes.
      
      It fixes the TTM interfaces along Thomas's suggestions, and I've tested
      the surface stealing code with two X servers and not seen any lockdep issues.
      
      I've stopped tiling the fbcon frontbuffer, as I don't see there being
      any advantage other than testing, I've left the testing commands in there,
      just flip the fb_tiled to true in radeon_fb.c
      
      Open: Can we integrate endian swapping in with this?
      
      Future features:
      texture tiling - need to relocate texture registers TXOFFSET* with tiling info.
      
      This also merges Michel's cleanup surfaces regs at init time patch
      even though it makes sense on its own, this patch really relies on it.
      
      Some PowerMac firmwares set up a tiling surface at the beginning of VRAM
      which messes us up otherwise.
      that patch is:
      Signed-off-by: default avatarMichel Dänzer <daenzer@vmware.com>
      Signed-off-by: default avatarDave Airlie <airlied@redhat.com>
      e024e110
  7. 15 Jul, 2009 1 commit
  8. 18 Jun, 2009 1 commit
  9. 15 Jun, 2009 1 commit
    • Jerome Glisse's avatar
      drm/radeon: introduce kernel modesetting for radeon hardware · 771fe6b9
      Jerome Glisse authored
      Add kernel modesetting support to radeon driver, use the ttm memory
      manager to manage memory and DRM/GEM to provide userspace API.
      In order to avoid backward compatibility issue and to allow clean
      design and code the radeon kernel modesetting use different code path
      than old radeon/drm driver.
      
      When kernel modesetting is enabled the IOCTL of radeon/drm
      driver are considered as invalid and an error message is printed
      in the log and they return failure.
      
      KMS enabled userspace will use new API to talk with the radeon/drm
      driver. The new API provide functions to create/destroy/share/mmap
      buffer object which are then managed by the kernel memory manager
      (here TTM). In order to submit command to the GPU the userspace
      provide a buffer holding the command stream, along this buffer
      userspace have to provide a list of buffer object used by the
      command stream. The kernel radeon driver will then place buffer
      in GPU accessible memory and will update command stream to reflect
      the position of the different buffers.
      
      The kernel will also perform security check on command stream
      provided by the user, we want to catch and forbid any illegal use
      of the GPU such as DMA into random system memory or into memory
      not owned by the process supplying the command stream. This part
      of the code is still incomplete and this why we propose that patch
      as a staging driver addition, future security might forbid current
      experimental userspace to run.
      
      This code support the following hardware : R1XX,R2XX,R3XX,R4XX,R5XX
      (radeon up to X1950). Works is underway to provide support for R6XX,
      R7XX and newer hardware (radeon from HD2XXX to HD4XXX).
      
      Authors:
          Jerome Glisse <jglisse@redhat.com>
          Dave Airlie <airlied@redhat.com>
          Alex Deucher <alexdeucher@gmail.com>
      Signed-off-by: default avatarJerome Glisse <jglisse@redhat.com>
      Signed-off-by: default avatarDave Airlie <airlied@redhat.com>
      Signed-off-by: default avatarAlex Deucher <alexdeucher@gmail.com>
      Signed-off-by: default avatarDave Airlie <airlied@redhat.com>
      771fe6b9