Advanced
Mailing List Archive

Mailing List Archive

  1. Home >
  2. ivtv>
  3. devel
tveeprom cannot autodetect tuner! (FQ1216LME MK5)
martin.dauskardt at gmx
May 21, 2009, 12:09 AM
Post #1 of 13 (7399 views)
Permalink
An owner of a PVR150 sent me the following dmesg:

[ 133.929892] ivtv: Start initialization, version 1.4.1
[ 133.929957] ivtv0: Initializing card 0
[ 133.929958] ivtv0: Autodetected Hauppauge card (cx23416 based)
[ 133.930478] ivtv 0000:04:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 133.983973] tveeprom 3-0050: Hauppauge model 26709, rev F0C1, serial#
9585403
[ 133.983975] tveeprom 3-0050: tuner model is Philips FQ1216LME MK5 (idx 121,
type 4)
[ 133.983977] tveeprom 3-0050: TV standards PAL(B/G) PAL(I) SECAM(L/L')
PAL(D/D1/K) (eeprom 0x74)
[ 133.983979] tveeprom 3-0050: audio processor is CX25843 (idx 37)
[ 133.983981] tveeprom 3-0050: decoder processor is CX25843 (idx 30)
[ 133.983982] tveeprom 3-0050: has no radio
[ 133.983984] ivtv0: Autodetected Hauppauge WinTV PVR-150
[ 133.983985] ivtv0: tveeprom cannot autodetect tuner!<6>cx25840 3-0044:
cx25843-24 found @ 0x88 (ivtv i2c driver #0)
[ 134.017173] tuner 3-0043: chip found @ 0x86 (ivtv i2c driver #0)
[ 134.017227] tda9887 3-0043: creating new instance
[ 134.017229] tda9887 3-0043: tda988[5/6/7] found
[ 134.027029] tuner 3-0061: chip found @ 0xc2 (ivtv i2c driver #0)
[ 134.034810] wm8775 3-001b: chip found @ 0x36 (ivtv i2c driver #0)
[ 134.043300] ivtv0: Registered device video0 for encoder MPG (4096 kB)
[ 134.043325] ivtv0: Registered device video32 for encoder YUV (2048 kB)
[ 134.043349] ivtv0: Registered device vbi0 for encoder VBI (1024 kB)
[ 134.043373] ivtv0: Registered device video24 for encoder PCM (320 kB)
[ 134.043375] ivtv0: Initialized card: Hauppauge WinTV PVR-150
[ 134.043389] ivtv: End initialization
[ 134.059301] ivtvfb: no cards found
[ 135.718015] ivtv 0000:04:00.0: firmware: requesting v4l-cx2341x-enc.fw
[ 135.737552] ivtv0: Loaded v4l-cx2341x-enc.fw firmware (376836 bytes)
[ 135.937153] ivtv0: Encoder revision: 0x02060039
[ 135.954204] cx25840 3-0044: firmware: requesting v4l-cx25840.fw
[ 139.419227] cx25840 3-0044: loaded v4l-cx25840.fw firmware (16382 bytes)
[ 139.601289] tuner 3-0061: tuner type not set
[ 139.641404] tuner 3-0061: tuner type not set
[ 139.828975] tuner 3-0061: tuner type not set

I never saw this. Detection of the tuner model is o.k., so why does
autodetection fail? What could be the problem?

I looked into tveeprom.c:

{ TUNER_ABSENT, "Philips FQ1216LME MK5"},

Does this mean the tuner is not supported? Should we try "modprobe ivtv
tuner=81" (this is the FQ1216LME MK3) ?


By the way: There is a small bug in ivtv-driver.c.
I think instead of

if (tv.tuner_type == TUNER_ABSENT)
IVTV_ERR("tveeprom cannot autodetect tuner!");

it should be

if (tv.tuner_type == TUNER_ABSENT)
IVTV_ERR("tveeprom cannot autodetect tuner!\n");

IVTV_ERR("Invalid EEPROM\n");

Greets,
Martin

_______________________________________________
ivtv-devel mailing list
ivtv-devel@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-devel
Re: tveeprom cannot autodetect tuner! (FQ1216LME MK5) [ In reply to ]
awalls at radix
May 21, 2009, 3:28 AM
Post #2 of 13 (7254 views)
Permalink
On Thu, 2009-05-21 at 09:09 +0200, Martin Dauskardt wrote:
> An owner of a PVR150 sent me the following dmesg:
>
> [ 133.929892] ivtv: Start initialization, version 1.4.1
> [ 133.929957] ivtv0: Initializing card 0
> [ 133.929958] ivtv0: Autodetected Hauppauge card (cx23416 based)
> [ 133.930478] ivtv 0000:04:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
> [ 133.983973] tveeprom 3-0050: Hauppauge model 26709, rev F0C1, serial#
> 9585403
> [ 133.983975] tveeprom 3-0050: tuner model is Philips FQ1216LME MK5 (idx 121,
> type 4)
> [ 133.983977] tveeprom 3-0050: TV standards PAL(B/G) PAL(I) SECAM(L/L')
> PAL(D/D1/K) (eeprom 0x74)
> [ 133.983979] tveeprom 3-0050: audio processor is CX25843 (idx 37)
> [ 133.983981] tveeprom 3-0050: decoder processor is CX25843 (idx 30)
> [ 133.983982] tveeprom 3-0050: has no radio
> [ 133.983984] ivtv0: Autodetected Hauppauge WinTV PVR-150
> [ 133.983985] ivtv0: tveeprom cannot autodetect tuner!<6>cx25840 3-0044:
> cx25843-24 found @ 0x88 (ivtv i2c driver #0)
> [ 134.017173] tuner 3-0043: chip found @ 0x86 (ivtv i2c driver #0)
> [ 134.017227] tda9887 3-0043: creating new instance
> [ 134.017229] tda9887 3-0043: tda988[5/6/7] found
> [ 134.027029] tuner 3-0061: chip found @ 0xc2 (ivtv i2c driver #0)
> [ 134.034810] wm8775 3-001b: chip found @ 0x36 (ivtv i2c driver #0)
> [ 134.043300] ivtv0: Registered device video0 for encoder MPG (4096 kB)
> [ 134.043325] ivtv0: Registered device video32 for encoder YUV (2048 kB)
> [ 134.043349] ivtv0: Registered device vbi0 for encoder VBI (1024 kB)
> [ 134.043373] ivtv0: Registered device video24 for encoder PCM (320 kB)
> [ 134.043375] ivtv0: Initialized card: Hauppauge WinTV PVR-150
> [ 134.043389] ivtv: End initialization
> [ 134.059301] ivtvfb: no cards found
> [ 135.718015] ivtv 0000:04:00.0: firmware: requesting v4l-cx2341x-enc.fw
> [ 135.737552] ivtv0: Loaded v4l-cx2341x-enc.fw firmware (376836 bytes)
> [ 135.937153] ivtv0: Encoder revision: 0x02060039
> [ 135.954204] cx25840 3-0044: firmware: requesting v4l-cx25840.fw
> [ 139.419227] cx25840 3-0044: loaded v4l-cx25840.fw firmware (16382 bytes)
> [ 139.601289] tuner 3-0061: tuner type not set
> [ 139.641404] tuner 3-0061: tuner type not set
> [ 139.828975] tuner 3-0061: tuner type not set
>
> I never saw this.

We just had an identical problem on the ivtv lists with an HVR-1600 and
a TCL MNM05-04 tuner with the cx18 driver.


> Detection of the tuner model is o.k., so why does
> autodetection fail?

tveeprom.c can identify it, but tveeprom.c doesn't know what parameters
to tell the ivtv driver. It returns TUNER_ABSENT instead.



> What could be the problem?
>
> I looked into tveeprom.c:
>
> { TUNER_ABSENT, "Philips FQ1216LME MK5"},

This is the problem.


> Does this mean the tuner is not supported? Should we try "modprobe ivtv
> tuner=81" (this is the FQ1216LME MK3) ?

Yes. If 81 is the the FQ1216LME MK3, then this will likely work. Let
me know how the reception is, and I can get the entry changed in
tveeprom.c.



> By the way: There is a small bug in ivtv-driver.c.
> I think instead of
>
> if (tv.tuner_type == TUNER_ABSENT)
> IVTV_ERR("tveeprom cannot autodetect tuner!");
>
> it should be
>
> if (tv.tuner_type == TUNER_ABSENT)
> IVTV_ERR("tveeprom cannot autodetect tuner!\n");
>
> IVTV_ERR("Invalid EEPROM\n");

Yes. I just fixed this bug in the cx18 driver a week or so ago.

Regards,
Andy

> Greets,
> Martin



_______________________________________________
ivtv-devel mailing list
ivtv-devel@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-devel
Re: tveeprom cannot autodetect tuner! (FQ1216LME MK5) [ In reply to ]
martin.dauskardt at gmx
May 21, 2009, 3:56 AM
Post #3 of 13 (7243 views)
Permalink
>IVTV_ERR("Invalid EEPROM\n");
ups, I forgot to delete this. Was just an example copied from another place...

_______________________________________________
ivtv-devel mailing list
ivtv-devel@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-devel
Re: tveeprom cannot autodetect tuner! (FQ1216LME MK5) [ In reply to ]
awalls at radix
May 22, 2009, 5:31 PM
Post #4 of 13 (7229 views)
Permalink
On Thu, 2009-05-21 at 06:28 -0400, Andy Walls wrote:
> On Thu, 2009-05-21 at 09:09 +0200, Martin Dauskardt wrote:
> > An owner of a PVR150 sent me the following dmesg:
> >
> > [ 133.929892] ivtv: Start initialization, version 1.4.1
> > [ 133.929957] ivtv0: Initializing card 0
> > [ 133.929958] ivtv0: Autodetected Hauppauge card (cx23416 based)
> > [ 133.930478] ivtv 0000:04:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
> > [ 133.983973] tveeprom 3-0050: Hauppauge model 26709, rev F0C1, serial#
> > 9585403
> > [ 133.983975] tveeprom 3-0050: tuner model is Philips FQ1216LME MK5 (idx 121,
> > type 4)
> > [ 133.983977] tveeprom 3-0050: TV standards PAL(B/G) PAL(I) SECAM(L/L')
> > PAL(D/D1/K) (eeprom 0x74)
> > [ 133.983979] tveeprom 3-0050: audio processor is CX25843 (idx 37)
> > [ 133.983981] tveeprom 3-0050: decoder processor is CX25843 (idx 30)
> > [ 133.983982] tveeprom 3-0050: has no radio
> > [ 133.983984] ivtv0: Autodetected Hauppauge WinTV PVR-150
> > [ 133.983985] ivtv0: tveeprom cannot autodetect tuner!<6>cx25840 3-0044:
> > cx25843-24 found @ 0x88 (ivtv i2c driver #0)
> > [ 134.017173] tuner 3-0043: chip found @ 0x86 (ivtv i2c driver #0)
> > [ 134.017227] tda9887 3-0043: creating new instance
> > [ 134.017229] tda9887 3-0043: tda988[5/6/7] found
> > [ 134.027029] tuner 3-0061: chip found @ 0xc2 (ivtv i2c driver #0)
> > [ 134.034810] wm8775 3-001b: chip found @ 0x36 (ivtv i2c driver #0)
> > [ 134.043300] ivtv0: Registered device video0 for encoder MPG (4096 kB)
> > [ 134.043325] ivtv0: Registered device video32 for encoder YUV (2048 kB)
> > [ 134.043349] ivtv0: Registered device vbi0 for encoder VBI (1024 kB)
> > [ 134.043373] ivtv0: Registered device video24 for encoder PCM (320 kB)
> > [ 134.043375] ivtv0: Initialized card: Hauppauge WinTV PVR-150
> > [ 134.043389] ivtv: End initialization
> > [ 134.059301] ivtvfb: no cards found
> > [ 135.718015] ivtv 0000:04:00.0: firmware: requesting v4l-cx2341x-enc.fw
> > [ 135.737552] ivtv0: Loaded v4l-cx2341x-enc.fw firmware (376836 bytes)
> > [ 135.937153] ivtv0: Encoder revision: 0x02060039
> > [ 135.954204] cx25840 3-0044: firmware: requesting v4l-cx25840.fw
> > [ 139.419227] cx25840 3-0044: loaded v4l-cx25840.fw firmware (16382 bytes)
> > [ 139.601289] tuner 3-0061: tuner type not set
> > [ 139.641404] tuner 3-0061: tuner type not set
> > [ 139.828975] tuner 3-0061: tuner type not set
> >
> > I never saw this.
>
> We just had an identical problem on the ivtv lists with an HVR-1600 and
> a TCL MNM05-04 tuner with the cx18 driver.
>
>
> > Detection of the tuner model is o.k., so why does
> > autodetection fail?
>
> tveeprom.c can identify it, but tveeprom.c doesn't know what parameters
> to tell the ivtv driver. It returns TUNER_ABSENT instead.
>
>
>
> > What could be the problem?
> >
> > I looked into tveeprom.c:
> >
> > { TUNER_ABSENT, "Philips FQ1216LME MK5"},
>
> This is the problem.
>
>
> > Does this mean the tuner is not supported? Should we try "modprobe ivtv
> > tuner=81" (this is the FQ1216LME MK3) ?
>
> Yes. If 81 is the the FQ1216LME MK3, then this will likely work. Let
> me know how the reception is, and I can get the entry changed in
> tveeprom.c.

Martin,

I don't see tuner type 81 in the list in tuners.h. I do see:


#define TUNER_PHILIPS_FQ1216ME 24 /* you must actively select B/G/D/K, I, L, L` */
#define TUNER_PHILIPS_FQ1216AME_MK4 56 /* Hauppauge PVR-150 PAL */

#define TUNER_PHILIPS_FM1216ME_MK3 38

#define TUNER_PHILIPS_FMD1216ME_MK3 63
#define TUNER_PHILIPS_FMD1216MEX_MK3 78
#define TUNER_PHILIPS_FM1216MK5 79

Could the user try one of those, starting with the FQ1216 tuner numbers
(24 and 56), to see if one of them works? For the FQ1261LME MK3,
tveeprom has the FM1216ME_MK3 tuner number (38).


>
>
> > By the way: There is a small bug in ivtv-driver.c.
> > I think instead of
> >
> > if (tv.tuner_type == TUNER_ABSENT)
> > IVTV_ERR("tveeprom cannot autodetect tuner!");
> >
> > it should be
> >
> > if (tv.tuner_type == TUNER_ABSENT)
> > IVTV_ERR("tveeprom cannot autodetect tuner!\n");

I'll commit a fix for this. I'm just waiting on which tuner # works
best for the user with the problem.

Regards,
Andy

> > Greets,
> > Martin



_______________________________________________
ivtv-devel mailing list
ivtv-devel@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-devel
Re: tveeprom cannot autodetect tuner! (FQ1216LME MK5) [ In reply to ]
martin.dauskardt at gmx
May 23, 2009, 12:27 AM
Post #5 of 13 (7232 views)
Permalink
Hi Andy,

> Martin,
>
> I don't see tuner type 81 in the list in tuners.h.  I do see:
>
>
> #define TUNER_PHILIPS_FQ1216ME          24      /* you must actively select
B/G/D/K, I, L, L` */
> #define TUNER_PHILIPS_FQ1216AME_MK4     56      /* Hauppauge PVR-150 PAL */
>
> #define TUNER_PHILIPS_FM1216ME_MK3      38
>
> #define TUNER_PHILIPS_FMD1216ME_MK3     63
> #define TUNER_PHILIPS_FMD1216MEX_MK3    78
> #define TUNER_PHILIPS_FM1216MK5         79

ah, sorry. I looked into hauppauge_tuner[] from tveeprom.c and also misread
the internal number 80 as 81:

/* 80-89 */
{ TUNER_PHILIPS_FM1216ME_MK3, "Philips FQ1216LME MK3"},

>
> Could the user try one of those, starting with the FQ1216 tuner numbers
> (24 and 56), to see if one of them works?  For the FQ1261LME MK3,
> tveeprom has the FM1216ME_MK3 tuner number (38).

I hope to get in contact with him this weekend. There is another problems with
the application which must be solved before, but I am sure we will found out
the right tuner type at the end.

Greets,
Martin

_______________________________________________
ivtv-devel mailing list
ivtv-devel@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-devel
Re: tveeprom cannot autodetect tuner! (FQ1216LME MK5) [ In reply to ]
martin.dauskardt at gmx
May 25, 2009, 12:34 PM
Post #6 of 13 (7167 views)
Permalink
> #define TUNER_PHILIPS_FQ1216ME 24 /* you must actively select
B/G/D/K, I, L, L` */
> #define TUNER_PHILIPS_FQ1216AME_MK4 56 /* Hauppauge PVR-150 PAL */
>
> #define TUNER_PHILIPS_FM1216ME_MK3 38
>
> #define TUNER_PHILIPS_FMD1216ME_MK3 63
> #define TUNER_PHILIPS_FMD1216MEX_MK3 78
> #define TUNER_PHILIPS_FM1216MK5 79
>
> Could the user try one of those, starting with the FQ1216 tuner numbers
> (24 and 56), to see if one of them works? For the FQ1261LME MK3,
> tveeprom has the FM1216ME_MK3 tuner number (38).
>

I have this card now at home for testing. First results:

#define TUNER_PHILIPS_FQ1216ME 24 /* you must actively select B/G/D/K, I, L,
Result: only static

#define TUNER_PHILIPS_FM1216ME_MK3 38
result: picture + sound o.k.

#define TUNER_PHILIPS_FQ1216AME_MK4 56 /* Hauppauge PVR-150 PAL */
result: picture o.k., but no sound

#define TUNER_PHILIPS_FMD1216ME_MK3 63
result: picture + sound o.k.

#define TUNER_PHILIPS_FMD1216MEX_MK3 78
result: picture + sound o.k.

#define TUNER_PHILIPS_FM1216MK5 79
result: picture o.k. , but audio disappears every few seconds (for about 1-2
seconds, then comes back)

tuner type 63 and 79 are Hybrid tuners. This is fore sure an analogue-only
tuner. The sticker says "Multi-PAL", and according to VIDIOC_ENUMSTD it
supports PAL, PAL-BG and PAL-H.

So I think 38 is right. Any suggestions for further tests?

_______________________________________________
ivtv-devel mailing list
ivtv-devel@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-devel
Re: tveeprom cannot autodetect tuner! (FQ1216LME MK5) [ In reply to ]
martin.dauskardt at gmx
May 25, 2009, 1:04 PM
Post #7 of 13 (7154 views)
Permalink
Am Montag, 25. Mai 2009 21:34:43 schrieb Martin Dauskardt:

> #define TUNER_PHILIPS_FM1216MK5 79
> result: picture o.k. , but audio disappears every few seconds (for about 1-2
> seconds, then comes back)

correction: This is not a problem of tuner type 79. It happens also with tuner
type 38. Sometimes the audio is also muted after the start of the
application. Only switching to another input and back brings the audio back.

I am beginning to wonder if this problem may be related to a similar problem
with the PVRUSB2:
http://www.isely.net/pipermail/pvrusb2/2009-May/002331.html

If there is a problem with the new v4l2 sub-device mechanism, it seems to be
more specific to some devices than to others. With my PVR350 I didn't notice
such problems - although I remember that in **very** rare cases the audio
fails after a channel switch.

Greets,
Martin


_______________________________________________
ivtv-devel mailing list
ivtv-devel@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-devel
Re: tveeprom cannot autodetect tuner! (FQ1216LME MK5) [ In reply to ]
martin.dauskardt at gmx
May 26, 2009, 1:21 PM
Post #8 of 13 (7152 views)
Permalink
I should add that the picture quality is with all tested tuner types worse
than with my PVR250/350. I don't know if a PVR150 is in generally worse than
a PVR250. I can't call it really noisy, but in german I would say the picture
is a little bit "grobkörnig". It really needs a temporal filter setting of
value 8 or more, while my other PVR cards have a nice quality even with value
0.

I will test whatever you guys want me to test :-) But I am not a programmer,
so I need detailled instructions what to patch.

My next step will be testing an older v4l2 with an 2.6.27 kernel to see if the
audio problem still exists.

_______________________________________________
ivtv-devel mailing list
ivtv-devel@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-devel
Re: tveeprom cannot autodetect tuner! (FQ1216LME MK5) [ In reply to ]
awalls at radix
May 26, 2009, 6:38 PM
Post #9 of 13 (7134 views)
Permalink
Hi Martin,

For some reason, I'm not getting any of your replies to the lists. (I'm
getting Hermann's posts though)


On Mon, 2009-05-25 at 23:45 +0200, hermann pitton wrote:
> Hi,
>
> Am Montag, den 25.05.2009, 21:34 +0200 schrieb Martin Dauskardt:
> > > #define TUNER_PHILIPS_FQ1216ME 24 /* you must actively select
> > B/G/D/K, I, L, L` */
> > > #define TUNER_PHILIPS_FQ1216AME_MK4 56 /* Hauppauge PVR-150 PAL */
> > >
> > > #define TUNER_PHILIPS_FM1216ME_MK3 38
> > >
> > > #define TUNER_PHILIPS_FMD1216ME_MK3 63
> > > #define TUNER_PHILIPS_FMD1216MEX_MK3 78
> > > #define TUNER_PHILIPS_FM1216MK5 79
> > >
> > > Could the user try one of those, starting with the FQ1216 tuner numbers
> > > (24 and 56), to see if one of them works? For the FQ1261LME MK3,
> > > tveeprom has the FM1216ME_MK3 tuner number (38).
> > >
> >
> > I have this card now at home for testing. First results:
> >
> > #define TUNER_PHILIPS_FQ1216ME 24 /* you must actively select B/G/D/K, I, L,
> > Result: only static
> >
> > #define TUNER_PHILIPS_FM1216ME_MK3 38
> > result: picture + sound o.k.
> >
> > #define TUNER_PHILIPS_FQ1216AME_MK4 56 /* Hauppauge PVR-150 PAL */
> > result: picture o.k., but no sound
> >
> > #define TUNER_PHILIPS_FMD1216ME_MK3 63
> > result: picture + sound o.k.
> >
> > #define TUNER_PHILIPS_FMD1216MEX_MK3 78
> > result: picture + sound o.k.
> >
> > #define TUNER_PHILIPS_FM1216MK5 79
> > result: picture o.k. , but audio disappears every few seconds (for about 1-2
> > seconds, then comes back)
> >
> > tuner type 63 and 79 are Hybrid tuners. This is fore sure an analogue-only
> > tuner. The sticker says "Multi-PAL", and according to VIDIOC_ENUMSTD it
> > supports PAL, PAL-BG and PAL-H.

Yes, the hybrid tuners defintions obviously aren't right. Sorry I
missed that with my initial suggestions. I'm not sure that I would
believe what VIDIOC_ENUMSTD reports without a proper tuner definition (I
haven't looked up the details on what the ioctl actually does though).


> > So I think 38 is right. Any suggestions for further tests?

When you don't specifiy a tuner number at all, does the driver loading
detect a tda988x chip?

With tuner type 24, does setting the video standard explicitly with

v4l2-ctl -s pal-B

or something similar help?


Anyway, it looks like Hermann has already got a better idea of what the
tuner definition might be. (I haven't been keeping up with the
conversation. If you and Hermann can figure out something faster,
off-list using German, I won't be offended by being left out of the
conversation.)

Regards,
Andy


> in my opinion the entry of tuner type 24 is buggy.
> I posted once about it, but it is long ago.
>
> /* ------------ TUNER_PHILIPS_FQ1216ME - Philips PAL ------------ */
>
> static struct tuner_params tuner_philips_fq1216me_params[] = {
> {
> .type = TUNER_PARAM_TYPE_PAL,
> .ranges = tuner_lg_pal_ranges,
> .count = ARRAY_SIZE(tuner_lg_pal_ranges),
> .has_tda9887 = 1,
> .port1_active = 1,
> .port2_active = 1,
> .port2_invert_for_secam_lc = 1,
> },
> };
>
> At least tuner_lg_pal_ranges must be wrong for an MK3 and UHF should
> fail, if you can test on that. Switch must be 0x04 and not 0x08.
>
> The hybrid tuners are also not compatible to an FM1216ME/I MK3.
> They miss some frequencies when used for such an one and some low VHF
> channels are snowy. The tda9887 is also not visible on them without
> special initialization in tuner-core.c for them. Likely not the case on
> yours.
>
> FQ types from Philips are without radio support. FM types have radio.
> Also the FMD1216MEX_MK3 has a different radio IF, BTW.
>
> Previously I did recommend tuner 56 for them, but now with the more
> detailed tda988/5/6/7 settings it misses .port2_active = 1.
> Hans likely knows that it is right and else we would have reports from
> people using it I guess. Hm.
>
> You could test with tda9887 port2=0, if you get sound on that one too.
>
> If the entry is correct and can't be changed, we likely need a new tuner
> entry or the TUNER_PHILIPS_FQ1216ME must use mk3 ranges on UHF. But on
> that one I have some doubts at all. How could it happen, given how old
> it is and previously without tda9887 at all, that the wrong UHF switch
> is undiscovered until today?
>
> Hm, the new MK5 has trouble with sound, FM anyway, but
> TUNER_PHILIPS_FM1216MK5 is a complete clone of the FM1216ME MK3,
> except for the discussed 1MHz change for UHF beginning and 0xce versus
> 0x8e. IIRC, 0xce should be even the better choice on tuners without
> radio, but I need to look it up again or Andy is more aware about the
> recent discussions. (faster tuning bit)
>
> Maybe Dmitry has a datasheet for that one too.
>
> One question, which might be interesting is the RF loop through.
> Is it enabled by default or even switchable?
>
> The latter would be reason enough to create a new tuner type I think.
>
> Just some quick ideas. (ivtv will bounce me, not subscribed)
>
> Cheers,
> Hermann



_______________________________________________
ivtv-devel mailing list
ivtv-devel@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-devel
Re: tveeprom cannot autodetect tuner! (FQ1216LME MK5) [ In reply to ]
awalls at radix
May 26, 2009, 7:03 PM
Post #10 of 13 (7141 views)
Permalink
On Wed, 2009-05-27 at 02:15 +0200, hermann pitton wrote:
> Hi,
>
> Am Dienstag, den 26.05.2009, 22:21 +0200 schrieb Martin Dauskardt:
> > I should add that the picture quality is with all tested tuner types worse
> > than with my PVR250/350. I don't know if a PVR150 is in generally worse than
> > a PVR250. I can't call it really noisy, but in german I would say the picture
> > is a little bit "grobkörnig". It really needs a temporal filter setting of
> > value 8 or more, while my other PVR cards have a nice quality even with value
> > 0.
> >
> > I will test whatever you guys want me to test :-) But I am not a programmer,
> > so I need detailled instructions what to patch.
> >
> > My next step will be testing an older v4l2 with an 2.6.27 kernel to see if the
> > audio problem still exists.
>
> Martin, that seems the right way to start and there is no need to hurry.
>
> If nobody has a datasheet, and I can imagine that such an early RF loop
> through tuner has some specials, you are still in a difficult testing
> field, even if only on PAL BG for now. Is RF out is active would be
> still interesting to know.

Hermann,

There is an FQ1216LME MK3 data sheet here:

http://dl.ivtvdriver.org/datasheets/tuners/FQ1216LME%20Mk3.pdf

Is it safe to assume that the MK5 is not very different from the MK3?

I can build an entry for the FQ1216LME based on this datasheet (maybe on
Friday night) and hope it works well enough for the MK5.

Regards,
Andy

> If on the same RF signal quality, means no more passive RF splitter in
> between, I don't know what we can expect, but for example the FM1216ME
> and the FMD1216ME hybrid MK3s do perform excellent and don't have this
> "grobkörnige" (grainy?) picture, which you often see on cheaper tuners.
>
> As far as I know, not any such complaints about the MK4s so far too.
>
> Dmitry has some MK3 variant, where the first time on a Philips tuner
> Chinese SAW filters are employed instead of the original EPCOS filters.
>
> The question, if that could cause performance/sensitivity losses, is not
> yet answered. Also if this is related to the SECAM DK tweaks he needs.
>
> I would start testing for different sound quality between tuner 56 and
> 38. Beginning silence on old B/W mono broadcasts could make a difference
> I somehow have in mind.
>
> If 56 still has no sound at all, that should indicate a major technical
> change compared to prior tuners.
>
> Cheers,
> Hermann
>
>


_______________________________________________
ivtv-devel mailing list
ivtv-devel@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-devel
Re: tveeprom cannot autodetect tuner! (FQ1216LME MK5) [ In reply to ]
ant at symons
May 26, 2009, 8:28 PM
Post #11 of 13 (7129 views)
Permalink
Andy Walls wrote:
> Hermann,
>
> There is an FQ1216LME MK3 data sheet here:
>
> http://dl.ivtvdriver.org/datasheets/tuners/FQ1216LME%20Mk3.pdf
>
> Is it safe to assume that the MK5 is not very different from the MK3?
>
I am no expert on the subject, but I found this reference to the MK3 vs MK5:

http://www.nxp.com/acrobat_download/other/products/rf/fq_mk5.pdf

Where it says

"The FQ1200 MK5 family is identical in footprint to the
FQ1200 MK3 series, ensuring a quick drop-in replacement."

If the MK5 family is designed as a drop in replacement for the MK3
family, I would think there is a good chance it functions exactly the same.

Anthony



_______________________________________________
ivtv-devel mailing list
ivtv-devel@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-devel
Re: tveeprom cannot autodetect tuner! (FQ1216LME MK5) [ In reply to ]
hverkuil at xs4all
May 26, 2009, 10:59 PM
Post #12 of 13 (7132 views)
Permalink
On Tuesday 26 May 2009 22:21:31 Martin Dauskardt wrote:
> I should add that the picture quality is with all tested tuner types
> worse than with my PVR250/350. I don't know if a PVR150 is in generally
> worse than a PVR250. I can't call it really noisy, but in german I would
> say the picture is a little bit "grobkörnig". It really needs a temporal
> filter setting of value 8 or more, while my other PVR cards have a nice
> quality even with value 0.

It's always been my impression that the saa7115/msp3400 combo is superior to
the cx2584x. I can't prove it, but the PVR150 picture quality is never as
sharp as what I get with my PVR350.

Regards,

Hans

> I will test whatever you guys want me to test :-) But I am not a
> programmer, so I need detailled instructions what to patch.
>
> My next step will be testing an older v4l2 with an 2.6.27 kernel to see
> if the audio problem still exists.



--
Hans Verkuil - video4linux developer - sponsored by TANDBERG Telecom

_______________________________________________
ivtv-devel mailing list
ivtv-devel@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-devel
Re: tveeprom cannot autodetect tuner! (FQ1216LME MK5) [ In reply to ]
hverkuil at xs4all
May 26, 2009, 11:09 PM
Post #13 of 13 (7136 views)
Permalink
On Wednesday 27 May 2009 05:28:19 Ant wrote:
> Andy Walls wrote:
> > Hermann,
> >
> > There is an FQ1216LME MK3 data sheet here:
> >
> > http://dl.ivtvdriver.org/datasheets/tuners/FQ1216LME%20Mk3.pdf
> >
> > Is it safe to assume that the MK5 is not very different from the MK3?
>
> I am no expert on the subject, but I found this reference to the MK3 vs
> MK5:
>
> http://www.nxp.com/acrobat_download/other/products/rf/fq_mk5.pdf
>
> Where it says
>
> "The FQ1200 MK5 family is identical in footprint to the
> FQ1200 MK3 series, ensuring a quick drop-in replacement."
>
> If the MK5 family is designed as a drop in replacement for the MK3
> family, I would think there is a good chance it functions exactly the
> same.
>
> Anthony

And in addition I have the datasheets for the FM1216ME_MK3, FM1216ME_MK5 and
FQ1236MK5. All combined should give enough information to deduce what if
any the changes are between the FQ1216LME MK3 and MK5.

Please mail me who wants these datasheets and I'll send them to you.

Regards,

Hans

--
Hans Verkuil - video4linux developer - sponsored by TANDBERG Telecom

_______________________________________________
ivtv-devel mailing list
ivtv-devel@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-devel

©2024 GT.net. A Gossamer Threads company.
5th Floor, 455 Granville St., Vancouver, BC V6C 1T1, Canada | Legal