0 Replies Latest reply on Nov 13, 2009 12:41 PM by CaptainN

    CAL_RESALLOC_GLOBAL_BUFFER and CAL_RESALLOC_CACHABLE

    CaptainN
      makes sense to combine them for local?

      1. If these two flags are used ORed for calResAllocRemote2D it means use non-tiled surface and allocate CACHABLE system memory. Whether using CACHABLE flag makes sense when calResAllocLocal2D is called?

      2. When CAL_RESALLOC_GLOBAL_BUFFER makes sense when calResAllocRemote2D is used, as remote (system) memory normally not tiled?

      3.Whether using CAL_RESALLOC_GLOBAL_BUFFER is the requirement for CS output buffers?