From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Taylor Ralph <taylor.ralph@gmail.com>
Cc: Devin Heitmueller <dheitmueller@kernellabs.com>,
Janne Grunau <j@jannau.net>,
linux-media@vger.kernel.org
Subject: Re: [PATCH] [media] hdpvr: update picture controls to support firmware versions > 0.15
Date: Mon, 07 Nov 2011 10:21:45 -0200 [thread overview]
Message-ID: <4EB7CD59.1010303@redhat.com> (raw)
In-Reply-To: <CAOTqeXpY3uvy7Dq3fi1wTD5nRx1r1LMo7=XEfJdxyURY2opKuw@mail.gmail.com>
Em 21-10-2011 01:33, Taylor Ralph escreveu:
> On Thu, Oct 20, 2011 at 3:26 PM, Taylor Ralph <taylor.ralph@gmail.com> wrote:
>> On Thu, Oct 20, 2011 at 2:14 PM, Devin Heitmueller
>> <dheitmueller@kernellabs.com> wrote:
>>> On Thu, Oct 20, 2011 at 1:08 PM, Janne Grunau <j@jannau.net> wrote:
>>>> I think such scenario is unlikely but I don't know it for sure and
>>>> I don't want to force anyone to test every firmware version.
>>>> Ignoring them for firmware version < 16 should be safe since we assume
>>>> they had no effect. Returning -EINVAL might break API-ignoring
>>>> applications written with the HD PVR in mind but I think it's a better
>>>> approach than silently ignoring those controls.
>>>
>>> At this point, let's just make it so that the old behavior is
>>> unchanged for old firmwares, meaning from both an API standpoint as
>>> well as what the values are. At some point if somebody cares enough
>>> to go back and fix the support so that the controls actually work with
>>> old firmwares, they can take that up as a separate task. In reality,
>>> it is likely that nobody will ever do that, as the "easy answer" is
>>> just to upgrade to firmware 16.
>>>
>>> Taylor, could you please tweak your patch to that effect and resubmit?
>>>
>>
>> Sure, I'll try to get to it tonight and have it tested.
>>
>
> OK, I've updated the patch per your requests. I made this patch
> against the latest kernel source but I'm unable to test since my
> 2.6.32 kernel has symbol issues with the new v4l code.
Please, add your Signed-off-by: to the patch. This is a requirement for
it to be accepted upstream[1].
Thanks,
Mauro
[1] See: http://linuxtv.org/wiki/index.php/Development:_Submitting_Patches#Developer.27s_Certificate_of_Origin_1.1
>
> Regards.
> --
> Taylor
next prev parent reply other threads:[~2011-11-07 12:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-20 15:24 [PATCH] [media] hdpvr: update picture controls to support firmware versions > 0.15 Taylor Ralph
2011-10-20 15:30 ` Devin Heitmueller
2011-10-20 16:09 ` Taylor Ralph
2011-10-20 16:23 ` Janne Grunau
2011-10-20 16:35 ` Devin Heitmueller
2011-10-20 17:08 ` Janne Grunau
2011-10-20 18:14 ` Devin Heitmueller
2011-10-20 19:26 ` Taylor Ralph
2011-10-21 3:33 ` Taylor Ralph
2011-11-07 12:21 ` Mauro Carvalho Chehab [this message]
2011-11-08 0:54 ` Taylor Ralph
2011-12-21 22:14 ` Taylor Ralph
2012-02-01 3:04 ` Taylor Ralph
2012-02-14 20:43 ` Jarod Wilson
2012-02-14 21:32 ` Devin Heitmueller
2012-02-14 22:09 ` Jarod Wilson
2012-02-15 11:46 ` missing patches in patchwork (was Re: [PATCH] [media] hdpvr: update picture controls to support firmware versions > 0.15) Janne Grunau
2012-02-15 12:07 ` 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=4EB7CD59.1010303@redhat.com \
--to=mchehab@redhat.com \
--cc=dheitmueller@kernellabs.com \
--cc=j@jannau.net \
--cc=linux-media@vger.kernel.org \
--cc=taylor.ralph@gmail.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