1. 01 Jan, 2021 1 commit
  2. 22 Sep, 2020 1 commit
  3. 06 May, 2020 1 commit
  4. 01 Apr, 2020 1 commit
  5. 04 Feb, 2020 2 commits
  6. 14 Nov, 2019 1 commit
  7. 17 Nov, 2017 2 commits
  8. 25 Oct, 2017 1 commit
    • Roland Scheidegger's avatar
      gallium/util: remove some block alignment assertions · 20c77ae6
      Roland Scheidegger authored
      
      
      These assertions were revisited a couple of times in the past, and they
      still weren't quite right.
      The problem I was seeing (with some other state tracker) was a copy between
      two 512x512 s3tc textures, but from mip level 0 to mip level 8. Therefore,
      the destination has only size 2x2 (not a full block), so the box width/height
      was only 2, causing the assertion to trigger for src alignment.
      As far as I can tell, such a copy is completely legal, and because a correct
      assertion would get ridiculously complicated just get rid of it for good.
      Reviewed-by: Brian Paul's avatarBrian Paul <brianp@vmware.com>
      20c77ae6
  9. 24 Feb, 2017 2 commits
  10. 01 Jul, 2016 1 commit
  11. 30 Jun, 2016 3 commits
  12. 14 Jun, 2016 1 commit
    • Roland Scheidegger's avatar
      gallium/util: don't use blocksize for minify for assertions · afbf5888
      Roland Scheidegger authored
      
      
      The previous assertions required for texture sizes smaller than block_size
      that src_box.x + src_box.width still be block size.
      (e.g. for a texture with width 3, and src_box.x = 0, src_box.width would
      have to be 4 to not assert.)
      This caused some assertions with some other state tracker.
      It looks though like callers aren't expected to round up widths to block sizes
      (for sizes larger than block size the assertion would still have verified it
      wouldn't have been rounded up) so we simply shouldn't use a minify which
      rounds up to block size.
      (No piglit change with llvmpipe.)
      Reviewed-by: Jose Fonseca's avatarJose Fonseca <jfonseca@vmware.com>
      Reviewed-by: Brian Paul's avatarBrian Paul <brianp@vmware.com>
      afbf5888
  13. 13 Jun, 2016 1 commit
  14. 10 Jun, 2016 1 commit
  15. 25 Apr, 2016 1 commit
  16. 06 Jan, 2016 1 commit
  17. 03 Dec, 2015 1 commit
  18. 21 Aug, 2015 1 commit
  19. 25 Apr, 2014 1 commit
    • Roland Scheidegger's avatar
      gallium/util: use ui[4] instead of ui in union util_color · fa408232
      Roland Scheidegger authored
      util_color often merely represents a collection of bytes, however it is
      inconvenient if those bytes can only be accessed as floats/doubles for int
      formats exceeding 32bits.
      (Note that since rgba8 formats use one uint, not 4 bytes, hence the byte and
      short member were left as is.)
      fa408232
  20. 13 Jun, 2013 1 commit
  21. 12 Jun, 2013 1 commit
  22. 07 Jun, 2013 1 commit
  23. 28 Feb, 2013 1 commit
  24. 12 Feb, 2013 1 commit
  25. 04 Jan, 2013 1 commit
  26. 12 Dec, 2012 2 commits
  27. 06 Dec, 2012 2 commits
  28. 04 Dec, 2012 1 commit
  29. 09 Nov, 2012 2 commits
  30. 11 Oct, 2012 1 commit
    • Marek Olšák's avatar
      gallium: unify transfer functions · 369e4688
      Marek Olšák authored
      
      
      "get_transfer + transfer_map" becomes "transfer_map".
      "transfer_unmap + transfer_destroy" becomes "transfer_unmap".
      
      transfer_map must create and return the transfer object and transfer_unmap
      must destroy it.
      
      transfer_map is successful if the returned buffer pointer is not NULL.
      If transfer_map fails, the pointer to the transfer object remains unchanged
      (i.e. doesn't have to be NULL).
      Acked-by: Brian Paul's avatarBrian Paul <brianp@vmware.com>
      369e4688
  31. 30 Sep, 2012 1 commit
  32. 05 Aug, 2012 1 commit