From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Devin Heitmueller <dheitmueller@kernellabs.com>
Cc: Alina Friedrichsen <x-alina@gmx.net>,
linux-media@vger.kernel.org, rglowery@exemail.com.au
Subject: Re: [PATCH v3] tuner_xc2028: Allow selection of the frequency adjustment code for XC3028
Date: Wed, 27 Jul 2011 13:06:53 -0300 [thread overview]
Message-ID: <4E30379D.1050301@redhat.com> (raw)
In-Reply-To: <CAGoCfiyx8d_ALG6N+9Zru8Hps3iACx=jCq+bUDkadQMFae=6gg@mail.gmail.com>
Em 27-07-2011 11:58, Devin Heitmueller escreveu:
> On Wed, Jul 27, 2011 at 10:34 AM, Mauro Carvalho Chehab
> <mchehab@redhat.com> wrote:
>> Btw, what's the video standard that you're using? DTV7? Does your device use
>> a xc3028 or xc3028xl? Whats's your demod and board?
>
> It was in the first sentence of his email. He's got an HVR-1400,
> which uses the xc3028L and dib7000p.
>
> It's also worth noting that he isn't the first person to complain
> about tuning offset problems with the xc3028L. Just look at the
> rather nasty hack some random user did for the EVGA inDtube (which is
> xc3208L/s5h1409).
>
> http://linuxtv.org/wiki/index.php/EVGA_inDtube
>
> Bear in mind that it worked when I added the original support.
> Somebody caused a regression since then though.
>
> In short, I can appreciate why the user is frustrated. The xc3028L
> support worked at one point and then somebody broke the xc3028 driver.
>
> Devin
>
Btw, looking at the firmware for xc3028L [1], with the v4l-utils
/utils/xc3028-firmware/firmware-tool:
[1] http://steventoth.net/linux/hvr1400/xc3028L-v36.fw
firmware file name: /lib/firmware/xc3028L-v36.fw
firmware name: xc2028 firmware
version: 3.6 (774)
standards: 81
Firmware 0, type: BASE FW F8MHZ (0x00000003), id: (0000000000000000), size: 9144
Firmware 1, type: BASE FW F8MHZ MTS (0x00000007), id: (0000000000000000), size: 9030
Firmware 2, type: BASE FW FM (0x00000401), id: (0000000000000000), size: 9054
Firmware 3, type: BASE FW FM INPUT1 (0x00000c01), id: (0000000000000000), size: 9068
Firmware 4, type: BASE FW (0x00000001), id: (0000000000000000), size: 9132
Firmware 5, type: BASE FW MTS (0x00000005), id: (0000000000000000), size: 9006
Firmware 6, type: STD FW (0x00000000), id: PAL/BG (0000000000000007), size: 161
Firmware 7, type: STD FW MTS (0x00000004), id: PAL/BG (0000000000000007), size: 169
Firmware 8, type: STD FW (0x00000000), id: PAL/BG (0000000000000007), size: 161
Firmware 9, type: STD FW MTS (0x00000004), id: PAL/BG (0000000000000007), size: 169
Firmware 10, type: STD FW (0x00000000), id: PAL/BG (0000000000000007), size: 161
Firmware 11, type: STD FW MTS (0x00000004), id: PAL/BG (0000000000000007), size: 169
Firmware 12, type: STD FW (0x00000000), id: PAL/BG (0000000000000007), size: 161
Firmware 13, type: STD FW MTS (0x00000004), id: PAL/BG (0000000000000007), size: 169
Firmware 14, type: STD FW (0x00000000), id: PAL/DK (00000000000000e0), size: 161
Firmware 15, type: STD FW MTS (0x00000004), id: PAL/DK (00000000000000e0), size: 169
Firmware 16, type: STD FW (0x00000000), id: PAL/DK (00000000000000e0), size: 161
Firmware 17, type: STD FW MTS (0x00000004), id: PAL/DK (00000000000000e0), size: 169
Firmware 18, type: STD FW (0x00000000), id: SECAM/K1 (0000000000200000), size: 161
Firmware 19, type: STD FW MTS (0x00000004), id: SECAM/K1 (0000000000200000), size: 169
Firmware 20, type: STD FW (0x00000000), id: SECAM/K3 (0000000004000000), size: 161
Firmware 21, type: STD FW MTS (0x00000004), id: SECAM/K3 (0000000004000000), size: 169
Firmware 22, type: STD FW D2633 DTV6 ATSC (0x00010030), id: (0000000000000000), size: 149
Firmware 23, type: STD FW D2620 DTV6 QAM (0x00000068), id: (0000000000000000), size: 149
Firmware 24, type: STD FW D2633 DTV6 QAM (0x00000070), id: (0000000000000000), size: 149
Firmware 25, type: STD FW D2620 DTV7 (0x00000088), id: (0000000000000000), size: 149
Firmware 26, type: STD FW D2633 DTV7 (0x00000090), id: (0000000000000000), size: 149
Firmware 27, type: STD FW D2620 DTV78 (0x00000108), id: (0000000000000000), size: 149
Firmware 28, type: STD FW D2633 DTV78 (0x00000110), id: (0000000000000000), size: 149
Firmware 29, type: STD FW D2620 DTV8 (0x00000208), id: (0000000000000000), size: 149
Firmware 30, type: STD FW D2633 DTV8 (0x00000210), id: (0000000000000000), size: 149
Firmware 31, type: STD FW FM (0x00000400), id: (0000000000000000), size: 135
Firmware 32, type: STD FW (0x00000000), id: PAL/I (0000000000000010), size: 161
Firmware 33, type: STD FW MTS (0x00000004), id: PAL/I (0000000000000010), size: 169
Firmware 34, type: STD FW (0x00000000), id: SECAM/L (0000000000400000), size: 161
Firmware 35, type: STD FW (0x00000000), id: SECAM/Lc (0000000000800000), size: 161
Firmware 36, type: STD FW (0x00000000), id: NTSC/M Kr (0000000000008000), size: 161
Firmware 37, type: STD FW LCD (0x00001000), id: NTSC/M Kr (0000000000008000), size: 161
Firmware 38, type: STD FW LCD NOGD (0x00003000), id: NTSC/M Kr (0000000000008000), size: 161
Firmware 39, type: STD FW MTS (0x00000004), id: NTSC/M Kr (0000000000008000), size: 169
Firmware 40, type: STD FW (0x00000000), id: NTSC PAL/M PAL/N (000000000000b700), size: 161
Firmware 41, type: STD FW LCD (0x00001000), id: NTSC PAL/M PAL/N (000000000000b700), size: 161
Firmware 42, type: STD FW LCD NOGD (0x00003000), id: NTSC PAL/M PAL/N (000000000000b700), size: 161
Firmware 43, type: STD FW (0x00000000), id: NTSC/M Jp (0000000000002000), size: 161
Firmware 44, type: STD FW MTS (0x00000004), id: NTSC PAL/M PAL/N (000000000000b700), size: 169
Firmware 45, type: STD FW MTS LCD (0x00001004), id: NTSC PAL/M PAL/N (000000000000b700), size: 169
Firmware 46, type: STD FW MTS LCD NOGD (0x00003004), id: NTSC PAL/M PAL/N (000000000000b700), size: 169
Firmware 47, type: SCODE FW HAS IF (0x60000000), IF = 3.28 MHz id: (0000000000000000), size: 192
Firmware 48, type: SCODE FW HAS IF (0x60000000), IF = 3.30 MHz id: (0000000000000000), size: 192
Firmware 49, type: SCODE FW HAS IF (0x60000000), IF = 3.44 MHz id: (0000000000000000), size: 192
Firmware 50, type: SCODE FW HAS IF (0x60000000), IF = 3.46 MHz id: (0000000000000000), size: 192
Firmware 51, type: SCODE FW DTV6 ATSC OREN36 HAS IF (0x60210020), IF = 3.80 MHz id: (0000000000000000), size: 192
Firmware 52, type: SCODE FW HAS IF (0x60000000), IF = 4.00 MHz id: (0000000000000000), size: 192
Firmware 53, type: SCODE FW DTV6 ATSC TOYOTA388 HAS IF (0x60410020), IF = 4.08 MHz id: (0000000000000000), size: 192
Firmware 54, type: SCODE FW HAS IF (0x60000000), IF = 4.20 MHz id: (0000000000000000), size: 192
Firmware 55, type: SCODE FW MONO HAS IF (0x60008000), IF = 4.32 MHz id: NTSC/M Kr (0000000000008000), size: 192
Firmware 56, type: SCODE FW HAS IF (0x60000000), IF = 4.45 MHz id: (0000000000000000), size: 192
Firmware 57, type: SCODE FW MTS LCD NOGD MONO IF HAS IF (0x6002b004), IF = 4.50 MHz id: NTSC PAL/M PAL/N (000000000000b700), size: 192
Firmware 58, type: SCODE FW DTV78 DTV8 ZARLINK456 HAS IF (0x62000300), IF = 4.56 MHz id: (0000000000000000), size: 192
Firmware 59, type: SCODE FW LCD NOGD IF HAS IF (0x60023000), IF = 4.60 MHz id: NTSC/M Kr (0000000000008000), size: 192
Firmware 60, type: SCODE FW DTV6 QAM DTV7 ZARLINK456 HAS IF (0x620000e0), IF = 4.76 MHz id: (0000000000000000), size: 192
Firmware 61, type: SCODE FW HAS IF (0x60000000), IF = 4.94 MHz id: (0000000000000000), size: 192
Firmware 62, type: SCODE FW DTV78 DTV8 DIBCOM52 HAS IF (0x61000300), IF = 5.20 MHz id: (0000000000000000), size: 192
Firmware 63, type: SCODE FW HAS IF (0x60000000), IF = 5.26 MHz id: (0000000000000000), size: 192
Firmware 64, type: SCODE FW MONO HAS IF (0x60008000), IF = 5.32 MHz id: PAL/BG (0000000000000007), size: 192
Firmware 65, type: SCODE FW DTV7 DTV8 DIBCOM52 CHINA HAS IF (0x65000280), IF = 5.40 MHz id: (0000000000000000), size: 192
Firmware 66, type: SCODE FW DTV6 ATSC OREN538 HAS IF (0x60110020), IF = 5.58 MHz id: (0000000000000000), size: 192
Firmware 67, type: SCODE FW HAS IF (0x60000000), IF = 5.64 MHz id: PAL/BG (0000000000000007), size: 192
Firmware 68, type: SCODE FW HAS IF (0x60000000), IF = 5.74 MHz id: PAL/BG (0000000000000007), size: 192
Firmware 69, type: SCODE FW HAS IF (0x60000000), IF = 5.90 MHz id: (0000000000000000), size: 192
Firmware 70, type: SCODE FW MONO HAS IF (0x60008000), IF = 6.00 MHz id: PAL/DK PAL/I SECAM/K3 SECAM/L SECAM/Lc (0000000004c000f0), size: 192
Firmware 71, type: SCODE FW DTV6 QAM ATSC LG60 F6MHZ HAS IF (0x68050060), IF = 6.20 MHz id: (0000000000000000), size: 192
Firmware 72, type: SCODE FW HAS IF (0x60000000), IF = 6.24 MHz id: PAL/I (0000000000000010), size: 192
Firmware 73, type: SCODE FW MONO HAS IF (0x60008000), IF = 6.32 MHz id: SECAM/K1 (0000000000200000), size: 192
Firmware 74, type: SCODE FW HAS IF (0x60000000), IF = 6.34 MHz id: SECAM/K1 (0000000000200000), size: 192
Firmware 75, type: SCODE FW MONO HAS IF (0x60008000), IF = 6.50 MHz id: PAL/DK SECAM/K3 (00000000040000e0), size: 192
Firmware 76, type: SCODE FW DTV6 ATSC ATI638 HAS IF (0x60090020), IF = 6.58 MHz id: (0000000000000000), size: 192
Firmware 77, type: SCODE FW HAS IF (0x60000000), IF = 6.60 MHz id: PAL/DK (00000000000000e0), size: 192
Firmware 78, type: SCODE FW MONO HAS IF (0x60008000), IF = 6.68 MHz id: PAL/DK (00000000000000e0), size: 192
Firmware 79, type: SCODE FW DTV6 ATSC TOYOTA794 HAS IF (0x60810020), IF = 8.14 MHz id: (0000000000000000), size: 192
Firmware 80, type: SCODE FW HAS IF (0x60000000), IF = 8.20 MHz id: (0000000000000000), size: 192
It seems that the firmware file was not properly generated, as it is pointing two firmwares
with DIBCOM52 and two firmwares with ZARLINK456, one with 200 kHz of offset for the other.
This is not a big issue, as the driver won't use this information anymore, but that means
that maybe there's something wrong at the scode tables.
In any case, there's no firmware associated with IF = 5 MHz, so, if the driver logic is ok,
it won't be loading any SCODE table for the device.
Cheers,
Mauro
next prev parent reply other threads:[~2011-07-27 16:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-22 18:35 [PATCH v3] tuner_xc2028: Allow selection of the frequency adjustment code for XC3028 Alina Friedrichsen
2011-07-27 14:34 ` Mauro Carvalho Chehab
2011-07-27 14:58 ` Devin Heitmueller
2011-07-27 15:50 ` Mauro Carvalho Chehab
2011-07-27 16:06 ` Mauro Carvalho Chehab [this message]
2011-07-28 19:38 ` Mauro Carvalho Chehab
2011-07-29 6:49 ` Alina Friedrichsen
-- strict thread matches above, loose matches on Subject: below --
2011-08-01 14:55 jean.bruenn
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=4E30379D.1050301@redhat.com \
--to=mchehab@redhat.com \
--cc=dheitmueller@kernellabs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox