linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sylwester Nawrocki <s.nawrocki@samsung.com>
To: Mauro Carvalho Chehab <mchehab@redhat.com>
Cc: LMML <linux-media@vger.kernel.org>,
	"Manu Abraham" <abraham.manu@gmail.com>,
	"David Härdeman" <david@hardeman.nu>,
	"Laurent Pinchart" <laurent.pinchart@ideasonboard.com>,
	"Jonathan Corbet" <corbet@lwn.net>,
	"Guennadi Liakhovetski" <g.liakhovetski@gmx.de>,
	"Prabhakar Lad" <prabhakar.lad@ti.com>
Subject: Re: Patches submitted via linux-media ML that are at patchwork.linuxtv.org
Date: Tue, 14 Aug 2012 18:37:23 +0200	[thread overview]
Message-ID: <502A7EC3.7030803@samsung.com> (raw)
In-Reply-To: <502A4CD1.1020108@redhat.com>

On 08/14/2012 03:04 PM, Mauro Carvalho Chehab wrote:
> This one requires more testing:
> 
> May,15 2012: [GIT,PULL,FOR,3.5] DMABUF importer feature in V4L2 API                 http://patchwork.linuxtv.org/patch/11268  Sylwester Nawrocki <s.nawrocki@samsung.com>

Hmm, this is not valid any more. Tomasz just posted a new patch series
that adds DMABUF importer and exporter feature altogether.

[PATCHv8 00/26] Integration of videobuf2 with DMABUF

I guess we need someone else to submit test patches for other H/W
than just Samsung SoCs. I'm not sure if we've got enough resources
to port this to other hardware. We have been using these features
internally for some time already. It's been 2 kernel releases and
I can see only Ack tags from Laurent on Tomasz's patch series, hence
it seems there is no wide interest in DMABUF support in V4L2 and
this patch series is probably going to stay in a fridge for another
few kernel releases.

--

Regards,
Sylwester


  parent reply	other threads:[~2012-08-14 16:37 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-14 13:04 Patches submitted via linux-media ML that are at patchwork.linuxtv.org Mauro Carvalho Chehab
2012-08-14 13:36 ` Prabhakar Lad
2012-08-14 14:02   ` Mauro Carvalho Chehab
2012-08-14 13:46 ` Hans Verkuil
2012-08-14 14:28   ` Mauro Carvalho Chehab
2012-08-14 15:21     ` Laurent Pinchart
2012-08-15  7:33       ` Michael Jones
2012-08-15 19:24         ` Mauro Carvalho Chehab
2012-08-15  9:54     ` Hans Verkuil
2012-08-15 10:13       ` Guennadi Liakhovetski
2012-08-15 19:34       ` Mauro Carvalho Chehab
2012-08-14 15:10 ` Sylwester Nawrocki
2012-08-14 15:18   ` Sylwester Nawrocki
2012-08-14 15:16 ` Laurent Pinchart
2012-08-15 21:43   ` Mauro Carvalho Chehab
2012-08-14 16:37 ` Sylwester Nawrocki [this message]
2012-08-14 22:06   ` Laurent Pinchart
2012-08-15 16:13     ` Sylwester Nawrocki
2012-08-15 21:09       ` Laurent Pinchart
2012-08-17 21:01         ` DRM/V4L2 buffer sharing (was: Re: Patches submitted via linux-media ML that are at patchwork.linuxtv.org) Sylwester Nawrocki
2012-08-17 22:03           ` DRM/V4L2 buffer sharing Mauro Carvalho Chehab
2012-08-17 22:54             ` Laurent Pinchart
2012-08-15  8:30 ` Patches submitted via linux-media ML that are at patchwork.linuxtv.org Guennadi Liakhovetski
2012-08-15 23:46 ` Mauro Carvalho Chehab
2012-08-16 10:38   ` Prabhakar Lad

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=502A7EC3.7030803@samsung.com \
    --to=s.nawrocki@samsung.com \
    --cc=abraham.manu@gmail.com \
    --cc=corbet@lwn.net \
    --cc=david@hardeman.nu \
    --cc=g.liakhovetski@gmx.de \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@redhat.com \
    --cc=prabhakar.lad@ti.com \
    /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).