From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Alina Friedrichsen <x-alina@gmx.net>
Cc: linux-media@vger.kernel.org, rglowery@exemail.com.au
Subject: Re: [RFC PATCH] Getting Hauppauge WinTV HVR-1400 (XC3028L) to work
Date: Sun, 23 Jan 2011 12:12:32 -0200 [thread overview]
Message-ID: <4D3C3750.8060301@redhat.com> (raw)
In-Reply-To: <20110123001615.86290@gmx.net>
Hi Alina,
Em 22-01-2011 22:16, Alina Friedrichsen escreveu:
> With this patch my DVB-T receiver works now like before 2.6.34, only the
> first four tunings fails, after that all works fine.
> The code was still in there, only commented out. As the original author
> says, please test it with different XC3028 hardware. If no one has problems
> with it, please commit it.
>
> Signed-off-by: Alina Friedrichsen <x-alina@gmx.net>
> ---
> diff -urNp linux-2.6.37.orig/drivers/media/common/tuners/tuner-xc2028.c linux-2.6.37/drivers/media/common/tuners/tuner-xc2028.c
> --- linux-2.6.37.orig/drivers/media/common/tuners/tuner-xc2028.c 2011-01-22 23:46:57.000000000 +0100
> +++ linux-2.6.37/drivers/media/common/tuners/tuner-xc2028.c 2011-01-22 23:51:33.000000000 +0100
> @@ -967,7 +967,7 @@ static int generic_set_freq(struct dvb_f
> * newer firmwares
> */
>
> -#if 1
> +#if 0
> /*
> * The proper adjustment would be to do it at s-code table.
> * However, this didn't work, as reported by
This is problematic, as it seems to be country-specific and/or demod-specific.
We'll need to work on a different solution for it. On what Country do you live?
By looking at HVR1400 entry, it uses a dibcom 7000p demod.
We need to know what are country/demod for the users for whose the old code
were broken.
Cheers,
Mauro
next prev parent reply other threads:[~2011-01-23 14:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-23 0:16 [RFC PATCH] Getting Hauppauge WinTV HVR-1400 (XC3028L) to work Alina Friedrichsen
2011-01-23 14:12 ` Mauro Carvalho Chehab [this message]
2011-01-23 16:33 ` Alina Friedrichsen
2011-01-26 9:52 ` Alina Friedrichsen
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=4D3C3750.8060301@redhat.com \
--to=mchehab@redhat.com \
--cc=linux-media@vger.kernel.org \
--cc=rglowery@exemail.com.au \
--cc=x-alina@gmx.net \
/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.