From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Michael Krufky <mkrufky@linuxtv.org>
Cc: Mike Isely <isely@pobox.com>,
linux-media <linux-media@vger.kernel.org>,
Communications nexus for pvrusb2 driver <pvrusb2@isely.net>,
stable@kernel.org
Subject: Re: pvrusb2: fix 7MHz & 8MHz DVB-T tuner support for HVR1900 rev D1F5
Date: Fri, 24 Feb 2012 17:27:45 -0200 [thread overview]
Message-ID: <4F47E4B1.10405@redhat.com> (raw)
In-Reply-To: <CAOcJUbwqtvWy+O5guZBj7T2f61=8oe+gwqH6Fbifu1PVz+THzQ@mail.gmail.com>
Em 07-02-2012 15:08, Michael Krufky escreveu:
> There are some new revisions of the HVR-1900 around whose DVB-T
> support is broken without this small bug-fix. Please merge asap -
> this fix needs to go to stable kernels as well. It applies cleanly
> against *all* recent kernels.
>
> The following changes since commit 805a6af8dba5dfdd35ec35dc52ec0122400b2610:
>
> Linux 3.2 (2012-01-04 15:55:44 -0800)
>
> are available in the git repository at:
> git://linuxtv.org/mkrufky/hauppauge surrey
>
> Michael Krufky (1):
> pvrusb2: fix 7MHz & 8MHz DVB-T tuner support for HVR1900 rev D1F5
>
> drivers/media/video/pvrusb2/pvrusb2-devattr.c | 10 ++++++++++
> 1 files changed, 10 insertions(+), 0 deletions(-)
> The D1F5 revision of the WinTV HVR-1900 uses a tda18271c2 tuner
> instead of a tda18271c1 tuner as used in revision D1E9. To
> account for this, we must hardcode the frontend configuration
> to use the same IF frequency configuration for both revisions
> of the device.
No, you don't need to hardcode the IF. Just use the get_if_frequency
callback at the demod, and it will work with whatever frequency you
use at the tuner.
Regards,
Mauro
next prev parent reply other threads:[~2012-02-24 19:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-07 17:08 pvrusb2: fix 7MHz & 8MHz DVB-T tuner support for HVR1900 rev D1F5 Michael Krufky
2012-02-24 19:27 ` Mauro Carvalho Chehab [this message]
2012-02-27 10:15 ` Michael Krufky
2012-02-27 11:44 ` Mauro Carvalho Chehab
2012-02-27 16:09 ` Michael Krufky
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=4F47E4B1.10405@redhat.com \
--to=mchehab@redhat.com \
--cc=isely@pobox.com \
--cc=linux-media@vger.kernel.org \
--cc=mkrufky@linuxtv.org \
--cc=pvrusb2@isely.net \
--cc=stable@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox