From: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
To: Warren Sturm <warren.sturm@gmail.com>
Cc: Andy Walls <awalls@md.metrocast.net>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
andy <andy@silverblocksystems.net>
Subject: Re: PVR-250 Composite 3 unavailable [Re: ivtv driver]
Date: Wed, 11 Nov 2015 15:14:25 -0200 [thread overview]
Message-ID: <20151111151425.32eadd9b@recife.lan> (raw)
In-Reply-To: <1446831368.20743.7.camel@gmail.com>
Em Fri, 06 Nov 2015 10:36:08 -0700
Warren Sturm <warren.sturm@gmail.com> escreveu:
> On Mon, 2015-10-26 at 19:49 -0400, Andy Walls wrote:
> > On October 26, 2015 7:13:52 PM EDT, Warren Sturm <
> > warren.sturm@gmail.com> wrote:
> > > Hi Andy.
> > >
> > > I don't know whether this was intended but the pvr250 lost the
> > > composite 3 input when going from kernel version 4.1.10 to 4.2.3.
> > >
> > > This is on a Fedora 22 x86_64 system.
> > >
> > >
> > > Thanks for any insight.
> >
> > Unintentional.
> >
> > I'm guessing this commit was the problem:
> >
> > http://git.linuxtv.org/cgit.cgi/media_tree.git/commit/drivers/media/pci/ivtv/ivtv-driver.c?id=09290cc885937cab3b2d60a6d48fe3d2d3e04061
My fault. I'll revert that patch.
> >
> > Could you confirm?
> >
> > R,
> > Andy
>
> Ok. I rebuilt the SRPM for kernel-4.2.5-201 with the patch reverted
> and installed it.
>
> uname -a
> Linux wrs 4.2.5-201.fc22.x86_64 #1 SMP Fri Nov 6 00:13:17 MST 2015 x86_64 x86_64 x86_64 GNU/Linux
>
> Attached are the v4l2-ctl --list-inputs for the respective kernels.
>
> Hope this is sufficient confirmation.
>
>
>
prev parent reply other threads:[~2015-11-11 17:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1445901232.9389.2.camel@gmail.com>
2015-10-26 23:49 ` PVR-250 Composite 3 unavailable [Re: ivtv driver] Andy Walls
2015-11-06 17:36 ` Warren Sturm
2015-11-11 17:14 ` Mauro Carvalho Chehab [this message]
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=20151111151425.32eadd9b@recife.lan \
--to=mchehab@osg.samsung.com \
--cc=andy@silverblocksystems.net \
--cc=awalls@md.metrocast.net \
--cc=linux-media@vger.kernel.org \
--cc=warren.sturm@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;
as well as URLs for NNTP newsgroup(s).