On Mon, Nov 04, 2013 at 05:57:38AM -0800, Thomas Hellstrom wrote:
Used by the vmwgfx driver
That looks OK to me. And baremetal should not be
affected as the Intel VT-d driver turns of the SWIOTLB
driver - so it will still use the classic ttm pool code.
Reviewed-by: Konrad Rzeszutek Wilk
On Thu, Oct 31, 2013 at 04:13:11PM -0700, Keith Packard wrote:
This just renames them so that they can be used with the DRI3 extension
without causing too much confusion.
Signed-off-by: Keith Packard kei...@keithp.com
---
src/mesa/drivers/dri/common/dri_util.c | 50
On Thu, Oct 31, 2013 at 04:13:12PM -0700, Keith Packard wrote:
Make an easy place to splice in a DRI3 version of this function
Signed-off-by: Keith Packard kei...@keithp.com
---
src/mesa/drivers/dri/i915/intel_context.c | 90
+--
On Mon, Nov 04, 2013 at 05:57:37AM -0800, Thomas Hellstrom wrote:
These patches makes the vmwgfx driver use the DMA API to obtain valid
device addresses rather than blindly using physical addresses.
The main motivation is to be able to use a virtual IOMMU in the future.
Ooooh. Neat! Are
On Mon, Nov 04, 2013 at 05:57:39AM -0800, Thomas Hellstrom wrote:
The code handles three different cases:
1) physical page addresses. The ttm page array is used.
2) DMA subsystem addresses. A scatter-gather list is used.
3) Coherent pages. The ttm dma pool is used, together with the dma_ttm
