From: Anders Thomson <aeriksson2@gmail.com>
To: Mauro Carvalho Chehab <mchehab@redhat.com>
Cc: "linux-media@vger.kernel.org" <linux-media@vger.kernel.org>
Subject: Re: tda8290 regression fix
Date: Sun, 23 Sep 2012 23:06:20 +0200 [thread overview]
Message-ID: <505F79CC.9080005@gmail.com> (raw)
In-Reply-To: <505F5760.2030602@gmail.com>
On 2012-09-23 20:39, Anders Thomson wrote:
> On 2012-09-23 19:54, Anders Thomson wrote:
> > > diff --git a/drivers/media/pci/saa7134/saa7134-cards.c b/drivers/media/pci/saa7134/saa7134-cards.c
> > > index bc08f1d..98b482e 100644
> > > --- a/drivers/media/pci/saa7134/saa7134-cards.c
> > > +++ b/drivers/media/pci/saa7134/saa7134-cards.c
> > > @@ -3288,13 +3288,13 @@ struct saa7134_board saa7134_boards[] = {
> > > .name = "Pinnacle PCTV 310i",
> > > .audio_clock = 0x00187de7,
> > > .tuner_type = TUNER_PHILIPS_TDA8290,
> > > .radio_type = UNSET,
> > > .tuner_addr = ADDR_UNSET,
> > > .radio_addr = ADDR_UNSET,
> > > - .tuner_config = 1,
> > > + .tuner_config = 0,
> > > .mpeg = SAA7134_MPEG_DVB,
> > > .gpiomask = 0x000200000,
> > > .inputs = {{
> > > .name = name_tv,
> > > .vmux = 4,
> > > .amux = TV,
> > >
> > >
> > > Please test if the above patch fixes the issue you're suffering[1]. If so, then
> > > we'll need to add a modprobe parameter to allow disabling LNA for saa7134 devices
> > > with LNA.
> > >
> > > [1] Note: the above is not the fix, as some users of this board may be using the
> > > original antenna, and changing tuner_config will break things for them; the right
> > > fix is likely to allow controlling the LNA via userspace.
> > Tried that patch on 3.5.3. No improvement, unfortunately.
> I have to retract that. It turns out that there is some strange interaction
> between the cabletv box and the card. When I rebooted into 'my' patch
> I still got the noisy signal. I then power cycled the cabletv box, and
> voila,
> I got a good signal on my own patch.
Awfully sorry about this. After having had the familty sit in and check
the differences,
I must say that the patch does not fix the issue. This time around I
have x11grabs with
ffmpeg to show if you want.
I'll be away from the card until the end of the coming week. Then, I'll
bring out the multimeter...
Best regards,
/Anders
next prev parent reply other threads:[~2012-09-23 21:06 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-30 11:27 tda8290 regression fix Anders Thomson
2012-09-15 16:34 ` Mauro Carvalho Chehab
2012-09-15 17:39 ` Anders Thomson
2012-09-15 17:44 ` Anders Thomson
2012-09-15 17:58 ` Mauro Carvalho Chehab
2012-09-15 18:12 ` Anders Thomson
2012-09-15 22:25 ` Mauro Carvalho Chehab
2012-09-16 8:48 ` Anders Thomson
2012-09-18 9:53 ` Mauro Carvalho Chehab
2012-09-19 13:01 ` Anders Thomson
2012-09-19 16:45 ` Mauro Carvalho Chehab
2012-09-19 19:25 ` Anders Thomson
[not found] ` <CAGncdOae+VoAAUWz3x84zUA-TCMeMmNONf_ktNFd1p7c-o5H_A@mail.gmail.com>
2012-09-21 14:49 ` Mauro Carvalho Chehab
[not found] ` <8ed8c988-fa8c-41fc-9f33-cccdceb1b232@email.android.com>
2012-09-23 11:36 ` Mauro Carvalho Chehab
2012-09-23 17:54 ` Anders Thomson
2012-09-23 18:14 ` Mauro Carvalho Chehab
2012-09-23 18:39 ` Anders Thomson
2012-09-23 21:06 ` Anders Thomson [this message]
2012-10-01 16:56 ` Anders Thomson
2012-11-15 20:43 ` Anders Thomson
2012-12-04 11:00 ` Anders Thomson
2012-09-15 18:28 ` Anders Thomson
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=505F79CC.9080005@gmail.com \
--to=aeriksson2@gmail.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@redhat.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).