From: Sylwester Nawrocki <sylvester.nawrocki@gmail.com>
To: Mauro Carvalho Chehab <mchehab@redhat.com>
Cc: LMML <linux-media@vger.kernel.org>,
Devin Heitmueller <devin.heitmueller@gmail.com>,
Hans Verkuil <hverkuil@xs4all.nl>,
Tomasz Stanislawski <t.stanislaws@samsung.com>
Subject: Re: [GIT PULL FOR 3.9] Exynos SoC media drivers updates
Date: Sun, 06 Jan 2013 13:34:53 +0100 [thread overview]
Message-ID: <50E96F6D.9080206@gmail.com> (raw)
In-Reply-To: <20130106093246.36f959da@redhat.com>
On 01/06/2013 12:32 PM, Mauro Carvalho Chehab wrote:
> Em Fri, 04 Jan 2013 23:39:12 +0100
> Sylwester Nawrocki<sylvester.nawrocki@gmail.com> escreveu:
>
>
>>> Tomasz Stanislawski (1):
>>> s5p-tv: mixer: fix handling of VIDIOC_S_FMT
>
> I'll drop this one for now. Devin raised a point: such changes would break
> existing applications.
>
> So, we'll need to revisit this topic before changing the drivers.
>
> Btw, I failed to find the corresponding patch at patchwork:
> http://patchwork.linuxtv.org/project/linux-media/list/?state=*&q=VIDIOC_S_FMT
>
> So, its status update may be wrong after flushing your pwclient commands.
Hmm, I got this patch from Tomasz by e-mail and added it to the pull
request.
I think it wasn't sent to the mailing list, but I noticed it only after
sending you the pull requests, when was preparing the pwclient commands.
I've just posted it now, sorry. The link is here:
http://patchwork.linuxtv.org/patch/16143
Tomasz created this patch specifically for the purpose of format negotiation
in video pipeline in the application we used to test various scenarios with
DMABUF. I agree this patch has a potential of breaking buggy user space
applications. I can't see other solution for it right now, there seems even
to be no possibility to return some flag in VIDIOC_S_FMT indicating that
format has been modified and is valid, when -EINVAL was returned. This
sounds
ugly anyway, but could ensure backward compatibility for applications that
exppect EINVAL when format has been changed. BTW, I wonder if it is only
fourcc,
or other format parameters as well - like width, height, some applications
expect to get EINVAL when those have changed.
Regards,
Sylwester
next prev parent reply other threads:[~2013-01-06 12:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-04 19:01 [GIT PULL FOR 3.9] Exynos SoC media drivers updates Sylwester Nawrocki
2013-01-04 22:39 ` Sylwester Nawrocki
2013-01-06 11:32 ` Mauro Carvalho Chehab
2013-01-06 12:34 ` Sylwester Nawrocki [this message]
2013-01-06 12:41 ` Mauro Carvalho Chehab
2013-01-06 12:53 ` Hans Verkuil
2013-01-06 13:04 ` Mauro Carvalho Chehab
2013-01-06 13:15 ` Sylwester Nawrocki
2013-01-06 13:18 ` Mauro Carvalho Chehab
2013-01-06 12:05 ` Mauro Carvalho Chehab
2013-01-06 12:58 ` Sylwester Nawrocki
2013-01-06 13:17 ` Mauro Carvalho Chehab
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=50E96F6D.9080206@gmail.com \
--to=sylvester.nawrocki@gmail.com \
--cc=devin.heitmueller@gmail.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@redhat.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.