> > +static struct dma_page *__ttm_dma_alloc_page(struct dma_pool *pool)
> > +{
> > + struct dma_page *d_page;
> > +
> > + d_page = kmalloc(sizeof(struct dma_page), GFP_KERNEL);
> > + if (!d_page)
> > + return NULL;
> > +
> > + d_page->vaddr = dma_alloc_coherent(pool->dev, pool->s
> > +static struct dma_page *__ttm_dma_alloc_page(struct dma_pool *pool)
> > +{
> > + struct dma_page *d_page;
> > +
> > + d_page = kmalloc(sizeof(struct dma_page), GFP_KERNEL);
> > + if (!d_page)
> > + return NULL;
> > +
> > + d_page->vaddr = dma_alloc_coherent(pool->dev, pool->s
On Wed, Oct 19, 2011 at 06:19:29PM -0400, Konrad Rzeszutek Wilk wrote:
> In TTM world the pages for the graphic drivers are kept in three different
> pools: write combined, uncached, and cached (write-back). When the pages
> are used by the graphic driver the graphic adapter via its built in MMU
>
On Wed, Oct 19, 2011 at 06:19:29PM -0400, Konrad Rzeszutek Wilk wrote:
> In TTM world the pages for the graphic drivers are kept in three different
> pools: write combined, uncached, and cached (write-back). When the pages
> are used by the graphic driver the graphic adapter via its built in MMU
>
In TTM world the pages for the graphic drivers are kept in three different
pools: write combined, uncached, and cached (write-back). When the pages
are used by the graphic driver the graphic adapter via its built in MMU
(or AGP) programs these pages in. The programming requires the virtual address
