From: Nicolas Dufresne <nicolas.dufresne@collabora.com>
To: Mauro Carvalho Chehab <m.chehab@samsung.com>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Hans Verkuil <hverkuil@xs4all.nl>,
Hans de Goede <hdegoede@redhat.com>,
linux-media@vger.kernel.org, Pawel Osciak <pawel@osciak.com>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Kyungmin Park <kyungmin.park@samsung.com>
Subject: Re: [PATCH/RFC v2 1/2] v4l: vb2: Don't return POLLERR during transient buffer underruns
Date: Mon, 15 Sep 2014 10:33:01 -0400 [thread overview]
Message-ID: <5416F89D.9080006@collabora.com> (raw)
In-Reply-To: <20140915105503.105233bf.m.chehab@samsung.com>
Le 2014-09-15 09:55, Mauro Carvalho Chehab a écrit :
> The DQBUF locking fixup was merged on libv4l2 for version 1.2. So, the
> potential breakage happens when libv4l2 is 1.2 and Gstreamer versions
> before 1.4.
>
> Do you have any procedure on gstreamer to fix a bug on stable releases?
A backport is possible, even though not trivial. Also, due to resources
there is no guaranty of a new stable 1.2 release. For GStreamer 0.10, it
is no longer maintained since 2 years already (mentioning since Laurent
was using an old vendor specific version base on this). Though this
situation isn't different from using a vendor specific kernel.
> Those VBI applications don't have any, as they're not actively
> maintained anymore. Even if we patch them today, I guess it could take
> a long time for those changes to be propagated on distros.
>
> So, I guess that the best is to try to fix Gstreamer on the distros
> that are using libv4l version 1.2 and a pre-1.4 Gstreamer version.
This seems an unlikely mix, as Gst 1.4 was released at around the same
moment as libv4l2 1.2.
cheers,
Nicolas
next prev parent reply other threads:[~2014-09-15 14:33 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-05 12:23 [PATCH/RFC v2 0/2] vb2: Report POLLERR for fatal errors only Laurent Pinchart
2014-06-05 12:23 ` [PATCH/RFC v2 1/2] v4l: vb2: Don't return POLLERR during transient buffer underruns Laurent Pinchart
2014-06-06 5:15 ` Pawel Osciak
2014-06-06 9:50 ` Hans de Goede
2014-06-06 9:58 ` Hans Verkuil
2014-06-06 13:42 ` Laurent Pinchart
2014-09-15 11:14 ` Hans Verkuil
2014-09-15 12:02 ` Mauro Carvalho Chehab
2014-09-15 12:49 ` Laurent Pinchart
2014-09-15 12:56 ` Nicolas Dufresne
2014-09-15 13:55 ` Mauro Carvalho Chehab
2014-09-15 14:33 ` Nicolas Dufresne [this message]
2014-09-15 15:51 ` Mauro Carvalho Chehab
2014-09-16 10:29 ` Laurent Pinchart
2014-09-16 11:18 ` Hans Verkuil
2014-09-16 12:19 ` Laurent Pinchart
2014-06-05 12:23 ` [PATCH/RFC v2 2/2] v4l: vb2: Add fatal error condition flag Laurent Pinchart
2014-06-06 5:31 ` Pawel Osciak
2014-06-06 9:19 ` Laurent Pinchart
2014-06-06 9:31 ` Hans Verkuil
2014-06-06 9:46 ` Laurent Pinchart
2014-06-06 9:55 ` Hans Verkuil
2014-06-06 13:42 ` Laurent Pinchart
2014-06-06 13:45 ` Hans Verkuil
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=5416F89D.9080006@collabora.com \
--to=nicolas.dufresne@collabora.com \
--cc=hdegoede@redhat.com \
--cc=hverkuil@xs4all.nl \
--cc=kyungmin.park@samsung.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=m.chehab@samsung.com \
--cc=m.szyprowski@samsung.com \
--cc=pawel@osciak.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).