From: Sylwester Nawrocki <sylvester.nawrocki@gmail.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: "Sylwester Nawrocki" <s.nawrocki@samsung.com>,
"Mauro Carvalho Chehab" <mchehab@redhat.com>,
LMML <linux-media@vger.kernel.org>,
"Manu Abraham" <abraham.manu@gmail.com>,
"David Härdeman" <david@hardeman.nu>,
"Jonathan Corbet" <corbet@lwn.net>,
"Guennadi Liakhovetski" <g.liakhovetski@gmx.de>,
"Prabhakar Lad" <prabhakar.lad@ti.com>,
"Tomasz Stanislawski" <t.stanislaws@samsung.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Subject: DRM/V4L2 buffer sharing (was: Re: Patches submitted via linux-media ML that are at patchwork.linuxtv.org)
Date: Fri, 17 Aug 2012 23:01:01 +0200 [thread overview]
Message-ID: <502EB10D.8050006@gmail.com> (raw)
In-Reply-To: <2376005.crkqt4XIze@avalon>
Hi Laurent,
On 08/15/2012 11:09 PM, Laurent Pinchart wrote:
> On Wednesday 15 August 2012 18:13:19 Sylwester Nawrocki wrote:
>> On 08/15/2012 12:06 AM, Laurent Pinchart wrote:
>>> On Tuesday 14 August 2012 18:37:23 Sylwester Nawrocki wrote:
>>>> 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.
>>>
>>> What would be required to push it to v3.7 ?
>>
>> Mauro requested more test coverage on that, which is understood since this
>> is a fairly important API enhancement and the V4L2 video overlay API
>> replacement.
>>
>> We need DMABUF support added at some webcam driver and a DRM driver with
>> prime support (or some V4L2 output driver), I guess it would be best to
>> have that in a PC environment. It looks like i915/radeon/nouveau drivers
>> already have prime support.
>
> uvcvideo has recently been moved to videobuf2, using vb2_vmalloc. I can easily
> test that, except that I have no idea how to export buffers on the i915 side
> when X is running. Have you looked into that ?
All right. Yes, I'm also not sure yet how to do it. I tried it on a laptop
with i915 driver, but in the running system drmModeGetResources() just fails
with EPERM. I've CCed dri-devel, so hopefully someone can shed some light
on this.
>> The DRM driver could be an exporter of buffers that would be passed to the
>> webcam driver.
>>
>> And except the kernel patches we would need a test application, similar
>> to that one:
>> http://git.infradead.org/users/kmpark/public-apps/blob/a7e755629a74a7ac13788
>> 2032a0f7b2480fa1490:/v4l2-drm-example/dmabuf-sharing.c
>>
>> I haven't been closely following the DMABUF APIs development, I think
>> Tomasz could provide more details on that.
>>
>> It's likely I'll get around and prepare a test case as outlined above in
>> coming days. Anyway, it would be appreciated if someone else could give this
>> patch series a try.
>
> I've previously tested the patches on Renesas hardware, exporting buffers on
> the FBDEV side and importing them on the V4L2 side. We thus have test results
> for two different platforms, albeit all ARM-based.
I guess ARM is where those APIs will be used mostly, still it would be helpful
to have easier reproducible test environment.
--
Thanks,
Sylwester
next prev parent reply other threads:[~2012-08-17 21:01 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
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 ` Sylwester Nawrocki [this message]
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=502EB10D.8050006@gmail.com \
--to=sylvester.nawrocki@gmail.com \
--cc=abraham.manu@gmail.com \
--cc=corbet@lwn.net \
--cc=david@hardeman.nu \
--cc=dri-devel@lists.freedesktop.org \
--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 \
--cc=s.nawrocki@samsung.com \
--cc=t.stanislaws@samsung.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).