Several modern tuners use tda9887 to help IF demodulation. Some require
special settings for tda9887, according with frequency range. I've
developed a patch at December (never applied at master), merging tda9887
into tuners. This will allow future patches to benefit of such merges.
This patch is already known to work on pvrusb2, em28xx, ivtv and cx88
drivers (at least with some boards). It should work with all tda9887
based boards.
We need volunteers to test it. There's a mercurial tree for this at:
http://linuxtv.org/hg/~mchehab/tda9887
It is basically master v4l-dvb tree + tda9887 patch. Please test it and
report us if this is working. For testing it, you should first remove
tda9887.ko module from your kernel. For this to happen, you should run:
hg clone http://linuxtv.org/hg/~mchehab/tda9887
cd tda9887
make allyesconfig
and, as root:
rm /lib/modules/`uname -r`/
rmmod tda9887
make install
make rmmod
insmod tuner debug=1
After this, just modprobe your board (or, instead, make insmod).
If all are ok, you should notice after probing the board, something like
(for boards with tda9887):
tuner 2-0043: chip found @ 0x86 (ivtv i2c driver #0)
tda9887 2-0043 (tda9887): tda988[5/6/7] found @ 0x43 (tuner)
And, after calling a tv app, something like
tda9887 2-0043 (tda9887): configure for: PAL-M/Nc
tda9887 2-0043 (tda9887): writing: b=0xd4 c=0x30 e=0x44
Cheers,
Mauro.

Harmlessly tested : module compilation and module loading.

I can't say more because as long I can't unhide i2c devices @ 0x86
address, I now things won't work.

Mauro Carvalho Chehab wrote:
Several modern tuners use tda9887 to help IF demodulation. Some require
special settings for tda9887, according with frequency range. I've
developed a patch at December (never applied at master), merging tda9887
into tuners. This will allow future patches to benefit of such merges.

Am Mittwoch, den 14.06.2006, 14:24 -0300 schrieb Mauro Carvalho Chehab:
Several modern tuners use tda9887 to help IF demodulation. Some require
special settings for tda9887, according with frequency range. I've
developed a patch at December (never applied at master), merging tda9887
into tuners. This will allow future patches to benefit of such merges.

This patch is already known to work on pvrusb2, em28xx, ivtv and cx88
drivers (at least with some boards). It should work with all tda9887
based boards.

We need volunteers to test it. There's a mercurial tree for this at:

http://linuxtv.org/hg/~mchehab/tda9887

It is basically master v4l-dvb tree + tda9887 patch. Please test it and
report us if this is working. For testing it, you should first remove
tda9887.ko module from your kernel. For this to happen, you should run:

hg clone http://linuxtv.org/hg/~mchehab/tda9887
cd tda9887
make allyesconfig

and, as root:

rm /lib/modules/`uname -r`/
rmmod tda9887
make install
make rmmod

insmod tuner debug=1

After this, just modprobe your board (or, instead, make insmod).

If all are ok, you should notice after probing the board, something like
(for boards with tda9887):

tuner 2-0043: chip found @ 0x86 (ivtv i2c driver #0)
tda9887 2-0043 (tda9887): tda988[5/6/7] found @ 0x43 (tuner)

And, after calling a tv app, something like

tda9887 2-0043 (tda9887): configure for: PAL-M/Nc
tda9887 2-0043 (tda9887): writing: b=0xd4 c=0x30 e=0x44

Mauro,

cool, this time it is indeed working on the saa7134 too!

Folks please test, especially with hybrid devices like Pinnacle 300i,
md7134 with FMD1216ME and similar, also the ATSC tuners.

Mauro needs feedback for those tda9885/6/7 bttv cards too.

Cheers,
Hermann

Hi, Mauro

Mauro Carvalho Chehab wrote:
Several modern tuners use tda9887 to help IF demodulation. Some require
special settings for tda9887, according with frequency range. I've
developed a patch at December (never applied at master), merging tda9887
into tuners. This will allow future patches to benefit of such merges.

This patch is already known to work on pvrusb2, em28xx, ivtv and cx88
drivers (at least with some boards). It should work with all tda9887
based boards.

We need volunteers to test it. There's a mercurial tree for this at:

http://linuxtv.org/hg/~mchehab/tda9887

It is basically master v4l-dvb tree + tda9887 patch. Please test it and
report us if this is working. For testing it, you should first remove
tda9887.ko module from your kernel. For this to happen, you should run:

<snip>
I just tested with 2 hybrid cardbus modules:

MD7134 hybrid (card 12)
SAA7134
FMD1216ME (tuner 63)
TDA9886
TDA10046

And (for compatibility)
ADS Tech PTV331 (Card 87, new Lifeview Design)
SAA7133
TDA8290
TDA8275A
TDA10046

Both work, analog and digital, no unexpected messages.
Please note that i could only test PAL-G from a VCR.
There seems to be no probing issue with TDA8290 which resides at the
same addres range.

Looks like you did a great job!

Hartmut

Hallo!

Does this concern the usbvision saa711x/saa7115 as well? I have a "Hauppauge
WinTV USB device Model 40219 Rev E189". Some told me I would need tda9887
others told me I should not modprobe it. If I do, I get some messages in the
syslog that sound promising but except for some beep there is not more than
without tda9887. When tda9887 is loaded the tuner module doesn't say anything
anymore even with debug enabled. Without the tda9887 the tuner has this
concern:
Jun 15 23:47:02 drago kernel: tuner 0-0060: i2c i/o error: rc == -121 (should
be 4)

Anyway I did as told in your insturction but neither the saa's nor the
tuner.ko get changed in the kernellibs. Is that right? I have to use modprobe
tuner debug=1 instead of insmod (which would need a full path), does that
matter in any way?

So like nearly a year I don't get anything out of my device. Any help or hint
is still apreciated. (messages attached)

Lynx

Em Qui, 2006-06-15 23:35 +0200, Hartmut Hackmann escreveu:
Hi, Mauro

I just tested with 2 hybrid cardbus modules:

MD7134 hybrid (card 12)
SAA7134
FMD1216ME (tuner 63)
TDA9886
TDA10046

And (for compatibility)
ADS Tech PTV331 (Card 87, new Lifeview Design)
SAA7133
TDA8290
TDA8275A
TDA10046

Both work, analog and digital, no unexpected messages.
Please note that i could only test PAL-G from a VCR.
Great!
There seems to be no probing issue with TDA8290 which resides at the
same addres range.
After the patch, tda8290 is being probed first. Nice to see that it is
ok!

Looks like you did a great job!
Thanks.

Hartmut

Em Qui, 2006-06-15 18:10 +0200, hermann pitton escreveu:
Am Mittwoch, den 14.06.2006, 14:24 -0300 schrieb Mauro Carvalho Chehab:

Mauro,

cool, this time it is indeed working on the saa7134 too!
Nice! So, it is known to work with cx88, saa7134, pvrusb2, ivtv and
em28xx. No tests yet with bttv.

Folks please test, especially with hybrid devices like Pinnacle 300i,
md7134 with FMD1216ME and similar, also the ATSC tuners.
Yes. Hybrid devices may have an additional complexity due the need to
initialize i2c bridges. It may require additional work, if tda9887 is
available only after some output at a tuner at 0x60 (7bit) address.

Mauro needs feedback for those tda9885/6/7 bttv cards too.

Cheers,
Hermann

Em Sex, 2006-06-16 00:10 +0200, lynx.abraxas (AT) freenet (DOT) de escreveu:
Hallo!

Does this concern the usbvision saa711x/saa7115 as well? I have a "Hauppauge
WinTV USB device Model 40219 Rev E189". Some told me I would need tda9887
others told me I should not modprobe it.
I'm not sure about the configuration for this device. The answer is
related to what tuner you have. non-usbvision devices, there is a
module (tveeprom) that reads Hauppauge eeprom content and detects what
tuner you have. I'm not sure if this will work with usbvision.

Do you know what tuner is there ? Tuner is that metallic can inside the
board.
If I do, I get some messages in the
syslog that sound promising but except for some beep there is not more than
without tda9887. When tda9887 is loaded the tuner module doesn't say anything
anymore even with debug enabled.
master V4L/DVB tree, tda9887 have a separate debug option, when you
load tda9887. After the patch, the tuner debug option will also activate
debug at tda9887., if detected.
Without the tda9887 the tuner has this
concern:
Jun 15 23:47:02 drago kernel: tuner 0-0060: i2c i/o error: rc == -121 (should
be 4)
rc<0 means error I2C couldn't communicate with your tuner.

With tda9887, you should see also a "tuner 0-0043:" msg (it may be also
0042, 004a or 004b, depending on what address tda9887 is configured).

Anyway I did as told in your insturction but neither the saa's nor the
tuner.ko get changed in the kernellibs. Is that right?
No. tuner.ko should be replaced by a newer version. At the procedure
I've described, you need to manually remove the old tda9887.ko module.
Then, make install will replace tuner.ko by the newer one.
If this is not happening, you may try first:
make distclean, to clean all stuff, including .version file

I have to use modprobe
tuner debug=1 instead of insmod (which would need a full path), does that
matter in any way?
modprobe will work fine, after you run make install (since it will read
the newly installed one).
You may, instead, run, after making all modules:

/scripts/rmmod.pl debug
(from v4l dir)

This will load all modules, and will pass (1) to tuner debug var.

So like nearly a year I don't get anything out of my device. Any help or hint
is still apreciated. (messages attached)

Lynx

Em Qui, 2006-06-15 07:32 +0200, Eric Thomas escreveu:
Harmlessly tested : module compilation and module loading.

I can't say more because as long I can't unhide i2c devices @ 0x86
address, I now things won't work.

Hmm are you meaning that, before it were working and now it stopped?

Cheers,
Mauro.

Hi,

Am Freitag, den 16.06.2006, 13:00 -0300 schrieb Mauro Carvalho Chehab:
Em Sex, 2006-06-16 *s 00:10 +0200, lynx.abraxas (AT) freenet (DOT) de escreveu:
Hallo!

Does this concern the usbvision saa711x/saa7115 as well? I have a "Hauppauge
WinTV USB device Model 40219 Rev E189". Some told me I would need tda9887
others told me I should not modprobe it.
I'm not sure about the configuration for this device. The answer is
related to what tuner you have. non-usbvision devices, there is a
module (tveeprom) that reads Hauppauge eeprom content and detects what
tuner you have. I'm not sure if this will work with usbvision.

Do you know what tuner is there ? Tuner is that metallic can inside the
board.

just some links.

We tried already once here. the pll chip at supposed 0x60 absolutely
nothing, but the tda9887 was fully responsive.

and some next.

The tuner is idx 89 TCL-MFPE05-2 in tveeprom.c, we got it working
immediately after Graham Lee Bevan (UK) introduced it here on a WinTV
cx88 Hauppauge card. The compatibility to FM1216ME MK3 tuner=38 was also
kindly confirmed by a Hauppauge support request.

No other complaints since then. Here the TCL site.

Michel Bardiaux found later a MPE05-2 model without radio on a bttv
WinTV-Express 44809/E1A5, we got it quickly working too.

Cheers,
Hermann

Mauro Carvalho Chehab wrote:
Em Qui, 2006-06-15 07:32 +0200, Eric Thomas escreveu:

>>Harmlessly tested : module compilation and module loading.
>>
>>I can't say more because as long I can't unhide i2c devices @ 0x86
>>address, I now things won't work.

Hmm are you meaning that, before it were working and now it stopped?

Not exactly. Don't worry.
I just hoped that it might help with my i2c problem. But it's not related.

Eric

16/06/06 13:00:43, Mauro Carvalho Chehab wrote:
Em Sex, 2006-06-16 ?s 00:10 +0200, lynx.abraxas (AT) freenet (DOT) de escreveu:
Hallo!

Does this concern the usbvision saa711x/saa7115 as well? I have a "Hauppauge
WinTV USB device Model 40219 Rev E189". Some told me I would need tda9887
others told me I should not modprobe it.
I'm not sure about the configuration for this device. The answer is
related to what tuner you have. non-usbvision devices, there is a
module (tveeprom) that reads Hauppauge eeprom content and detects what
tuner you have. I'm not sure if this will work with usbvision.

Do you know what tuner is there ? Tuner is that metallic can inside the
board.

Things from me are at http://www.bttv-gallery.de/ under WinTV USB 40219 Rev. E189
There is a windows dump telling:
Philips FM1216ME H-3 // (B/G/I/D/K/L/L') (FM)
And also eeprom stuff
At ~.grr06742.2.stud.uni-r.de/ are the high res pics (WINTVU~1.JPG)
Also the thread from usbvision:

Anyway I did as told in your insturction but neither the saa's nor the
tuner.ko get changed in the kernellibs. Is that right?
No. tuner.ko should be replaced by a newer version. At the procedure
I've described, you need to manually remove the old tda9887.ko module.
Then, make install will replace tuner.ko by the newer one.
If this is not happening, you may try first:
make distclean, to clean all stuff, including .version file

Got the new modules finally. There is a make all necessary for me, how comes? (What gcc version do You recommend for kernel and its modules? I use gcc-3.3.6)

Now I'm stuck on the version mismatch usbvision complains about:

Jun 17 15:08:07 drago kernel: Linux video capture interface: v2.00
Jun 17 15:08:07 drago kernel: usbvision: disagrees about version of symbol video_devdata
Jun 17 15:08:07 drago kernel: usbvision: Unknown symbol video_devdata
Jun 17 15:08:07 drago kernel: usbvision: disagrees about version of symbol video_unregister_device
Jun 17 15:08:07 drago kernel: usbvision: Unknown symbol video_unregister_device
Jun 17 15:08:07 drago kernel: usbvision: disagrees about version of symbol video_device_alloc
Jun 17 15:08:07 drago kernel: usbvision: Unknown symbol video_device_alloc
Jun 17 15:08:07 drago kernel: usbvision: disagrees about version of symbol video_register_device
Jun 17 15:08:07 drago kernel: usbvision: Unknown symbol video_register_device
Jun 17 15:08:07 drago kernel: usbvision: disagrees about version of symbol video_device_release
Jun 17 15:08:07 drago kernel: usbvision: Unknown symbol video_device_release

What can I do about that?
Thanks for Your answers.

Lynx

Mauro Carvalho Chehab wrote:

>This patch is already known to work on pvrusb2, em28xx, ivtv and cx88
>drivers (at least with some boards). It should work with all tda9887
>based boards.

Tested successfully on bt878-based DViC FusionHDTV5 Lite:

[4295799.207000] Linux video capture interface: v2.00
[4295799.253000] bttv: driver version 0.9.16 loaded
[4295799.253000] bttv: using 8 buffers with 2080k (520 pages) each for
capture
[4295799.266000] bttv: Bt8xx card found (0).
[4295799.266000] ACPI: PCI Interrupt 0000:02:07.0[A] -GSI 19 (level,
low) -IRQ 19
[4295799.266000] bttv0: Bt878 (rev 17) at 0000:02:07.0, irq: 19,
latency: 64, mmio: 0xe8200000
[4295799.268000] bttv0: detected: DViC FusionHDTV 5 Lite [card=135],
PCI subsystem ID is 18ac:d500
[4295799.268000] bttv0: using: DViC FusionHDTV 5 Lite
[card=135,autodetected]
[4295799.268000] bttv0: gpio: en=00000000, out=00000000 in=00ffffdf [init]
[4295799.278000] tuner: tuner_debug is deprecated and will be removed in
2.6.17.
[4295799.278000] tuner: use the debug option instead.
[4295799.287000] tuner 0-0043: chip found @ 0x86 (bt878 #0 [sw])
[4295799.288000] tda9887 0-0043 (tda9887): tda988[5/6/7] found @ 0x43
(tuner)
[4295799.288000] tuner 0-0043: bt878 #0 [sw] tuner I2C addr 0x86 with
type 74 used for 0x0e
[4295799.295000] tuner: tuner_debug is deprecated and will be removed in
2.6.17.
[4295799.295000] tuner: use the debug option instead.
[4295799.295000] tuner 0-0061: Setting mode_mask to 0x0e
[4295799.295000] tuner 0-0061: chip found @ 0xc2 (bt878 #0 [sw])
[4295799.299000] tuner 0-0061: tuner 0x61: Tuner type absent
[4295799.323000] tuner: tuner_debug is deprecated and will be removed in
2.6.17.
[4295799.323000] tuner: use the debug option instead.
[4295799.323000] tuner 0-006b: chip found @ 0xd6 (bt878 #0 [sw])
[4295799.324000] tuner 0-006b: tuner 0x6b: Tuner type absent
[4295799.332000] tuner: tuner_debug is deprecated and will be removed in
2.6.17.
[4295799.332000] tuner: use the debug option instead.
[4295799.332000] tuner 0-006f: chip found @ 0xde (bt878 #0 [sw])
[4295799.336000] tuner 0-006f: tuner 0x6f: Tuner type absent
[4295799.340000] bttv0: using tuner=64
[4295799.340000] tuner 0-0043: Calling set_type_addr for type=64,
addr=0xff, mode=0x0c
[4295799.340000] tuner 0-0043: set addr for type 74
[4295799.340000] tuner 0-0061: Calling set_type_addr for type=64,
addr=0xff, mode=0x0c
[4295799.340000] tuner 0-0061: set addr for type -1
[4295799.343000] tuner 0-0061: type set to 64 (LG TDVS-H06xF)
[4295799.343000] tuner 0-0061: bt878 #0 [sw] tuner I2C addr 0xc2 with
type 64 used for 0x0e
[4295799.343000] tuner 0-006b: Calling set_type_addr for type=64,
addr=0xff, mode=0x0c
[4295799.343000] tuner 0-006b: set addr for type -1
[4295799.343000] tuner 0-006f: Calling set_type_addr for type=64,
addr=0xff, mode=0x0c
[4295799.343000] tuner 0-006f: set addr for type -1
[4295799.395000] bttv0: registered device video0
[4295799.395000] bttv0: registered device vbi0
[4295799.395000] tuner 0-0043: Cmd VIDIC_S_STD accepted for analog TV
[4295799.395000] tuner 0-0043: switching to v4l2
[4295799.395000] tuner 0-0061: Cmd VIDIC_S_STD accepted for analog TV
[4295799.395000] tuner 0-0061: switching to v4l2
[4295799.395000] tuner 0-0061: tv freq set to 400.00
[4295799.395000] tuner 0-0061: IFPCoff = 623: tuner_params undefined for
tuner 64
[4295799.395000] tuner 0-0061: tv: param 0, range 1
[4295799.395000] tuner 0-0061: Freq= 400.00 MHz, V_IF=38.93 MHz,
=0.00 MHz, div=7023
[4295799.395000] tuner 0-0061: tv 0x1b 0x6f 0x8e 0x02
[4295799.400000] bttv0: add subdevice "dvb0"
[4295801.703000] bt878: AUDI driver version 0.0.0 loaded
[4295801.713000] bt878: Bt878 AUDI function found (0).
[4295801.713000] ACPI: PCI Interrupt 0000:02:07.1[A] -GSI 19 (level,
low) -IRQ 19
[4295801.713000] bt878_probe: card id=[0xd50018ac],[ DViC FusionHDTV 5
Lite ] has DVB functions.
[4295801.713000] bt878(0): Bt878 (rev 17) at 02:07.1, irq: 19, latency:
64, memory: 0xe8201000
[4295801.747000] DVB: registering new adapter (bttv0).
[4295801.962000] DVB: registering frontend 0 (LG Electronics LGDT3303
VSB/QAM Frontend)

[4296651.714000] tda9887 0-0043 (tda9887): configure for: NTSC-M
[4296651.714000] tda9887 0-0043 (tda9887): writing: b=0xd4 c=0x30 e=0x44
[4296651.716000] tuner 0-0061: tv freq set to 48.25
[4296651.716000] tuner 0-0061: tv: param 0, range 0
[4296651.716000] tuner 0-0061: Freq= 48.25 MHz, V_IF=45.75 MHz,
=0.00 MHz, div=1504
[4296651.716000] tuner 0-0061: tv 0x05 0xe0 0x8e 0x01
[4296656.931000] tuner 0-0043: tv freq set to 73.25
[4296656.931000] tda9887 0-0043 (tda9887): configure for: NTSC-M
[4296656.931000] tda9887 0-0043 (tda9887): writing: b=0xd4 c=0x30 e=0x44
[4296656.934000] tuner 0-0061: tv freq set to 73.25
[4296656.934000] tuner 0-0061: tv: param 0, range 0
[4296656.934000] tuner 0-0061: Freq= 73.25 MHz, V_IF=45.75 MHz,
=0.00 MHz, div=1904
[4296656.934000] tuner 0-0061: tv 0x07 0x70 0x8e 0x01
[4296657.587000] tuner 0-0043: tv freq set to 55.25
[4296657.587000] tda9887 0-0043 (tda9887): configure for: NTSC-M
[4296657.587000] tda9887 0-0043 (tda9887): writing: b=0xd4 c=0x30 e=0x44
[4296657.589000] tuner 0-0061: tv freq set to 55.25
[4296657.589000] tuner 0-0061: tv: param 0, range 0
[4296657.589000] tuner 0-0061: Freq= 55.25 MHz, V_IF=45.75 MHz,
=0.00 MHz, div=1616
[4296657.589000] tuner 0-0061: tv 0x06 0x50 0x8e 0x01
[4296716.464000] tuner 0-0043: tv freq set to 61.25
[4296716.464000] tda9887 0-0043 (tda9887): configure for: NTSC-M
[4296716.464000] tda9887 0-0043 (tda9887): writing: b=0xd4 c=0x30 e=0x44
[4296716.467000] tuner 0-0061: tv freq set to 61.25
[4296716.467000] tuner 0-0061: tv: param 0, range 0
[4296716.467000] tuner 0-0061: Freq= 61.25 MHz, V_IF=45.75 MHz,
=0.00 MHz, div=1712
[4296716.467000] tuner 0-0061: tv 0x06 0xb0 0x8e 0x01
[4296739.230000] tuner 0-0043: tv freq set to 67.25
[4296739.230000] tda9887 0-0043 (tda9887): configure for: NTSC-M
[4296739.230000] tda9887 0-0043 (tda9887): writing: b=0xd4 c=0x30 e=0x44
[4296739.232000] tuner 0-0061: tv freq set to 67.25
[4296739.232000] tuner 0-0061: tv: param 0, range 0
[4296739.232000] tuner 0-0061: Freq= 67.25 MHz, V_IF=45.75 MHz,
=0.00 MHz, div=1808
[4296739.232000] tuner 0-0061: tv 0x07 0x10 0x8e 0x01
[4296739.873000] tuner 0-0043: tv freq set to 77.25
[4296739.873000] tda9887 0-0043 (tda9887): configure for: NTSC-M
[4296739.873000] tda9887 0-0043 (tda9887): writing: b=0xd4 c=0x30 e=0x44
[4296739.875000] tuner 0-0061: tv freq set to 77.25
[4296739.875000] tuner 0-0061: tv: param 0, range 0
[4296739.875000] tuner 0-0061: Freq= 77.25 MHz, V_IF=45.75 MHz,
=0.00 MHz, div=1968
[4296739.875000] tuner 0-0061: tv 0x07 0xb0 0x8e 0x01
[4296740.965000] tuner 0-0043: tv freq set to 83.25
[4296740.965000] tda9887 0-0043 (tda9887): configure for: NTSC-M
[4296740.965000] tda9887 0-0043 (tda9887): writing: b=0xd4 c=0x30 e=0x44
[4296740.968000] tuner 0-0061: tv freq set to 83.25
[4296740.968000] tuner 0-0061: tv: param 0, range 0
[4296740.968000] tuner 0-0061: Freq= 83.25 MHz, V_IF=45.75 MHz,
=0.00 MHz, div=2064
[4296740.968000] tuner 0-0061: tv 0x08 0x10 0x8e 0x01
[4296741.687000] tuner 0-0043: tv freq set to 175.25
[4296741.687000] tda9887 0-0043 (tda9887): configure for: NTSC-M
[4296741.687000] tda9887 0-0043 (tda9887): writing: b=0xd4 c=0x30 e=0x44
[4296741.689000] tuner 0-0061: tv freq set to 175.25
[4296741.689000] tuner 0-0061: tv: param 0, range 1
[4296741.689000] tuner 0-0061: Freq= 175.25 MHz, V_IF=45.75 MHz,
=0.00 MHz, div=3536
[4296741.689000] tuner 0-0061: tv 0x0d 0xd0 0x8e 0x02
[4296742.319000] tuner 0-0043: tv freq set to 181.25
[4296742.319000] tda9887 0-0043 (tda9887): configure for: NTSC-M
[4296742.319000] tda9887 0-0043 (tda9887): writing: b=0xd4 c=0x30 e=0x44
[4296742.322000] tuner 0-0061: tv freq set to 181.25
[4296742.322000] tuner 0-0061: tv: param 0, range 1
[4296742.322000] tuner 0-0061: Freq= 181.25 MHz, V_IF=45.75 MHz,
=0.00 MHz, div=3632
[4296742.322000] tuner 0-0061: tv 0x0e 0x30 0x8e 0x02
[4296742.983000] tuner 0-0043: tv freq set to 187.25
[4296742.983000] tda9887 0-0043 (tda9887): configure for: NTSC-M
[4296742.983000] tda9887 0-0043 (tda9887): writing: b=0xd4 c=0x30 e=0x44
[4296742.986000] tuner 0-0061: tv freq set to 187.25
[4296742.986000] tuner 0-0061: tv: param 0, range 1
[4296742.986000] tuner 0-0061: Freq= 187.25 MHz, V_IF=45.75 MHz,
=0.00 MHz, div=3728
[4296742.986000] tuner 0-0061: tv 0x0e 0x90 0x8e 0x02
[4296750.858000] tuner 0-0043: tv freq set to 193.25
[4296750.858000] tda9887 0-0043 (tda9887): configure for: NTSC-M
[4296750.858000] tda9887 0-0043 (tda9887): writing: b=0xd4 c=0x30 e=0x44
[4296750.860000] tuner 0-0061: tv freq set to 193.25
[4296750.860000] tuner 0-0061: tv: param 0, range 1
[4296750.860000] tuner 0-0061: Freq= 193.25 MHz, V_IF=45.75 MHz,
=0.00 MHz, div=3824
[4296750.860000] tuner 0-0061: tv 0x0e 0xf0 0x8e 0x02
[4296751.684000] tuner 0-0043: tv freq set to 199.25
[4296751.684000] tda9887 0-0043 (tda9887): configure for: NTSC-M
[4296751.684000] tda9887 0-0043 (tda9887): writing: b=0xd4 c=0x30 e=0x44
[4296751.686000] tuner 0-0061: tv freq set to 199.25
[4296751.686000] tuner 0-0061: tv: param 0, range 1
[4296751.686000] tuner 0-0061: Freq= 199.25 MHz, V_IF=45.75 MHz,
=0.00 MHz, div=3920
[4296751.686000] tuner 0-0061: tv 0x0f 0x50 0x8e 0x02
[4296752.489000] tuner 0-0043: tv freq set to 205.25
[4296752.489000] tda9887 0-0043 (tda9887): configure for: NTSC-M
[4296752.489000] tda9887 0-0043 (tda9887): writing: b=0xd4 c=0x30 e=0x44
[4296752.491000] tuner 0-0061: tv freq set to 205.25
[4296752.491000] tuner 0-0061: tv: param 0, range 1
[4296752.491000] tuner 0-0061: Freq= 205.25 MHz, V_IF=45.75 MHz,
=0.00 MHz, div=4016
[4296752.491000] tuner 0-0061: tv 0x0f 0xb0 0x8e 0x02
[4296753.440000] tuner 0-0043: tv freq set to 211.25
[4296753.440000] tda9887 0-0043 (tda9887): configure for: NTSC-M
[4296753.440000] tda9887 0-0043 (tda9887): writing: b=0xd4 c=0x30 e=0x44
[4296753.443000] tuner 0-0061: tv freq set to 211.25
[4296753.443000] tuner 0-0061: tv: param 0, range 1
[4296753.443000] tuner 0-0061: Freq= 211.25 MHz, V_IF=45.75 MHz,
=0.00 MHz, div=4112
[4296753.443000] tuner 0-0061: tv 0x10 0x10 0x8e 0x02
[4296754.568000] tuner 0-0043: tv freq set to 121.25
[4296754.568000] tda9887 0-0043 (tda9887): configure for: NTSC-M
[4296754.568000] tda9887 0-0043 (tda9887): writing: b=0xd4 c=0x30 e=0x44
[4296754.570000] tuner 0-0061: tv freq set to 121.25
[4296754.570000] tuner 0-0061: tv: param 0, range 0
[4296754.570000] tuner 0-0061: Freq= 121.25 MHz, V_IF=45.75 MHz,
=0.00 MHz, div=2672
[4296754.570000] tuner 0-0061: tv 0x0a 0x70 0x8e 0x01

Em Ter, 2006-06-20 01:05 -0400, Michael Krufky escreveu:
Mauro Carvalho Chehab wrote:

>This patch is already known to work on pvrusb2, em28xx, ivtv and cx88
>drivers (at least with some boards). It should work with all tda9887
>based boards.

Tested successfully on bt878-based DViC FusionHDTV5 Lite:

Nice! it seems that tda9887 is ready to go to the main tree. People,
please report any stuff that might broke after this patch.

Cheers,
Mauro.

Am Donnerstag, den 15.06.2006, 18:10 +0200 schrieb hermann pitton:
Am Mittwoch, den 14.06.2006, 14:24 -0300 schrieb Mauro Carvalho Chehab:

[]

cool, this time it is indeed working on the saa7134 too!

Folks please test, especially with hybrid devices like Pinnacle 300i,
md7134 with FMD1216ME and similar, also the ATSC tuners.

Mauro needs feedback for those tda9885/6/7 bttv cards too.

Just a quick note, not yet investigated.

I had a short test on kradio too that time, autotuning locks as usual on
stereo detection and all seemed fine.

Just notice, if tuning into some off there is a high thrilling noise
from the chip, at least not what we had previously

Cheers,
Hermann

Am Montag, den 10.07.2006, 01:49 +0200 schrieb hermann pitton:
Am Donnerstag, den 15.06.2006, 18:10 +0200 schrieb hermann pitton:
Am Mittwoch, den 14.06.2006, 14:24 -0300 schrieb Mauro Carvalho Chehab:

[]

cool, this time it is indeed working on the saa7134 too!

Folks please test, especially with hybrid devices like Pinnacle 300i,
md7134 with FMD1216ME and similar, also the ATSC tuners.

Mauro needs feedback for those tda9885/6/7 bttv cards too.

Just a quick note, not yet investigated.

I had a short test on kradio too that time, autotuning locks as usual on
stereo detection and all seemed fine.

Just notice, if tuning into some off there is a high thrilling noise
from the chip, at least not what we had previously

logs.

tuner 2-0060: v4l2 ioctl VIDIC_G_TUNER, dir=rw (0xc054561d)
tuner 2-0060: Cmd VIDIC_G_TUNER accepted for radio
tuner 2-0043: v4l2 ioctl VIDIC_S_FREQUENCY, dir=-w (0x402c5639)
tuner 2-0043: radio freq set to 102.30
tda9887 2-0043: configure for: Radio Stereo
tda9887 2-0043: writing: b=0x4c c=0x90 e=0x3d
tda9887 2-0043: write: byte B 0x4c
tda9887 2-0043: B0 video mode : sound trap
tda9887 2-0043: B1 auto mute fm : no
tda9887 2-0043: B2 carrier mode : QSS
tda9887 2-0043: B3-4 tv sound/radio : FM/radio
tda9887 2-0043: B5 force mute audio: no
tda9887 2-0043: B6 output port 1 : high (inactive)
tda9887 2-0043: B7 output port 2 : low (active)
tda9887 2-0043: write: byte C 0x90
tda9887 2-0043: C0-4 top adjustment : 0 dB
tda9887 2-0043: C5-6 de-emphasis : no
tda9887 2-0043: C7 audio gain : -6
tda9887 2-0043: write: byte E 0x3d
tda9887 2-0043: E0-1 sound carrier : 5.5 MHz
tda9887 2-0043: E6 l pll gating : 13
tda9887 2-0043: E2-4 video if : 44 MHz
tda9887 2-0043: E7 vif agc output : fm radio carrier afc
tda9887 2-0043: --
tuner 2-0060: v4l2 ioctl VIDIC_S_FREQUENCY, dir=-w (0x402c5639)
tuner 2-0060: radio freq set to 102.30
tuner 2-0060: radio 0x08 0xd4 0x88 0x19
tuner 2-0043: v4l2_int ioctl TDA9887_SET_CNFIG, dir=-w (0x4004645c)
tuner 2-0043: radio freq set to 0.00
tuner 2-0043: radio freq (0.00) out of range (65-108)
tda9887 2-0043: configure for: Radio Stereo
tda9887 2-0043: writing: b=0x4c c=0x90 e=0x3d
tda9887 2-0043: write: byte B 0x4c
tda9887 2-0043: B0 video mode : sound trap
tda9887 2-0043: B1 auto mute fm : no
tda9887 2-0043: B2 carrier mode : QSS
tda9887 2-0043: B3-4 tv sound/radio : FM/radio
tda9887 2-0043: B5 force mute audio: no
tda9887 2-0043: B6 output port 1 : high (inactive)
tda9887 2-0043: B7 output port 2 : low (active)
tda9887 2-0043: write: byte C 0x90
tda9887 2-0043: C0-4 top adjustment : 0 dB
tda9887 2-0043: C5-6 de-emphasis : no
tda9887 2-0043: C7 audio gain : -6
tda9887 2-0043: write: byte E 0x3d
tda9887 2-0043: E0-1 sound carrier : 5.5 MHz
tda9887 2-0043: E6 l pll gating : 13
tda9887 2-0043: E2-4 video if : 44 MHz
tda9887 2-0043: E7 vif agc output : fm radio carrier afc
tda9887 2-0043: --
tuner 2-0060: v4l2_int ioctl TDA9887_SET_CNFIG, dir=-w (0x4004645c)
tuner 2-0043: v4l2 ioctl VIDIC_G_TUNER, dir=rw (0xc054561d)
tuner 2-0043: Cmd VIDIC_G_TUNER accepted for radio

Was initially on the way to look what should make secam=d fail on
2.6.17, but can't test the true thing, as most of us.

Cheers,
Hermann

Am Montag, den 10.07.2006, 02:37 +0200 schrieb hermann pitton:
Am Montag, den 10.07.2006, 01:49 +0200 schrieb hermann pitton:
Am Donnerstag, den 15.06.2006, 18:10 +0200 schrieb hermann pitton:
Am Mittwoch, den 14.06.2006, 14:24 -0300 schrieb Mauro Carvalho Chehab:

[]

cool, this time it is indeed working on the saa7134 too!

Folks please test, especially with hybrid devices like Pinnacle 300i,
md7134 with FMD1216ME and similar, also the ATSC tuners.

Mauro needs feedback for those tda9885/6/7 bttv cards too.

Just a quick note, not yet investigated.

I had a short test on kradio too that time, autotuning locks as usual on
stereo detection and all seemed fine.

Just notice, if tuning into some off there is a high thrilling noise
from the chip, at least not what we had previously

logs.

tuner 2-0060: v4l2 ioctl VIDIC_G_TUNER, dir=rw (0xc054561d)
tuner 2-0060: Cmd VIDIC_G_TUNER accepted for radio
tuner 2-0043: v4l2 ioctl VIDIC_S_FREQUENCY, dir=-w (0x402c5639)
tuner 2-0043: radio freq set to 102.30
tda9887 2-0043: configure for: Radio Stereo
tda9887 2-0043: writing: b=0x4c c=0x90 e=0x3d
tda9887 2-0043: write: byte B 0x4c
tda9887 2-0043: B0 video mode : sound trap
tda9887 2-0043: B1 auto mute fm : no
tda9887 2-0043: B2 carrier mode : QSS
tda9887 2-0043: B3-4 tv sound/radio : FM/radio
tda9887 2-0043: B5 force mute audio: no
tda9887 2-0043: B6 output port 1 : high (inactive)
tda9887 2-0043: B7 output port 2 : low (active)
tda9887 2-0043: write: byte C 0x90
tda9887 2-0043: C0-4 top adjustment : 0 dB
tda9887 2-0043: C5-6 de-emphasis : no
tda9887 2-0043: C7 audio gain : -6
tda9887 2-0043: write: byte E 0x3d
tda9887 2-0043: E0-1 sound carrier : 5.5 MHz
tda9887 2-0043: E6 l pll gating : 13
tda9887 2-0043: E2-4 video if : 44 MHz
tda9887 2-0043: E7 vif agc output : fm radio carrier afc
tda9887 2-0043: --
tuner 2-0060: v4l2 ioctl VIDIC_S_FREQUENCY, dir=-w (0x402c5639)
tuner 2-0060: radio freq set to 102.30
tuner 2-0060: radio 0x08 0xd4 0x88 0x19
tuner 2-0043: v4l2_int ioctl TDA9887_SET_CNFIG, dir=-w (0x4004645c)
tuner 2-0043: radio freq set to 0.00
tuner 2-0043: radio freq (0.00) out of range (65-108)
tda9887 2-0043: configure for: Radio Stereo
tda9887 2-0043: writing: b=0x4c c=0x90 e=0x3d
tda9887 2-0043: write: byte B 0x4c
tda9887 2-0043: B0 video mode : sound trap
tda9887 2-0043: B1 auto mute fm : no
tda9887 2-0043: B2 carrier mode : QSS
tda9887 2-0043: B3-4 tv sound/radio : FM/radio
tda9887 2-0043: B5 force mute audio: no
tda9887 2-0043: B6 output port 1 : high (inactive)
tda9887 2-0043: B7 output port 2 : low (active)
tda9887 2-0043: write: byte C 0x90
tda9887 2-0043: C0-4 top adjustment : 0 dB
tda9887 2-0043: C5-6 de-emphasis : no
tda9887 2-0043: C7 audio gain : -6
tda9887 2-0043: write: byte E 0x3d
tda9887 2-0043: E0-1 sound carrier : 5.5 MHz
tda9887 2-0043: E6 l pll gating : 13
tda9887 2-0043: E2-4 video if : 44 MHz
tda9887 2-0043: E7 vif agc output : fm radio carrier afc
tda9887 2-0043: --
tuner 2-0060: v4l2_int ioctl TDA9887_SET_CNFIG, dir=-w (0x4004645c)
tuner 2-0043: v4l2 ioctl VIDIC_G_TUNER, dir=rw (0xc054561d)
tuner 2-0043: Cmd VIDIC_G_TUNER accepted for radio

Was initially on the way to look what should make secam=d fail on
2.6.17, but can't test the true thing, as most of us.

Hi,

not much time, but at least some further tests.

With the original testing release from Mauro there is no problem with
setfreq on radio when the stereo detection is lost, this must happen
with the further changes.

But when forced to mono deemphasis stays already at : no. That is not
what was supposed for keeping mono working. I have nothing in mono,
except stereo forced to mono, but I'm sure Nickolay went through it.

Does this happen intentionally and if, why?

Cheers,
Hermann

Am Dienstag, den 11.07.2006, 02:30 +0200 schrieb hermann pitton:
Am Montag, den 10.07.2006, 02:37 +0200 schrieb hermann pitton:
Am Montag, den 10.07.2006, 01:49 +0200 schrieb hermann pitton:
Am Donnerstag, den 15.06.2006, 18:10 +0200 schrieb hermann pitton:
Am Mittwoch, den 14.06.2006, 14:24 -0300 schrieb Mauro Carvalho Chehab:

[]

cool, this time it is indeed working on the saa7134 too!

Folks please test, especially with hybrid devices like Pinnacle 300i,
md7134 with FMD1216ME and similar, also the ATSC tuners.

Mauro needs feedback for those tda9885/6/7 bttv cards too.

Just a quick note, not yet investigated.

I had a short test on kradio too that time, autotuning locks as usual on
stereo detection and all seemed fine.

Just notice, if tuning into some off there is a high thrilling noise
from the chip, at least not what we had previously

logs.

tuner 2-0060: v4l2 ioctl VIDIC_G_TUNER, dir=rw (0xc054561d)
tuner 2-0060: Cmd VIDIC_G_TUNER accepted for radio
tuner 2-0043: v4l2 ioctl VIDIC_S_FREQUENCY, dir=-w (0x402c5639)
tuner 2-0043: radio freq set to 102.30
tda9887 2-0043: configure for: Radio Stereo
tda9887 2-0043: writing: b=0x4c c=0x90 e=0x3d
tda9887 2-0043: write: byte B 0x4c
tda9887 2-0043: B0 video mode : sound trap
tda9887 2-0043: B1 auto mute fm : no
tda9887 2-0043: B2 carrier mode : QSS
tda9887 2-0043: B3-4 tv sound/radio : FM/radio
tda9887 2-0043: B5 force mute audio: no
tda9887 2-0043: B6 output port 1 : high (inactive)
tda9887 2-0043: B7 output port 2 : low (active)
tda9887 2-0043: write: byte C 0x90
tda9887 2-0043: C0-4 top adjustment : 0 dB
tda9887 2-0043: C5-6 de-emphasis : no
tda9887 2-0043: C7 audio gain : -6
tda9887 2-0043: write: byte E 0x3d
tda9887 2-0043: E0-1 sound carrier : 5.5 MHz
tda9887 2-0043: E6 l pll gating : 13
tda9887 2-0043: E2-4 video if : 44 MHz
tda9887 2-0043: E7 vif agc output : fm radio carrier afc
tda9887 2-0043: --
tuner 2-0060: v4l2 ioctl VIDIC_S_FREQUENCY, dir=-w (0x402c5639)
tuner 2-0060: radio freq set to 102.30
tuner 2-0060: radio 0x08 0xd4 0x88 0x19
tuner 2-0043: v4l2_int ioctl TDA9887_SET_CNFIG, dir=-w (0x4004645c)
tuner 2-0043: radio freq set to 0.00
tuner 2-0043: radio freq (0.00) out of range (65-108)
tda9887 2-0043: configure for: Radio Stereo
tda9887 2-0043: writing: b=0x4c c=0x90 e=0x3d
tda9887 2-0043: write: byte B 0x4c
tda9887 2-0043: B0 video mode : sound trap
tda9887 2-0043: B1 auto mute fm : no
tda9887 2-0043: B2 carrier mode : QSS
tda9887 2-0043: B3-4 tv sound/radio : FM/radio
tda9887 2-0043: B5 force mute audio: no
tda9887 2-0043: B6 output port 1 : high (inactive)
tda9887 2-0043: B7 output port 2 : low (active)
tda9887 2-0043: write: byte C 0x90
tda9887 2-0043: C0-4 top adjustment : 0 dB
tda9887 2-0043: C5-6 de-emphasis : no
tda9887 2-0043: C7 audio gain : -6
tda9887 2-0043: write: byte E 0x3d
tda9887 2-0043: E0-1 sound carrier : 5.5 MHz
tda9887 2-0043: E6 l pll gating : 13
tda9887 2-0043: E2-4 video if : 44 MHz
tda9887 2-0043: E7 vif agc output : fm radio carrier afc
tda9887 2-0043: --
tuner 2-0060: v4l2_int ioctl TDA9887_SET_CNFIG, dir=-w (0x4004645c)
tuner 2-0043: v4l2 ioctl VIDIC_G_TUNER, dir=rw (0xc054561d)
tuner 2-0043: Cmd VIDIC_G_TUNER accepted for radio

Was initially on the way to look what should make secam=d fail on
2.6.17, but can't test the true thing, as most of us.

Hi,

not much time, but at least some further tests.

With the original testing release from Mauro there is no problem with
setfreq on radio when the stereo detection is lost, this must happen
with the further changes.

But when forced to mono deemphasis stays already at : no. That is not
what was supposed for keeping mono working. I have nothing in mono,
except stereo forced to mono, but I'm sure Nickolay went through it.

Does this happen intentionally and if, why?

That is only misleading print stuff. Instead "on" prints "no".

tuner 2-0043: Cmd AUDC_SET_RADI accepted for radio
tuner 2-0043: radio freq set to 102.15
tda9887 2-0043 (tda9887): configure for: Radio Mono
tda9887 2-0043 (tda9887): writing: b=0x4e c=0x30 e=0x3d
tda9887 2-0043 (tda9887): write: byte B 0x4e
tda9887 2-0043 (tda9887): B0 video mode : sound trap
tda9887 2-0043 (tda9887): B1 auto mute fm : yes
tda9887 2-0043 (tda9887): B2 carrier mode : QSS
tda9887 2-0043 (tda9887): B3-4 tv sound/radio : FM/radio
tda9887 2-0043 (tda9887): B5 force mute audio: no
tda9887 2-0043 (tda9887): B6 output port 1 : high (inactive)
tda9887 2-0043 (tda9887): B7 output port 2 : low (active)
tda9887 2-0043 (tda9887): write: byte C 0x30
tda9887 2-0043 (tda9887): C0-4 top adjustment : 0 dB
tda9887 2-0043 (tda9887): C5-6 de-emphasis : no
tda9887 2-0043 (tda9887): C7 audio gain : 0
tda9887 2-0043 (tda9887): write: byte E 0x3d
tda9887 2-0043 (tda9887): E0-1 sound carrier : 5.5 MHz
tda9887 2-0043 (tda9887): E6 l pll gating : 13
tda9887 2-0043 (tda9887): E2-4 video if : 44 MHz
tda9887 2-0043 (tda9887): E7 vif agc output : fm radio carrier afc
tda9887 2-0043 (tda9887): --
C = 0x30 is correct for TP 0x10, N, deemphasis75 and audio
gain 0.

tuner 2-0043: v4l2 ioctl VIDIC_S_FREQUENCY, dir=-w (0x402c5639)
tuner 2-0043: radio freq set to 102.15
tda9887 2-0043 (tda9887): configure for: Radio Stereo
tda9887 2-0043 (tda9887): writing: b=0x4e c=0x90 e=0x3d
tda9887 2-0043 (tda9887): write: byte B 0x4e
tda9887 2-0043 (tda9887): B0 video mode : sound trap
tda9887 2-0043 (tda9887): B1 auto mute fm : yes
tda9887 2-0043 (tda9887): B2 carrier mode : QSS
tda9887 2-0043 (tda9887): B3-4 tv sound/radio : FM/radio
tda9887 2-0043 (tda9887): B5 force mute audio: no
tda9887 2-0043 (tda9887): B6 output port 1 : high (inactive)
tda9887 2-0043 (tda9887): B7 output port 2 : low (active)
tda9887 2-0043 (tda9887): write: byte C 0x90
tda9887 2-0043 (tda9887): C0-4 top adjustment : 0 dB
tda9887 2-0043 (tda9887): C5-6 de-emphasis : no
tda9887 2-0043 (tda9887): C7 audio gain : -6
tda9887 2-0043 (tda9887): write: byte E 0x3d
tda9887 2-0043 (tda9887): E0-1 sound carrier : 5.5 MHz
tda9887 2-0043 (tda9887): E6 l pll gating : 13
tda9887 2-0043 (tda9887): E2-4 video if : 44 MHz
tda9887 2-0043 (tda9887): E7 vif agc output : fm radio carrier afc
tda9887 2-0043 (tda9887): --
tuner 2-0060: v4l2 ioctl VIDIC_S_FREQUENCY, dir=-w (0x402c5639)
tuner 2-0060: radio freq set to 102.15
tuner 2-0060: radio 0x08 0xd1 0x88 0x19

Same goes for C 0x90 and stereo configuration.

Hans has changed TP from 0x10 (still on NTSC tuners and radio) to 0x14
on PAL/SECAM. This must be taken from the FQ1200MK3 application note
1_0, the FM1216ME MK3 stuff said 0x10. They also mention a newer
modified chip. With the current configuration 0x14 seems K, have only
PAL-BG. Previously there have been more reports to lower it for about
2-4 dB helps on noise created from AGC. DScaler has/had it for PAL-I on
some cards, IIRC.

Just to mention it, if something comes up. Not related to radio though.
BTW, there is a patch pending to correct tda9887_get_afc.

Cheers,
Hermann

[]

Just notice, if tuning into some off there is a high thrilling noise
from the chip, at least not what we had previously

Hi,

can't see anything wrong yet after a first closer look.
Hans seems to have done a very nice job for these tuners.

saa7134[0]: i2c xfer: < c0 08 fc 88 19 >
saa7134[0]: i2c xfer: < 87 =50 >
saa7134[0]: i2c xfer: < c1 =79 >
saa7134[0]: i2c xfer: < c1 =7b >
saa7134[0]: i2c xfer: < 86 00 60 00 00 >
saa7134[0]: i2c xfer: < 86 00 4c 90 3d >
saa7134[0]: i2c xfer: < c0 08 fc 88 19 >
saa7134[0]: i2c xfer: < 87 =4e >
saa7134[0]: i2c xfer: < c1 =7c >
saa7134[0]: i2c xfer: < c1 =7c >
saa7134[0]: i2c xfer: < 86 00 60 00 00 >
saa7134[0]: i2c xfer: < 86 00 4c 90 3d >
saa7134[0]: i2c xfer: < c0 08 fc 88 19 >
saa7134[0]: i2c xfer: < 87 =d2 >
saa7134[0]: i2c xfer: < c1 =7c >
saa7134[0]: i2c xfer: < c1 =7c >
saa7134[0]: i2c xfer: < 87 =c8 >
saa7134[0]: i2c xfer: < c1 =79 >
saa7134[0]: i2c xfer: < c1 =79 >
saa7134[0]: i2c xfer: < 87 =ce >
saa7134[0]: i2c xfer: < c1 =79 >
saa7134[0]: i2c xfer: < c1 =79 >
saa7134[0]: i2c xfer: < 86 00 4c 90 3d >
saa7134[0]: i2c xfer: < 86 00 4c 90 3d >
saa7134[0]: i2c xfer: < c0 08 fc 88 19 >
saa7134[0]: i2c xfer: < 87 =c4 >
saa7134[0]: i2c xfer: < c1 =79 >
saa7134[0]: i2c xfer: < c1 =79 >
saa7134[0]: i2c xfer: < 87 =d8 >
saa7134[0]: i2c xfer: < c1 =79 >
saa7134[0]: i2c xfer: < c1 =79 >
saa7134[0]: i2c xfer: < 87 =50 >
saa7134[0]: i2c xfer: < c1 =79 >

However, this 86 00 60 00 00 should not happen on radio, IIRC.

Cheers,
Hermann

Am Freitag, den 14.07.2006, 00:32 +0200 schrieb hermann pitton:
[]

Just notice, if tuning into some off there is a high thrilling noise
from the chip, at least not what we had previously

Hi,

can't see anything wrong yet after a first closer look.
Hans seems to have done a very nice job for these tuners.

saa7134[0]: i2c xfer: < c0 08 fc 88 19 >
saa7134[0]: i2c xfer: < 87 =50 >
saa7134[0]: i2c xfer: < c1 =79 >
saa7134[0]: i2c xfer: < c1 =7b >
saa7134[0]: i2c xfer: < 86 00 60 00 00 >
saa7134[0]: i2c xfer: < 86 00 4c 90 3d >
saa7134[0]: i2c xfer: < c0 08 fc 88 19 >
saa7134[0]: i2c xfer: < 87 =4e >
saa7134[0]: i2c xfer: < c1 =7c >
saa7134[0]: i2c xfer: < c1 =7c >
saa7134[0]: i2c xfer: < 86 00 60 00 00 >
saa7134[0]: i2c xfer: < 86 00 4c 90 3d >
saa7134[0]: i2c xfer: < c0 08 fc 88 19 >
saa7134[0]: i2c xfer: < 87 =d2 >
saa7134[0]: i2c xfer: < c1 =7c >
saa7134[0]: i2c xfer: < c1 =7c >
saa7134[0]: i2c xfer: < 87 =c8 >
saa7134[0]: i2c xfer: < c1 =79 >
saa7134[0]: i2c xfer: < c1 =79 >
saa7134[0]: i2c xfer: < 87 =ce >
saa7134[0]: i2c xfer: < c1 =79 >
saa7134[0]: i2c xfer: < c1 =79 >
saa7134[0]: i2c xfer: < 86 00 4c 90 3d >
saa7134[0]: i2c xfer: < 86 00 4c 90 3d >
saa7134[0]: i2c xfer: < c0 08 fc 88 19 >
saa7134[0]: i2c xfer: < 87 =c4 >
saa7134[0]: i2c xfer: < c1 =79 >
saa7134[0]: i2c xfer: < c1 =79 >
saa7134[0]: i2c xfer: < 87 =d8 >
saa7134[0]: i2c xfer: < c1 =79 >
saa7134[0]: i2c xfer: < c1 =79 >
saa7134[0]: i2c xfer: < 87 =50 >
saa7134[0]: i2c xfer: < c1 =79 >

However, this 86 00 60 00 00 should not happen on radio, IIRC.

Hi,

no, that standby isn't the problem.

saa7134[0]: i2c xfer: < 86 00 60 00 00 >
saa7134[0]: i2c xfer: < 86 00 4c 90 3d >
saa7134[0]: i2c xfer: < 86 00 60 00 00 >
saa7134[0]: i2c xfer: < 86 00 4c 90 3d >
saa7134[0]: i2c xfer: < 86 00 60 00 00 >
saa7134[0]: i2c xfer: < 86 00 4c 90 3d >
saa7134[0]: i2c xfer: < 86 00 4c 90 3d >
saa7134[0]: i2c xfer: < 86 00 4c 90 3d >
saa7134[0]: i2c xfer: < 86 00 60 00 00 >
saa7134[0]: i2c xfer: < 86 >
saa7134[0]: i2c xfer: < 86 01 02 >
saa7134[0]: i2c xfer: < 86 00 00 >
saa7134[0]: i2c xfer: < 86 07 >
saa7134[0]: i2c xfer: < 86 00 d6 30 >
tuner 2-0043: chip found @ 0x86 (saa7134[0])
saa7134[0]: i2c xfer: < 86 00 e2 00 00 >
saa7134[0]: i2c xfer: < 86 00 e2 00 00 >
saa7134[0]: i2c xfer: < 86 00 ce 90 3d >
saa7134[0]: i2c xfer: < 86 00 e2 00 00 >
saa7134[0]: i2c xfer: < 86 00 ce 90 3d >
saa7134[0]: i2c xfer: < 86 00 e2 00 00 >
saa7134[0]: i2c xfer: < 86 00 ce 90 3d >
saa7134[0]: i2c xfer: < 86 00 e2 00 00 >
saa7134[0]: i2c xfer: < 86 00 ce 90 3d >
saa7134[0]: i2c xfer: < 86 00 ce 90 3d >
saa7134[0]: i2c xfer: < 86 00 e2 00 00 >

It was always visible, but had suspects on the wrong end.

Automute is disabled. Why?

Should it be reenabled, at least for radio,
what I have now to get rid of this crazy noise,

static struct tvnorm radio_stereo = {
.name = "Radio Stereo",
.b = ( cFmRadio |
cQSS |
cAutoMuteFmActive ),
.c = ( cDFF |
cAudioGain6 |
cTopDefault),
.e = ( cTunerGainLow |
cAudioIF_5_5 |
cRadioIF_38_90 ),
};

static struct tvnorm radio_mono = {
.name = "Radio Mono",
.b = ( cFmRadio |
cQSS |
cAutoMuteFmActive ),
.c = ( cDN |
cDeemphasis75 |
cTopDefault),
.e = ( cTunerGainLow |
cAudioIF_5_5 |
cRadioIF_38_90 ),
};

or set per tuner?

Cheers,
Hermann

Am Samstag, den 15.07.2006, 00:52 +0200 schrieb hermann pitton:
Am Freitag, den 14.07.2006, 00:32 +0200 schrieb hermann pitton:
[]

Just notice, if tuning into some off there is a high thrilling noise
from the chip, at least not what we had previously

Hi,

can't see anything wrong yet after a first closer look.
Hans seems to have done a very nice job for these tuners.

saa7134[0]: i2c xfer: < c0 08 fc 88 19 >
saa7134[0]: i2c xfer: < 87 =50 >
saa7134[0]: i2c xfer: < c1 =79 >
saa7134[0]: i2c xfer: < c1 =7b >
saa7134[0]: i2c xfer: < 86 00 60 00 00 >
saa7134[0]: i2c xfer: < 86 00 4c 90 3d >
saa7134[0]: i2c xfer: < c0 08 fc 88 19 >
saa7134[0]: i2c xfer: < 87 =4e >
saa7134[0]: i2c xfer: < c1 =7c >
saa7134[0]: i2c xfer: < c1 =7c >
saa7134[0]: i2c xfer: < 86 00 60 00 00 >
saa7134[0]: i2c xfer: < 86 00 4c 90 3d >
saa7134[0]: i2c xfer: < c0 08 fc 88 19 >
saa7134[0]: i2c xfer: < 87 =d2 >
saa7134[0]: i2c xfer: < c1 =7c >
saa7134[0]: i2c xfer: < c1 =7c >
saa7134[0]: i2c xfer: < 87 =c8 >
saa7134[0]: i2c xfer: < c1 =79 >
saa7134[0]: i2c xfer: < c1 =79 >
saa7134[0]: i2c xfer: < 87 =ce >
saa7134[0]: i2c xfer: < c1 =79 >
saa7134[0]: i2c xfer: < c1 =79 >
saa7134[0]: i2c xfer: < 86 00 4c 90 3d >
saa7134[0]: i2c xfer: < 86 00 4c 90 3d >
saa7134[0]: i2c xfer: < c0 08 fc 88 19 >
saa7134[0]: i2c xfer: < 87 =c4 >
saa7134[0]: i2c xfer: < c1 =79 >
saa7134[0]: i2c xfer: < c1 =79 >
saa7134[0]: i2c xfer: < 87 =d8 >
saa7134[0]: i2c xfer: < c1 =79 >
saa7134[0]: i2c xfer: < c1 =79 >
saa7134[0]: i2c xfer: < 87 =50 >
saa7134[0]: i2c xfer: < c1 =79 >

However, this 86 00 60 00 00 should not happen on radio, IIRC.

Hi,

no, that standby isn't the problem.

saa7134[0]: i2c xfer: < 86 00 60 00 00 >
saa7134[0]: i2c xfer: < 86 00 4c 90 3d >
saa7134[0]: i2c xfer: < 86 00 60 00 00 >
saa7134[0]: i2c xfer: < 86 00 4c 90 3d >
saa7134[0]: i2c xfer: < 86 00 60 00 00 >
saa7134[0]: i2c xfer: < 86 00 4c 90 3d >
saa7134[0]: i2c xfer: < 86 00 4c 90 3d >
saa7134[0]: i2c xfer: < 86 00 4c 90 3d >
saa7134[0]: i2c xfer: < 86 00 60 00 00 >
saa7134[0]: i2c xfer: < 86 >
saa7134[0]: i2c xfer: < 86 01 02 >
saa7134[0]: i2c xfer: < 86 00 00 >
saa7134[0]: i2c xfer: < 86 07 >
saa7134[0]: i2c xfer: < 86 00 d6 30 >
tuner 2-0043: chip found @ 0x86 (saa7134[0])
saa7134[0]: i2c xfer: < 86 00 e2 00 00 >
saa7134[0]: i2c xfer: < 86 00 e2 00 00 >
saa7134[0]: i2c xfer: < 86 00 ce 90 3d >
saa7134[0]: i2c xfer: < 86 00 e2 00 00 >
saa7134[0]: i2c xfer: < 86 00 ce 90 3d >
saa7134[0]: i2c xfer: < 86 00 e2 00 00 >
saa7134[0]: i2c xfer: < 86 00 ce 90 3d >
saa7134[0]: i2c xfer: < 86 00 e2 00 00 >
saa7134[0]: i2c xfer: < 86 00 ce 90 3d >
saa7134[0]: i2c xfer: < 86 00 ce 90 3d >
saa7134[0]: i2c xfer: < 86 00 e2 00 00 >

It was always visible, but had suspects on the wrong end.

Automute is disabled. Why?

Should it be reenabled, at least for radio,
what I have now to get rid of this crazy noise,

static struct tvnorm radio_stereo = {
.name = "Radio Stereo",
.b = ( cFmRadio |
cQSS |
cAutoMuteFmActive ),
.c = ( cDFF |
cAudioGain6 |
cTopDefault),
.e = ( cTunerGainLow |
cAudioIF_5_5 |
cRadioIF_38_90 ),
};

static struct tvnorm radio_mono = {
.name = "Radio Mono",
.b = ( cFmRadio |
cQSS |
cAutoMuteFmActive ),
.c = ( cDN |
cDeemphasis75 |
cTopDefault),
.e = ( cTunerGainLow |
cAudioIF_5_5 |
cRadioIF_38_90 ),
};

or set per tuner?

Hi Guys,

this one is also not yet out of sight.

Recommended cAutoMuteFmActive should be set for radio.

I don't care much which way it is done,
but expect at least an argument why currently not.

Cheers,
Hermann

BTW, we have a broken Leadtek bttv remote, fixes have been suggested.
Guess that one is for Ricardo.

Em Ter, 2006-08-22 00:11 +0200, hermann pitton escreveu:
Am Samstag, den 15.07.2006, 00:52 +0200 schrieb hermann pitton:
Am Freitag, den 14.07.2006, 00:32 +0200 schrieb hermann pitton:

Hi Guys,

this one is also not yet out of sight.

Recommended cAutoMuteFmActive should be set for radio.

I don't care much which way it is done,
but expect at least an argument why currently not.
Hmm I think we should add a control for automute. Having this always
on is not a good idea, since, on areas where the radio signal is very
weak (or on boards with less sensitive tuners, like some Tenna/Ymec
ones), you may need to have this disabled.

Cheers,
Hermann

BTW, we have a broken Leadtek bttv remote, fixes have been suggested.
Guess that one is for Ricardo.

Cheers,
Mauro.

Am Dienstag, den 22.08.2006, 09:56 -0300 schrieb Mauro Carvalho Chehab:
Em Ter, 2006-08-22 *s 00:11 +0200, hermann pitton escreveu:
Am Samstag, den 15.07.2006, 00:52 +0200 schrieb hermann pitton:
Am Freitag, den 14.07.2006, 00:32 +0200 schrieb hermann pitton:

Hi Guys,

this one is also not yet out of sight.

Recommended cAutoMuteFmActive should be set for radio.

I don't care much which way it is done,
but expect at least an argument why currently not.
Hmm I think we should add a control for automute. Having this always
on is not a good idea, since, on areas where the radio signal is very
weak (or on boards with less sensitive tuners, like some Tenna/Ymec
ones), you may need to have this disabled.

Hi Mauro,

you are right. I'm focused too much in direction to get rid of the noise
I have. If I get some time I'll do some backward tests. The old win98
driver of the md7134 has automuteFM on I found, no noise, datasheet of
the FM1216ME MK3 recommends too.

BTW, we have a broken Leadtek bttv remote, fixes have been suggested.
Guess that one is for Ricardo.

, we seem to miss the PixelView PV-M4900 remote was meant.

Cheers,
Hermann

Em Ter, 2006-08-22 23:40 +0200, hermann pitton escreveu:
Am Dienstag, den 22.08.2006, 09:56 -0300 schrieb Mauro Carvalho Chehab:
Em Ter, 2006-08-22 00:11 +0200, hermann pitton escreveu:
Am Samstag, den 15.07.2006, 00:52 +0200 schrieb hermann pitton:
Am Freitag, den 14.07.2006, 00:32 +0200 schrieb hermann pitton:

, we seem to miss the PixelView PV-M4900 remote was meant.

Argh! I lost this thread due to a bounce detection (and other stuff
close to this)

If I understood well, the patch for fixing it is just:

diff -r d40504e3be14
Wed Aug 23 10:08:41 2006 -0300
Wed Aug 23 10:19:32 2006 -0300
@@ -304,6 +304,7 @@ int bttv_input_init(struct bttv *btv)
ir->mask_keyup = 0x010000;
ir->polling = 50; // ms
break;
+case BTTV_BARD_PV_M4900:
case BTTV_BARD_PV_BT878P_9B:
case BTTV_BARD_PV_BT878P_PLUS:
ir_codes = ir_codes_pixelview;

Right?

Cheers,
Mauro.

Am Mittwoch, den 23.08.2006, 10:20 -0300 schrieb Mauro Carvalho Chehab:
Em Ter, 2006-08-22 *s 23:40 +0200, hermann pitton escreveu:
Am Dienstag, den 22.08.2006, 09:56 -0300 schrieb Mauro Carvalho Chehab:
Em Ter, 2006-08-22 *s 00:11 +0200, hermann pitton escreveu:
Am Samstag, den 15.07.2006, 00:52 +0200 schrieb hermann pitton:
Am Freitag, den 14.07.2006, 00:32 +0200 schrieb hermann pitton:

, we seem to miss the PixelView PV-M4900 remote was meant.

Argh! I lost this thread due to a bounce detection (and other stuff
close to this)

If I understood well, the patch for fixing it is just:

diff -r d40504e3be14
Wed Aug 23 10:08:41 2006 -0300
Wed Aug 23 10:19:32 2006 -0300
@@ -304,6 +304,7 @@ int bttv_input_init(struct bttv *btv)
ir->mask_keyup = 0x010000;
ir->polling = 50; // ms
break;
+case BTTV_BARD_PV_M4900:
case BTTV_BARD_PV_BT878P_9B:
case BTTV_BARD_PV_BT878P_PLUS:
ir_codes = ir_codes_pixelview;

Right?

Yes.

As reported, only that was missing to get it back.

Cheers,
Hermann

Em Qua, 2006-08-23 15:52 +0200, hermann pitton escreveu:
Am Mittwoch, den 23.08.2006, 10:20 -0300 schrieb Mauro Carvalho Chehab:
, we seem to miss the PixelView PV-M4900 remote was meant.

+case BTTV_BARD_PV_M4900:
Right?

Yes.

As reported, only that was missing to get it back.

, patch applied. Thanks!

Cheers,
Mauro.