From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Sylwester Nawrocki <sylvester.nawrocki@gmail.com>
Cc: "Laurent Pinchart" <laurent.pinchart@ideasonboard.com>,
"Sylwester Nawrocki" <s.nawrocki@samsung.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: Re: DRM/V4L2 buffer sharing
Date: Fri, 17 Aug 2012 19:03:47 -0300 [thread overview]
Message-ID: <502EBFC3.2090205@redhat.com> (raw)
In-Reply-To: <502EB10D.8050006@gmail.com>
Em 17-08-2012 18:01, Sylwester Nawrocki escreveu:
> 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.
Likely, you need to run with root permission to use it, or to write an Xorg
driver.
It is probably easier to get the V4L driver there, that uses the VIDIOC_OVERLAY
stuff, and make it work via DMABUF:
http://cgit.freedesktop.org/xorg/driver/xf86-video-v4l/
In order to test it, xawtv has already the code needed to talk with the v4l
plugin.
What the plugin does is to export the video board as a XV extension, accessible
via xawtv. It currently talks with the display card also via XV, but I believe it
won't be hard to port it to work with DMABUF.
As the interface between xawtv and the v4l plugin is just Xv, changing the code
there from VIDIOC_OVERLAY to DMABUF should be trivial.
Regards,
Mauro
next prev parent reply other threads:[~2012-08-17 22:03 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 ` 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 ` Mauro Carvalho Chehab [this message]
2012-08-17 22:54 ` DRM/V4L2 buffer sharing 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=502EBFC3.2090205@redhat.com \
--to=mchehab@redhat.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=prabhakar.lad@ti.com \
--cc=s.nawrocki@samsung.com \
--cc=sylvester.nawrocki@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.