1. 15 3月, 2010 2 次提交
  2. 25 2月, 2010 1 次提交
  3. 18 2月, 2010 1 次提交
    • J
      drm/radeon/kms: simplify memory controller setup V2 · d594e46a
      Jerome Glisse 提交于
      Get rid of _location and use _start/_end also simplify the
      computation of vram_start|end & gtt_start|end. For R1XX-R2XX
      we place VRAM at the same address of PCI aperture, those GPU
      shouldn't have much memory and seems to behave better when
      setup that way. For R3XX and newer we place VRAM at 0. For
      R6XX-R7XX AGP we place VRAM before or after AGP aperture this
      might limit to limit the VRAM size but it's very unlikely.
      For IGP we don't change the VRAM placement.
      
      Tested on (compiz,quake3,suspend/resume):
      PCI/PCIE:RV280,R420,RV515,RV570,RV610,RV710
      AGP:RV100,RV280,R420,RV350,RV620(RPB*),RV730
      IGP:RS480(RPB*),RS690,RS780(RPB*),RS880
      
      RPB: resume previously broken
      
      V2 correct commit message to reflect more accurately the bug
      and move VRAM placement to 0 for most of the GPU to avoid
      limiting VRAM.
      Signed-off-by: NJerome Glisse <jglisse@redhat.com>
      Signed-off-by: NDave Airlie <airlied@redhat.com>
      d594e46a
  4. 11 2月, 2010 1 次提交
  5. 09 2月, 2010 4 次提交
  6. 05 2月, 2010 2 次提交
  7. 21 1月, 2010 1 次提交
  8. 14 1月, 2010 1 次提交
  9. 08 1月, 2010 3 次提交
  10. 23 12月, 2009 1 次提交
  11. 16 12月, 2009 2 次提交
  12. 10 12月, 2009 1 次提交
  13. 08 12月, 2009 3 次提交
  14. 02 12月, 2009 5 次提交
  15. 04 11月, 2009 1 次提交
  16. 26 10月, 2009 2 次提交
  17. 16 10月, 2009 1 次提交
  18. 12 10月, 2009 1 次提交
  19. 08 10月, 2009 1 次提交
  20. 05 10月, 2009 1 次提交
  21. 02 10月, 2009 3 次提交
  22. 26 9月, 2009 1 次提交
  23. 25 9月, 2009 1 次提交
    • D
      drm/radeon/kms: don't require up to 64k allocations. (v2) · 513bcb46
      Dave Airlie 提交于
      This avoids needing to do a kmalloc > PAGE_SIZE for the main
      indirect buffer chunk, it adds an accessor for all reads from
      the chunk and caches a single page at a time for subsequent
      reads.
      
      changes since v1:
      Use a two page pool which should be the most common case
      a single packet spanning > PAGE_SIZE will be hit, but I'm
      having trouble seeing anywhere we currently generate anything like that.
      hopefully proper short page copying at end
      added parser_error flag to set deep errors instead of having to test
      every ib value fetch.
      fixed bug in patch that went to list.
      Signed-off-by: NDave Airlie <airlied@redhat.com>
      513bcb46