Hi Hermann
Many thanks for helping.
Unfortunately no joy with uploading the firmware on TDA10046, I have installed the v4l from the tarball, get the new firmware (issuing the tda10046lifeview on get_dvb_firmware) put the firmware in bot /usr/lib and /usr/lib/hotplug and change the line code on the saa7134-dvb.c in accordance with the advice reported on
As you mentioned, we most probably need a special config entry
for your card. As far as i know, it has no firmware eeprom for
the channel decoder.
To test this, you can try the following:
In saa7134-dvb.c, line 873, struct tda1004x_config philips_tiger_config
change the entry
.request_firmware = NULL,
to
.request_firmware = ,
The locaion of the firmware image depends on the distribution and
version you use. Its name is dvb-fe-tda10046.fw
Hartmut
The problem is the same when the scan start I got the following from dmesg
saa7130/34: v4l2 driver version 0.2.14 loaded
ACPI: PCI Interrupt 0000:02:0a.0[A] -Link [LNKC] -GSI 10 (level, low) -IRQ 10
saa7133[0]: found at 0000:02:0a.0, rev: 209, irq: 10, latency: 64, mmio: 0xfeaff800
saa7133[0]: subsystem: 1043:4876, board: ASUSTeK P7131 Dual [card=78,insmod option]
saa7133[0]: board init: gpio is 0
tuner 0-004b: chip found @ 0x96 (saa7133[0])
tuner 0-004b: setting tuner address to 61
tuner 0-004b: type set to tda8290+75a
saa7133[0]: i2c eeprom 00: 43 10 76 48 54 20 1c 00 43 43 a9 1c 55 d2 b2 92
saa7133[0]: i2c eeprom 10: ff ff ff 0f ff 20 ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 20: 01 40 01 02 03 01 01 03 08 ff 00 d5 ff ff ff ff
saa7133[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 40: ff 21 00 c2 96 10 03 32 55 50 ff ff ff ff ff ff
saa7133[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: registered device video0 [v4l2]
saa7133[0]: registered device vbi0
saa7133[0]: registered device radio0
DVB: registering new adapter (saa7133[0]).
DVB: registering frontend 0 (Philips TDA10046H DVB-T)
tda1004x: setting up plls for 48MHz sampling clock
tda1004x: timeout waiting for DSP ready
tda1004x: found firmware revision 0 -- invalid
tda1004x: booting from eeprom
tda1004x: timeout waiting for DSP ready
tda1004x: found firmware revision 0 -- invalid
tda1004x: firmware upload failed
I don't know if I made some mistake or misundertanding, (take care I'm a newbie)
Any further help will welcome
Thanks
Giuseppe
Initial Header

Hi Giuseppe,

Am Dienstag, den 05.09.2006, 23:29 +0200 schrieb
giuseppe.bortolan (AT) inwind (DOT) it:
Hi Hermann
Many thanks for helping.
Unfortunately no joy with uploading the firmware on TDA10046, I have installed the v4l from the tarball, get the new firmware (issuing the tda10046lifeview on get_dvb_firmware) put the firmware in bot /usr/lib and /usr/lib/hotplug and change the line code on the saa7134-dvb.c in accordance with the advice reported on

As you mentioned, we most probably need a special config entry
for your card. As far as i know, it has no firmware eeprom for
the channel decoder.
To test this, you can try the following:
In saa7134-dvb.c, line 873, struct tda1004x_config philips_tiger_config
change the entry
.request_firmware = NULL,
to
.request_firmware = ,

The locaion of the firmware image depends on the distribution and
version you use. Its name is dvb-fe-tda10046.fw

Hartmut

The problem is the same when the scan start I got the following from dmesg
saa7130/34: v4l2 driver version 0.2.14 loaded
ACPI: PCI Interrupt 0000:02:0a.0[A] -Link [LNKC] -GSI 10 (level, low) -IRQ 10
saa7133[0]: found at 0000:02:0a.0, rev: 209, irq: 10, latency: 64, mmio: 0xfeaff800
saa7133[0]: subsystem: 1043:4876, board: ASUSTeK P7131 Dual [card=78,insmod option]
saa7133[0]: board init: gpio is 0
tuner 0-004b: chip found @ 0x96 (saa7133[0])
tuner 0-004b: setting tuner address to 61
tuner 0-004b: type set to tda8290+75a
saa7133[0]: i2c eeprom 00: 43 10 76 48 54 20 1c 00 43 43 a9 1c 55 d2 b2 92
saa7133[0]: i2c eeprom 10: ff ff ff 0f ff 20 ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 20: 01 40 01 02 03 01 01 03 08 ff 00 d5 ff ff ff ff
saa7133[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 40: ff 21 00 c2 96 10 03 32 55 50 ff ff ff ff ff ff
saa7133[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: registered device video0 [v4l2]
saa7133[0]: registered device vbi0
saa7133[0]: registered device radio0
DVB: registering new adapter (saa7133[0]).
DVB: registering frontend 0 (Philips TDA10046H DVB-T)
tda1004x: setting up plls for 48MHz sampling clock
tda1004x: timeout waiting for DSP ready
tda1004x: found firmware revision 0 -- invalid
tda1004x: booting from eeprom
tda1004x: timeout waiting for DSP ready
tda1004x: found firmware revision 0 -- invalid
tda1004x: firmware upload failed

I don't know if I made some mistake or misundertanding, (take care I'm a newbie)
Any further help will welcome

did you recompile and install the modules and unload the old stuff?
You might try to reboot after the install.

Best would be anyway to try a mercurial snapshot from linuxtv.org, apply
the change and hopefully get it compiled with "make" and "make install"
on a distribution kernel.

Hm, on a previous report it also did not load it immediately.

Cheers,
Hermann

Hi,

Just to make it sure, the firmware have to be put in :
/usr/lib/hotplug/firmware or/and /lib/firmware (this one for me), and
not exactly what you've put in your email. I don't know if you make a
mistack writing the email or in your box
But I can confirm that only with this little modification it is working.

Regards and good luke.

2006/9/6, hermann pitton <hermann-pitton (AT) arcor (DOT) de>:
Hi Giuseppe,

Am Dienstag, den 05.09.2006, 23:29 +0200 schrieb
giuseppe.bortolan (AT) inwind (DOT) it:
Hi Hermann
Many thanks for helping.
Unfortunately no joy with uploading the firmware on TDA10046, I have installed the v4l from the tarball, get the new firmware (issuing the tda10046lifeview on get_dvb_firmware) put the firmware in bot /usr/lib and /usr/lib/hotplug and change the line code on the saa7134-dvb.c in accordance with the advice reported on

As you mentioned, we most probably need a special config entry
for your card. As far as i know, it has no firmware eeprom for
the channel decoder.
To test this, you can try the following:
In saa7134-dvb.c, line 873, struct tda1004x_config philips_tiger_config
change the entry
.request_firmware = NULL,
to
.request_firmware = ,

The locaion of the firmware image depends on the distribution and
version you use. Its name is dvb-fe-tda10046.fw

Hartmut

The problem is the same when the scan start I got the following from dmesg
saa7130/34: v4l2 driver version 0.2.14 loaded
ACPI: PCI Interrupt 0000:02:0a.0[A] -Link [LNKC] -GSI 10 (level, low) -IRQ 10
saa7133[0]: found at 0000:02:0a.0, rev: 209, irq: 10, latency: 64, mmio: 0xfeaff800
saa7133[0]: subsystem: 1043:4876, board: ASUSTeK P7131 Dual [card=78,insmod option]
saa7133[0]: board init: gpio is 0
tuner 0-004b: chip found @ 0x96 (saa7133[0])
tuner 0-004b: setting tuner address to 61
tuner 0-004b: type set to tda8290+75a
saa7133[0]: i2c eeprom 00: 43 10 76 48 54 20 1c 00 43 43 a9 1c 55 d2 b2 92
saa7133[0]: i2c eeprom 10: ff ff ff 0f ff 20 ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 20: 01 40 01 02 03 01 01 03 08 ff 00 d5 ff ff ff ff
saa7133[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 40: ff 21 00 c2 96 10 03 32 55 50 ff ff ff ff ff ff
saa7133[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: registered device video0 [v4l2]
saa7133[0]: registered device vbi0
saa7133[0]: registered device radio0
DVB: registering new adapter (saa7133[0]).
DVB: registering frontend 0 (Philips TDA10046H DVB-T)
tda1004x: setting up plls for 48MHz sampling clock
tda1004x: timeout waiting for DSP ready
tda1004x: found firmware revision 0 -- invalid
tda1004x: booting from eeprom
tda1004x: timeout waiting for DSP ready
tda1004x: found firmware revision 0 -- invalid
tda1004x: firmware upload failed

I don't know if I made some mistake or misundertanding, (take care I'm a newbie)
Any further help will welcome

did you recompile and install the modules and unload the old stuff?
You might try to reboot after the install.

Best would be anyway to try a mercurial snapshot from linuxtv.org, apply
the change and hopefully get it compiled with "make" and "make install"
on a distribution kernel.

Hm, on a previous report it also did not load it immediately.

Cheers,
Hermann
>
>
>
>

Am Mittwoch, den 06.09.2006, 14:39 +0200 schrieb Erik Beauvalot:
Hi,

Just to make it sure, the firmware have to be put in :
/usr/lib/hotplug/firmware or/and /lib/firmware (this one for me), and
not exactly what you've put in your email. I don't know if you make a
mistack writing the email or in your box
But I can confirm that only with this little modification it is working.

Regards and good luke.

Hi Erik,

thanks for confirmation!

Can at least see that there is also still an old variant of tda1004x and
not the new one within mercurial.

Does it come with a PC39 remote, since gpio0 doesn't indicate the
keydown like on the older one gpio init 0x40000?

Cheers,
Hermann

2006/9/6, hermann pitton <hermann-pitton (AT) arcor (DOT) de>:
Hi Giuseppe,

Am Dienstag, den 05.09.2006, 23:29 +0200 schrieb
giuseppe.bortolan (AT) inwind (DOT) it:
Hi Hermann
Many thanks for helping.
Unfortunately no joy with uploading the firmware on TDA10046, I have installed the v4l from the tarball, get the new firmware (issuing the tda10046lifeview on get_dvb_firmware) put the firmware in bot /usr/lib and /usr/lib/hotplug and change the line code on the saa7134-dvb.c in accordance with the advice reported on

As you mentioned, we most probably need a special config entry
for your card. As far as i know, it has no firmware eeprom for
the channel decoder.
To test this, you can try the following:
In saa7134-dvb.c, line 873, struct tda1004x_config philips_tiger_config
change the entry
.request_firmware = NULL,
to
.request_firmware = ,

The locaion of the firmware image depends on the distribution and
version you use. Its name is dvb-fe-tda10046.fw

Hartmut

The problem is the same when the scan start I got the following from dmesg
saa7130/34: v4l2 driver version 0.2.14 loaded
ACPI: PCI Interrupt 0000:02:0a.0[A] -Link [LNKC] -GSI 10 (level, low) -IRQ 10
saa7133[0]: found at 0000:02:0a.0, rev: 209, irq: 10, latency: 64, mmio: 0xfeaff800
saa7133[0]: subsystem: 1043:4876, board: ASUSTeK P7131 Dual [card=78,insmod option]
saa7133[0]: board init: gpio is 0
tuner 0-004b: chip found @ 0x96 (saa7133[0])
tuner 0-004b: setting tuner address to 61
tuner 0-004b: type set to tda8290+75a
saa7133[0]: i2c eeprom 00: 43 10 76 48 54 20 1c 00 43 43 a9 1c 55 d2 b2 92
saa7133[0]: i2c eeprom 10: ff ff ff 0f ff 20 ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 20: 01 40 01 02 03 01 01 03 08 ff 00 d5 ff ff ff ff
saa7133[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 40: ff 21 00 c2 96 10 03 32 55 50 ff ff ff ff ff ff
saa7133[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: registered device video0 [v4l2]
saa7133[0]: registered device vbi0
saa7133[0]: registered device radio0
DVB: registering new adapter (saa7133[0]).
DVB: registering frontend 0 (Philips TDA10046H DVB-T)
tda1004x: setting up plls for 48MHz sampling clock
tda1004x: timeout waiting for DSP ready
tda1004x: found firmware revision 0 -- invalid
tda1004x: booting from eeprom
tda1004x: timeout waiting for DSP ready
tda1004x: found firmware revision 0 -- invalid
tda1004x: firmware upload failed

I don't know if I made some mistake or misundertanding, (take care I'm a newbie)
Any further help will welcome

did you recompile and install the modules and unload the old stuff?
You might try to reboot after the install.

Best would be anyway to try a mercurial snapshot from linuxtv.org, apply
the change and hopefully get it compiled with "make" and "make install"
on a distribution kernel.

Hm, on a previous report it also did not load it immediately.

Cheers,
Hermann

Hi Herman,

Sorry for the lat answer, I was looking for the remote as I'm not
using it, it was lost .
Never mind, it is a PC-39 remote model. But I cannot tell you if it works.
I use the card with a DVB-S card with the (very good) software : VDR
to control all this world.

Regards.

Hi Erik,

thanks for confirmation!

Can at least see that there is also still an old variant of tda1004x and
not the new one within mercurial.

Does it come with a PC39 remote, since gpio0 doesn't indicate the
keydown like on the older one gpio init 0x40000?

Cheers,
Hermann

Hi Erik,

Am Samstag, den 09.09.2006, 15:02 +0200 schrieb Erik Beauvalot:
Hi Herman,

Sorry for the lat answer, I was looking for the remote as I'm not
using it, it was lost .
Never mind, it is a PC-39 remote model. But I cannot tell you if it works.
I use the card with a DVB-S card with the (very good) software : VDR
to control all this world.

Regards.

thanks again. Gunther has it also on the bttv-gallery for that one.

If somebody wants to test on it, the current version of Marc's and
Nickolay's patch is still here.

We need their sign and it might need some more cleaning,
but else it is working fine currently using rc5_key_timeout=50 as an
saa7134 option on my older 1043:4862 card.

Cheers,
Hermann

Hi Erik,

thanks for confirmation!

Can at least see that there is also still an old variant of tda1004x and
not the new one within mercurial.

Does it come with a PC39 remote, since gpio0 doesn't indicate the
keydown like on the older one gpio init 0x40000?

Cheers,
Hermann