Re: Problems tuning PAL-D with a Hauppauge HVR-1110 (TDA18271 tuner) - workaround hack included
On Friday 30 September 2011, Malcolm Priestley tvbox...@gmail.com wrote: On 28/09/11 13:50, Simon Farnsworth wrote: (note - the CC list is everyone over 50% certainty from get_maintainer.pl) I'm having problems getting a Hauppauge HVR-1110 card to successfully tune PAL-D at 85.250 MHz vision frequency; by experimentation, I've determined that the tda18271 is tuning to a frequency 1.25 MHz lower than the vision frequency I've requested, so the following workaround fixes it for me. Are you sure the transmitter concerned doesn't have a VSB filter for an adjacent DVB-T digital transmitter? The transmitter concerned is a test pattern generator - it has no filters applied to its output. The intended customer for this device is in China, hence the use of PAL-D. -- Simon Farnsworth Software Engineer ONELAN Limited http://www.onelan.com/ -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Problems tuning PAL-D with a Hauppauge HVR-1110 (TDA18271 tuner) - workaround hack included
On Friday 30 September 2011, Andy Walls awa...@md.metrocast.net wrote: Steven Toth st...@kernellabs.com wrote: The TDA18271 driver on linux DOES NOT use the same I/F's that the windows driver uses. Reason? Mike Decided to follow the data sheet and NOT use the Hauppauge specifically select IFs. If you have one of the latest HVR1600's with that analog tuner, does PAL-D work with it without and offset? I don't have a current model HVR-1600 to hand - if I get hold of one, I will test it. -- Simon Farnsworth Software Engineer ONELAN Limited http://www.onelan.com/ -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Problems tuning PAL-D with a Hauppauge HVR-1110 (TDA18271 tuner) - workaround hack included
Em 28-09-2011 09:50, Simon Farnsworth escreveu:
(note - the CC list is everyone over 50% certainty from get_maintainer.pl)
I'm having problems getting a Hauppauge HVR-1110 card to successfully
tune PAL-D at 85.250 MHz vision frequency; by experimentation, I've
determined that the tda18271 is tuning to a frequency 1.25 MHz lower
than the vision frequency I've requested, so the following workaround
fixes it for me.
diff --git a/drivers/media/common/tuners/tda18271-fe.c
b/drivers/media/common/tuners/tda18271-fe.c
index 63cc400..1a94e1a 100644
--- a/drivers/media/common/tuners/tda18271-fe.c
+++ b/drivers/media/common/tuners/tda18271-fe.c
@@ -1031,6 +1031,7 @@ static int tda18271_set_analog_params(struct
dvb_frontend *fe,
mode = I;
} else if (params-std V4L2_STD_DK) {
map = std_map-atv_dk;
+freq += 125;
mode = DK;
} else if (params-std V4L2_STD_SECAM_L) {
map = std_map-atv_l;
If I am to fix this bug, instead of a hack like that, it seems to be better
to split the .atv_dk line at the struct tda18271_std_map maps on
drivers/media/common/tuners/tda18271-maps.c.
Looking at the datasheet, on page 43, available at:
http://www.nxp.com/documents/data_sheet/TDA18271HD.pdf
The offset values for IF seem ok, but maybe your device is using some variant
of this chip that requires a different maps table.
I've checked with a signal analyser, and confirmed that my signal
generator is getting the spectrum right - I am seeing vision peaking
at 85.25 MHz, with one sideband going down to 84.5 MHz, and the other
going up to 90.5MHz. I also see an audio carrier at 91.75 MHz.
I'm going to run with this hack in place, but I'd appreciate it if
someone who knew more about the TDA18271 looked at this, and either
gave me a proper fix for testing, or confirmed that what I'm doing is
right.
--
Simon Farnsworth
Software Engineer
ONELAN Limited
http://www.onelan.com/
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Problems tuning PAL-D with a Hauppauge HVR-1110 (TDA18271 tuner) - workaround hack included
On Friday 30 September 2011, Mauro Carvalho Chehab mche...@infradead.org
wrote:
Em 28-09-2011 09:50, Simon Farnsworth escreveu:
(note - the CC list is everyone over 50% certainty from get_maintainer.pl)
I'm having problems getting a Hauppauge HVR-1110 card to successfully
tune PAL-D at 85.250 MHz vision frequency; by experimentation, I've
determined that the tda18271 is tuning to a frequency 1.25 MHz lower
than the vision frequency I've requested, so the following workaround
fixes it for me.
diff --git a/drivers/media/common/tuners/tda18271-fe.c
b/drivers/media/common/tuners/tda18271-fe.c
index 63cc400..1a94e1a 100644
--- a/drivers/media/common/tuners/tda18271-fe.c
+++ b/drivers/media/common/tuners/tda18271-fe.c
@@ -1031,6 +1031,7 @@ static int tda18271_set_analog_params(struct
dvb_frontend *fe,
mode = I;
} else if (params-std V4L2_STD_DK) {
map = std_map-atv_dk;
+freq += 125;
mode = DK;
} else if (params-std V4L2_STD_SECAM_L) {
map = std_map-atv_l;
If I am to fix this bug, instead of a hack like that, it seems to be better
to split the .atv_dk line at the struct tda18271_std_map maps on
drivers/media/common/tuners/tda18271-maps.c.
Looking at the datasheet, on page 43, available at:
http://www.nxp.com/documents/data_sheet/TDA18271HD.pdf
The offset values for IF seem ok, but maybe your device is using some variant
of this chip that requires a different maps table.
How would I identify that?
I definitely need the hack on multiple different HVR1110 cards, in different
motherboards, so if it's a new variant needing a new maps table, it should
be possible to distinguish it from the other devices somehow - but I have no
idea how.
--
Simon Farnsworth
Software Engineer
ONELAN Limited
http://www.onelan.com/
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Problems tuning PAL-D with a Hauppauge HVR-1110 (TDA18271 tuner) - workaround hack included
On Friday 30 September 2011, Mauro Carvalho Chehab mche...@infradead.org
wrote:
Em 28-09-2011 09:50, Simon Farnsworth escreveu:
(note - the CC list is everyone over 50% certainty from get_maintainer.pl)
I'm having problems getting a Hauppauge HVR-1110 card to successfully
tune PAL-D at 85.250 MHz vision frequency; by experimentation, I've
determined that the tda18271 is tuning to a frequency 1.25 MHz lower
than the vision frequency I've requested, so the following workaround
fixes it for me.
diff --git a/drivers/media/common/tuners/tda18271-fe.c
b/drivers/media/common/tuners/tda18271-fe.c
index 63cc400..1a94e1a 100644
--- a/drivers/media/common/tuners/tda18271-fe.c
+++ b/drivers/media/common/tuners/tda18271-fe.c
@@ -1031,6 +1031,7 @@ static int tda18271_set_analog_params(struct
dvb_frontend *fe,
mode = I;
} else if (params-std V4L2_STD_DK) {
map = std_map-atv_dk;
+freq += 125;
mode = DK;
} else if (params-std V4L2_STD_SECAM_L) {
map = std_map-atv_l;
If I am to fix this bug, instead of a hack like that, it seems to be better
to split the .atv_dk line at the struct tda18271_std_map maps on
drivers/media/common/tuners/tda18271-maps.c.
Looking at the datasheet, on page 43, available at:
http://www.nxp.com/documents/data_sheet/TDA18271HD.pdf
The offset values for IF seem ok, but maybe your device is using some variant
of this chip that requires a different maps table.
How would I identify this? I definitely need the hack on multiple different
HVR1110 cards, in different motherboards. I get apparently perfect reception
if I apply the hack, so clearly something is wrong.
--
Simon Farnsworth
Software Engineer
ONELAN Limited
http://www.onelan.com/
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Problems tuning PAL-D with a Hauppauge HVR-1110 (TDA18271 tuner) - workaround hack included
Em 30-09-2011 08:03, Simon Farnsworth escreveu:
On Friday 30 September 2011, Mauro Carvalho Chehab mche...@infradead.org
wrote:
Em 28-09-2011 09:50, Simon Farnsworth escreveu:
(note - the CC list is everyone over 50% certainty from get_maintainer.pl)
I'm having problems getting a Hauppauge HVR-1110 card to successfully
tune PAL-D at 85.250 MHz vision frequency; by experimentation, I've
determined that the tda18271 is tuning to a frequency 1.25 MHz lower
than the vision frequency I've requested, so the following workaround
fixes it for me.
diff --git a/drivers/media/common/tuners/tda18271-fe.c
b/drivers/media/common/tuners/tda18271-fe.c
index 63cc400..1a94e1a 100644
--- a/drivers/media/common/tuners/tda18271-fe.c
+++ b/drivers/media/common/tuners/tda18271-fe.c
@@ -1031,6 +1031,7 @@ static int tda18271_set_analog_params(struct
dvb_frontend *fe,
mode = I;
} else if (params-std V4L2_STD_DK) {
map = std_map-atv_dk;
+freq += 125;
mode = DK;
} else if (params-std V4L2_STD_SECAM_L) {
map = std_map-atv_l;
If I am to fix this bug, instead of a hack like that, it seems to be better
to split the .atv_dk line at the struct tda18271_std_map maps on
drivers/media/common/tuners/tda18271-maps.c.
Looking at the datasheet, on page 43, available at:
http://www.nxp.com/documents/data_sheet/TDA18271HD.pdf
The offset values for IF seem ok, but maybe your device is using some variant
of this chip that requires a different maps table.
How would I identify this? I definitely need the hack on multiple different
HVR1110 cards, in different motherboards.
Michael/Devin may be able to double check what tda18271 variants are used at the
hvr1100 supported models.
It seems that there are 5 HVR-1100 model variants:
drivers/media/video/saa7134/saa7134-cards.c: case 67019: /* WinTV-HVR1110
(Retail, IR Blaster, hybrid, FM, SVid/Comp, 3.5mm audio in) */
drivers/media/video/saa7134/saa7134-cards.c: case 67209: /* WinTV-HVR1110
(Retail, IR Receive, hybrid, FM, SVid/Comp, 3.5mm audio in) */
drivers/media/video/saa7134/saa7134-cards.c: case 67559: /* WinTV-HVR1110
(OEM, no IR, hybrid, FM, SVid/Comp, RCA aud) */
drivers/media/video/saa7134/saa7134-cards.c: case 67569: /* WinTV-HVR1110
(OEM, no IR, hybrid, FM) */
drivers/media/video/saa7134/saa7134-cards.c: case 67579: /* WinTV-HVR1110
(OEM, no IR, hybrid, no FM) */
I get apparently perfect reception
if I apply the hack, so clearly something is wrong.
Yes, but, on the other hand, if the device has the C2 or HD variant of tda18271,
the driver locks correct, acording with the datasheet.
Cheers,
Mauro
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Problems tuning PAL-D with a Hauppauge HVR-1110 (TDA18271 tuner) - workaround hack included
Em 30-09-2011 08:11, Simon Farnsworth escreveu:
On Friday 30 September 2011, Mauro Carvalho Chehab mche...@infradead.org
wrote:
Em 28-09-2011 09:50, Simon Farnsworth escreveu:
(note - the CC list is everyone over 50% certainty from get_maintainer.pl)
I'm having problems getting a Hauppauge HVR-1110 card to successfully
tune PAL-D at 85.250 MHz vision frequency; by experimentation, I've
determined that the tda18271 is tuning to a frequency 1.25 MHz lower
than the vision frequency I've requested, so the following workaround
fixes it for me.
diff --git a/drivers/media/common/tuners/tda18271-fe.c
b/drivers/media/common/tuners/tda18271-fe.c
index 63cc400..1a94e1a 100644
--- a/drivers/media/common/tuners/tda18271-fe.c
+++ b/drivers/media/common/tuners/tda18271-fe.c
@@ -1031,6 +1031,7 @@ static int tda18271_set_analog_params(struct
dvb_frontend *fe,
mode = I;
} else if (params-std V4L2_STD_DK) {
map = std_map-atv_dk;
+freq += 125;
mode = DK;
} else if (params-std V4L2_STD_SECAM_L) {
map = std_map-atv_l;
If I am to fix this bug, instead of a hack like that, it seems to be better
to split the .atv_dk line at the struct tda18271_std_map maps on
drivers/media/common/tuners/tda18271-maps.c.
Looking at the datasheet, on page 43, available at:
http://www.nxp.com/documents/data_sheet/TDA18271HD.pdf
The offset values for IF seem ok, but maybe your device is using some variant
of this chip that requires a different maps table.
How would I identify that?
I definitely need the hack on multiple different HVR1110 cards, in different
motherboards, so if it's a new variant needing a new maps table, it should
be possible to distinguish it from the other devices somehow - but I have no
idea how.
The tveeprom.c uses the board eeprom to read the tuner model. I might be wrong,
but
when Hauppauge uses a different component, a new entry is created there.
Regards,
Mauro
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Problems tuning PAL-D with a Hauppauge HVR-1110 (TDA18271 tuner) - workaround hack included
On Fri, Sep 30, 2011 at 7:59 AM, Mauro Carvalho Chehab mche...@infradead.org wrote: Michael/Devin may be able to double check what tda18271 variants are used at the hvr1100 supported models. Mike could confirm definitively but I would be very surprised if it was anything other than a C2. I also don't think we've had multiple revisions of that board (other than the ones in the list which were all released at the same time and are just different population options). All that said, I also wonder if perhaps this is an issue with the analog demod as opposed to the tuner. It feels unlikely but that might explain why I didn't see similar results when I did the testing on the cx231xx/tda18271 combo back in February. The big problem here really though is that somebody who is knowledgeable of the driver internals needs to dig into the issue, and I don't foresee that happening in the immediate future (I cannot speak for Michael but I've been too tied up in other projects). I'm definitely not discounting Simon's skills or findings, but this needs to be investigated in a context beyond the tuner/demod combination found on a single product. Devin -- Devin J. Heitmueller - Kernel Labs http://www.kernellabs.com -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Problems tuning PAL-D with a Hauppauge HVR-1110 (TDA18271 tuner) - workaround hack included
On 28/09/11 13:50, Simon Farnsworth wrote: (note - the CC list is everyone over 50% certainty from get_maintainer.pl) I'm having problems getting a Hauppauge HVR-1110 card to successfully tune PAL-D at 85.250 MHz vision frequency; by experimentation, I've determined that the tda18271 is tuning to a frequency 1.25 MHz lower than the vision frequency I've requested, so the following workaround fixes it for me. Are you sure the transmitter concerned doesn't have a VSB filter for an adjacent DVB-T digital transmitter? VSB fitlers have been used on UK(PAL-I) transmitters for some time. From downloads.bbc.co.uk/rd/pubs/whp/whp-pdf-files/WHP023.pdf To avoid the likelihood of PAL-I interference to DTT transmissions, the proposal is to use a System B/G VSB filter which provides at least 30 dB of sideband attenuation at 1.4 MHz below the vision carrier. It is also necessary to reduce the image sidebands resulting from transmitter non-linearity, and the method is to fit a high-order bandpass filter at the transmitter output. Typically, the overall sideband response will be -2 dB at (fv - 0.75) MHz and -20 dB at (fv - 1.25) MHz, where fv is the frequency of the vision carrier. -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Problems tuning PAL-D with a Hauppauge HVR-1110 (TDA18271 tuner) - workaround hack included
map = std_map-atv_dk; Simon, I've been chewing on this for a day or so and it reminded me partly why I stopped working on combined PAL/NTSC support for the saa7164 hardware family, it's been bugging me for a reason - now I understand why. Essentially, I had a long discussion with Mike Krufky about a year ago related to I/F's for analog TV output. The SAA7164 analog demod IF (as best as I can tell) are not configurable. I have no good set_if() interface I can call on the tuner to select a different I/F as the bridge driver needs. I was fairly unhappy about that. bah, such is life. The TDA18271 driver on linux DOES NOT use the same I/F's that the windows driver uses. Reason? Mike Decided to follow the data sheet and NOT use the Hauppauge specifically select IFs. His advise to me, at the time, which I think will work nicely for you and probably a better patch, is to have the HVR-1110 define a better I/F map for the atv_dk case. This way at least you would not pollute the 18271 driver in it's core and effect other DK users (potentially), instead, for the HVR1110 18271 attach, define the I/F maps for each country/modulation and simple change the DK version by your desired offset. That may be a cleaner fix and accepted for merge. (Note to self: Now that I recall the conversation with Mike I may actually go ahead and fix my saa7164 Pal issue.) -- Steven Toth - Kernel Labs http://www.kernellabs.com -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Problems tuning PAL-D with a Hauppauge HVR-1110 (TDA18271 tuner) - workaround hack included
Steven Toth st...@kernellabs.com wrote: map = std_map-atv_dk; Simon, I've been chewing on this for a day or so and it reminded me partly why I stopped working on combined PAL/NTSC support for the saa7164 hardware family, it's been bugging me for a reason - now I understand why. Essentially, I had a long discussion with Mike Krufky about a year ago related to I/F's for analog TV output. The SAA7164 analog demod IF (as best as I can tell) are not configurable. I have no good set_if() interface I can call on the tuner to select a different I/F as the bridge driver needs. I was fairly unhappy about that. bah, such is life. The TDA18271 driver on linux DOES NOT use the same I/F's that the windows driver uses. Reason? Mike Decided to follow the data sheet and NOT use the Hauppauge specifically select IFs. His advise to me, at the time, which I think will work nicely for you and probably a better patch, is to have the HVR-1110 define a better I/F map for the atv_dk case. This way at least you would not pollute the 18271 driver in it's core and effect other DK users (potentially), instead, for the HVR1110 18271 attach, define the I/F maps for each country/modulation and simple change the DK version by your desired offset. That may be a cleaner fix and accepted for merge. (Note to self: Now that I recall the conversation with Mike I may actually go ahead and fix my saa7164 Pal issue.) -- Steven Toth - Kernel Labs http://www.kernellabs.com -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Simon, If you have one of the latest HVR1600's with that analog tuner, does PAL-D work with it without and offset? Regards, Andy -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Problems tuning PAL-D with a Hauppauge HVR-1110 (TDA18271 tuner) - workaround hack included
Hi Simon,
On Wed, Sep 28, 2011 at 8:50 AM, Simon Farnsworth
simon.farnswo...@onelan.com wrote:
(note - the CC list is everyone over 50% certainty from get_maintainer.pl)
I'm having problems getting a Hauppauge HVR-1110 card to successfully
tune PAL-D at 85.250 MHz vision frequency; by experimentation, I've
determined that the tda18271 is tuning to a frequency 1.25 MHz lower
than the vision frequency I've requested, so the following workaround
fixes it for me.
diff --git a/drivers/media/common/tuners/tda18271-fe.c
b/drivers/media/common/tuners/tda18271-fe.c
index 63cc400..1a94e1a 100644
--- a/drivers/media/common/tuners/tda18271-fe.c
+++ b/drivers/media/common/tuners/tda18271-fe.c
@@ -1031,6 +1031,7 @@ static int tda18271_set_analog_params(struct
dvb_frontend *fe,
mode = I;
} else if (params-std V4L2_STD_DK) {
map = std_map-atv_dk;
+ freq += 125;
mode = DK;
} else if (params-std V4L2_STD_SECAM_L) {
map = std_map-atv_l;
I've checked with a signal analyser, and confirmed that my signal
generator is getting the spectrum right - I am seeing vision peaking
at 85.25 MHz, with one sideband going down to 84.5 MHz, and the other
going up to 90.5MHz. I also see an audio carrier at 91.75 MHz.
I'm going to run with this hack in place, but I'd appreciate it if
someone who knew more about the TDA18271 looked at this, and either
gave me a proper fix for testing, or confirmed that what I'm doing is
right.
Hi Simon,
This is interesting. I did some testing with an 18271 based device a
few months back (a Hauppauge cx231xx based tuner), and I believe
PAL-DK was working (although I did have unrelated issues with the DIF
configuration).
When you are doing the tuning request, are you explicitly stating
PAL-D in your calling application? Or are you passing PAL to the
V4L layer and expecting it to work with a PAL-D feed?
I'm not doubting your findings, and clearly you've done a good bit of
research/analysis, but I did want to raise it as a data point to
consider
Devin
--
Devin J. Heitmueller - Kernel Labs
http://www.kernellabs.com
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Problems tuning PAL-D with a Hauppauge HVR-1110 (TDA18271 tuner) - workaround hack included
On Wednesday 28 September 2011, Devin Heitmueller dheitmuel...@kernellabs.com wrote: Hi Simon, On Wed, Sep 28, 2011 at 8:50 AM, Simon Farnsworth simon.farnswo...@onelan.com wrote: I'm having problems getting a Hauppauge HVR-1110 card to successfully tune PAL-D at 85.250 MHz vision frequency; by experimentation, I've determined that the tda18271 is tuning to a frequency 1.25 MHz lower than the vision frequency I've requested, so the following workaround fixes it for me. I'm going to run with this hack in place, but I'd appreciate it if someone who knew more about the TDA18271 looked at this, and either gave me a proper fix for testing, or confirmed that what I'm doing is right. Hi Simon, This is interesting. I did some testing with an 18271 based device a few months back (a Hauppauge cx231xx based tuner), and I believe PAL-DK was working (although I did have unrelated issues with the DIF configuration). When you are doing the tuning request, are you explicitly stating PAL-D in your calling application? Or are you passing PAL to the V4L layer and expecting it to work with a PAL-D feed? I'm noticing this problem because I fixed a bug of ours, where we were passing PAL to the V4L2 layer, and expecting it to work (video did, at the correct frequency, but audio did not, as the TDA18271 chose PAL-B). Having fixed the bug, I was having to either adjust my signal generator down by 1.25MHz, or adjust the frequency I passed to V4L2 up by 1.25MHz to make PAL-D work. Hence the hack - I've confirmed that with the hack in place, I can get colour video from the signal if I use PAL-B or PAL-D, and sound if I use PAL-D. Without the hack, I need to change the frequency as I toggle between PAL-B and PAL-D, or I lose video. -- Simon Farnsworth Software Engineer ONELAN Limited http://www.onelan.com/ -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
