From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 0/2] GEM CMA DMA-BUF support
Date: Mon, 15 Apr 2013 15:39:20 +0200 [thread overview]
Message-ID: <3961884.6b7yW6F7aE@avalon> (raw)
In-Reply-To: <7037846.bb3IFv1e3D@avalon>
On Thursday 28 March 2013 16:12:25 Laurent Pinchart wrote:
> On Thursday 14 March 2013 15:05:29 Laurent Pinchart wrote:
> > On Tuesday 12 March 2013 15:45:36 Laurent Pinchart wrote:
> > > Hello,
> > >
> > > This two patches add support for GEM CMA objects import and export as
> > > dma-buf file handles.
> > >
> > > There's not much to be added about the patches themselves, they're
> > > pretty self-explicit. The code is based on the Exynos DRM DMA-BUF
> > > implementation.
> > >
> > > The exporter role has been successfully tested with the Renesas R-Car DU
> > > driver.
> > >
> > > Laurent Pinchart (2):
> > > drm: GEM CMA: Split object creation into object alloc and DMA memory
> > >
> > > alloc
> > >
> > > drm: GEM CMA: Add DRM PRIME support
> > >
> > > drivers/gpu/drm/drm_gem_cma_helper.c | 376 +++++++++++++++++++++++++---
> > > include/drm/drm_gem_cma_helper.h | 9 +
> > > 2 files changed, 356 insertions(+), 29 deletions(-)
> >
> > Oops, the CC list was missing from the original post, sorry about that.
> > It's fixed now.
>
> No comment about these patches ? I'd like to get them in v3.10 if possible.
Ping ?
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2013-04-15 13:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-12 14:45 [PATCH 0/2] GEM CMA DMA-BUF support Laurent Pinchart
2013-03-12 14:45 ` [PATCH 1/2] drm: GEM CMA: Split object creation into object alloc and DMA memory alloc Laurent Pinchart
2013-03-12 14:45 ` [PATCH 2/2] drm: GEM CMA: Add DRM PRIME support Laurent Pinchart
2013-03-14 14:05 ` [PATCH 0/2] GEM CMA DMA-BUF support Laurent Pinchart
2013-03-28 15:12 ` Laurent Pinchart
2013-04-15 13:39 ` Laurent Pinchart [this message]
2013-04-15 13:52 ` Rob Clark
2013-04-15 13:58 ` Laurent Pinchart
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3961884.6b7yW6F7aE@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).