From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Devin Heitmueller <dheitmueller@kernellabs.com>
Cc: Benjamin Larsson <benjamin@southpole.se>,
linux-media@vger.kernel.org, Eddi De Pieri <eddi@depieri.net>
Subject: Re: PCTV 520e on Linux
Date: Fri, 14 Oct 2011 11:03:06 -0300 [thread overview]
Message-ID: <4E98411A.6040809@redhat.com> (raw)
In-Reply-To: <CAGoCfizDdx=a=mR5TRXw_Dnj9cw2_1C9NuRH2LR2gXxEzyfW3w@mail.gmail.com>
Em 14-10-2011 10:28, Devin Heitmueller escreveu:
> On Fri, Oct 14, 2011 at 9:19 AM, Mauro Carvalho Chehab
> <mchehab@redhat.com> wrote:
>>> While the basic chips used are different, they are completely
>>> different hardware designs and likely have different GPIO
>>> configurations as well as IF specs.
>>
>> The IF settings for xc5000 with DRX-K are solved with this patch:
>> http://patchwork.linuxtv.org/patch/7932/
>>
>> Basically, DRX-K will use whatever IF the tuner uses.
>
> While I fundamentally disagree with this change, I'm not going to nack
> it. That said, this wasn't the issue I was concerned with. My
> suggestion was simply that you cannot assume that all devices that
> happen to have a particular demod and tuner combo will always use the
> same IF configuration. The PCB layout can effect the optimal IF.
>
> This is one of those things that (like many tuners in the LinuxTV
> tree) will probably work good enough to get a signal lock for whoever
> added the board profile, but will result in poor tuning performance
> (and a failure to work in less-than-ideal reception conditions).
This patch doesn't prevent customizing the IF. It will just avoid the
need of setting the IF on both xc5000 and drx-k. Basically, (some) DRX-K
based boards use different IF's depending on the bandwidth and delivery
system type. Instead of adding a complex logic that would allow such
kind of IF adjustments on both, drx-k will simply inquire the tuner about
what IF is currently used.
>
> All that said, if somebody actually intends to hack on it, I can look
> up what the correct IF is for the 520e.
>
> Devin
>
prev parent reply other threads:[~2011-10-14 14:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-13 14:49 PCTV 520e on Linux Claus Olesen
2011-10-13 15:57 ` Devin Heitmueller
2011-10-13 16:07 ` Antti Palosaari
2011-10-13 16:15 ` Devin Heitmueller
2011-10-13 16:19 ` Antti Palosaari
2011-10-13 17:48 ` Devin Heitmueller
2011-10-13 23:06 ` Benjamin Larsson
2011-10-13 23:19 ` Devin Heitmueller
2011-10-14 13:19 ` Mauro Carvalho Chehab
2011-10-14 13:28 ` Devin Heitmueller
2011-10-14 14:01 ` AW: " Sönke Brandt
2011-10-14 14:04 ` Devin Heitmueller
2011-10-14 16:14 ` Mauro Carvalho Chehab
2011-10-14 16:41 ` Devin Heitmueller
2011-10-14 17:39 ` Mauro Carvalho Chehab
2011-10-14 18:38 ` Devin Heitmueller
2011-10-14 14:03 ` 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=4E98411A.6040809@redhat.com \
--to=mchehab@redhat.com \
--cc=benjamin@southpole.se \
--cc=dheitmueller@kernellabs.com \
--cc=eddi@depieri.net \
--cc=linux-media@vger.kernel.org \
/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.