All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Nicolas Dufresne <nicolas.dufresne@collabora.com>,
	Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: LibV4L2 and CREATE_BUFS issues
Date: Sat, 13 Dec 2014 11:41:13 +0100	[thread overview]
Message-ID: <548C17C9.2060809@redhat.com> (raw)
In-Reply-To: <5488748B.7060703@collabora.com>

Hi,

On 10-12-14 17:27, Nicolas Dufresne wrote:
> Hi,
>
> we recently fixed our CREATE_BUFS support in GStreamer master. It works
> nicely with UVC drivers. The problem is that libv4l2 isn't aware of it,
> and endup taking terribly decision the least quickly lead to crash.
>
> I'm not sure what that right approach. It seems non-trivial to support
> it, at least it would require a bit more knowledge of the converter code
> and memory model. Maybe we should at least make sure that CREATE_BUF
> fails if we are doing conversion ? Some input on that would be appreciated.

I think making CREATE_BUFS fail when doing conversion is probably best,
note that gstreamer should be able to tell which formats will lead to doing
conversion, and that it can try to avoid those.

Regards,

Hans

  reply	other threads:[~2014-12-13 10:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-10 16:27 LibV4L2 and CREATE_BUFS issues Nicolas Dufresne
2014-12-13 10:41 ` Hans de Goede [this message]
2014-12-13 16:15   ` Nicolas Dufresne
2014-12-14  9:49     ` Hans de Goede
2014-12-14 14:24       ` Nicolas Dufresne
2014-12-15 15:58         ` Hans de Goede
2014-12-15 16:35           ` Nicolas Dufresne

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=548C17C9.2060809@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=linux-media@vger.kernel.org \
    --cc=nicolas.dufresne@collabora.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.