public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
* Re: [linux-dvb] HVR1200 / HVR1700 / TDA10048 support
@ 2008-04-20 21:33 Steven Ellis
  0 siblings, 0 replies; 11+ messages in thread
From: Steven Ellis @ 2008-04-20 21:33 UTC (permalink / raw)
  To: linux-dvb

On Sun, April 20, 2008 01:51, Steven Toth wrote:
> A couple of people have been asking about TDA10048 support, well it was
merged into master this morning. You can get the driver (and support for
the Hauppauge HVR1200 / HVR1700) here linuxtv.org/hg/v4l-dvb.
>
> Firmware for the TDA10048 can be extract from the windows driver,
everything you needs is here:
>
> steventoth.net/linux/hvr1200 or steventoth.net/linux/hvr1700
>

Awesome news. Thanks for the update.

Hope to hear a similar announcement about the HVR2200 soon(ish).

Steve



_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: [linux-dvb] HVR1200 / HVR1700 / TDA10048 support
@ 2008-04-21  3:02 Trevor Boon
  2008-04-21  5:10 ` Amitay Isaacs
  0 siblings, 1 reply; 11+ messages in thread
From: Trevor Boon @ 2008-04-21  3:02 UTC (permalink / raw)
  To: linux-dvb

Hi,

I have a Leadtek DTV1000s, which uses the tda10048,
and after compiling the latest build of v4l-dvb which
include the tda10048 support, the driver crashes upon
boot. 

I know the DTV100s is not yet officially supported,
however now that the nxp18271 and the tda10048 drivers
have been implemented, I thought I'd give it a go.

Using Kernel 2.6.25 on Ubuntu Hardy 8.04

I've already tried blacklisting the saa7134-alsa from
a previous driver crash. (I believe that has been
fixed however?)

As the dmesg output shows, I specified card=21 as this
worked for composite input previously. I've tried
other card numbers as well with the same result. No
card number just returns 0=autodetected (as expected)
but it doesn't try to load the tda10048 module and
therefore doesn't crash.

Is there anything else I can do to try and help
troubleshoot this issue/ expediate official dtv1000s
support?

Here's the dmesg output.

[   16.420527] Linux video capture interface: v2.00
[   16.668573] saa7130/34: v4l2 driver version 0.2.14
loaded
[   16.668681] ACPI: PCI Interrupt 0000:02:03.0[A] ->
GSI 18 (level, low) -> IRQ 18
[   16.668773] saa7130[0]: found at 0000:02:03.0, rev:
1, irq: 18, latency: 32, mmio: 0xc0021000
[   16.668836] saa7130[0]: subsystem: 107d:6655,
board: 10MOONS PCI TV CAPTURE CARD [card=21,insmod
option]
[   16.668903] saa7130[0]: board init: gpio is 22000
[   16.836163] saa7130[0]: i2c eeprom 00: 7d 10 55 66
54 20 1c 00 43 43 a9 1c 55 d2 b2 92
[   16.836719] saa7130[0]: i2c eeprom 10: 00 ff 82 0e
ff 20 ff ff ff ff ff ff ff ff ff ff
[   16.837268] saa7130[0]: i2c eeprom 20: 01 40 01 01
01 ff 01 03 08 ff 00 8a ff ff ff ff
[   16.837816] saa7130[0]: i2c eeprom 30: ff ff ff ff
ff ff ff ff ff ff ff ff ff ff ff ff
[   16.838366] saa7130[0]: i2c eeprom 40: ff 35 00 c0
00 10 03 02 ff 04 ff ff ff ff ff ff
[   16.838919] saa7130[0]: i2c eeprom 50: ff ff ff ff
ff ff ff ff ff ff ff ff ff ff ff ff
[   16.839466] saa7130[0]: i2c eeprom 60: ff ff ff ff
ff ff ff ff ff ff ff ff ff ff ff ff
[   16.840011] saa7130[0]: i2c eeprom 70: ff ff ff ff
ff ff ff ff ff ff ff ff ff ff ff ff
[   16.840606] saa7130[0]: i2c eeprom 80: ff ff ff ff
ff ff ff ff ff ff ff ff ff ff ff ff
[   16.841152] saa7130[0]: i2c eeprom 90: ff ff ff ff
ff ff ff ff ff ff ff ff ff ff ff ff
[   16.841697] saa7130[0]: i2c eeprom a0: ff ff ff ff
ff ff ff ff ff ff ff ff ff ff ff ff
[   16.842242] saa7130[0]: i2c eeprom b0: ff ff ff ff
ff ff ff ff ff ff ff ff ff ff ff ff
[   16.842789] saa7130[0]: i2c eeprom c0: ff ff ff ff
ff ff ff ff ff ff ff ff ff ff ff ff
[   16.843334] saa7130[0]: i2c eeprom d0: ff ff ff ff
ff ff ff ff ff ff ff ff ff ff ff ff
[   16.843881] saa7130[0]: i2c eeprom e0: ff ff ff ff
ff ff ff ff ff ff ff ff ff ff ff ff
[   16.844457] saa7130[0]: i2c eeprom f0: ff ff ff ff
ff ff ff ff ff ff ff ff ff ff ff ff
[   17.169977] Chip ID is not zero. It is not a
TEA5767
[   17.169977] tuner' 0-0060: chip found @ 0xc0
(saa7130[0])
[   16.692386] BUG: unable to handle kernel NULL
pointer dereference at 00000000
[   16.692386] IP: [<c020c2ea>] strlen+0xa/0x20
[   16.692386] *pde = 00000000 
[   16.692386] Oops: 0000 [#1] SMP 
[   16.692386] Modules linked in: tuner(+) tea5767
tda8290 tda18271 tda827x tuner_xc2028 xc5000 tda9887
tuner_simple mt20xx tea5761 serio_raw(+) psmouse
saa7134(+) videodev v4l1_compat compat_ioctl32
v4l2_common videobuf_dma_sg videobuf_core ir_kbd_i2c
ir_common tveeprom pcspkr i2c_core button iTCO_wdt
iTCO_vendor_support intel_agp shpchp pci_hotplug
agpgart evdev ext3 jbd mbcache sg sr_mod sd_mod cdrom
pata_acpi ata_piix ata_generic libata scsi_mod dock
r8169 ehci_hcd uhci_hcd usbcore thermal processor fan
fuse fbcon tileblit font bitblit softcursor
[   16.692386] 
[   16.692386] Pid: 3755, comm: modprobe Not tainted
(2.6.25-custom #1)
[   16.692386] EIP: 0060:[<c020c2ea>] EFLAGS: 00010246
CPU: 1
[   16.692386] EIP is at strlen+0xa/0x20
[   16.692386] EAX: 00000000 EBX: 00000014 ECX:
ffffffff EDX: 00000000
[   16.692386] ESI: 00000000 EDI: 00000000 EBP:
f7a44404 ESP: f7a79cfc
[   16.692386]  DS: 007b ES: 007b FS: 00d8 GS: 0033
SS: 0068
[   16.692386] Process modprobe (pid: 3755,
ti=f7a78000 task=f7bb0bc0 task.ti=f7a78000)
[   16.692386] Stack: f7a44400 c020a40f f795f400
f795f400 f7a44400 f795f400 f89f3f27 f7a79d48 
[   16.692386]        f79d3240 f4c06000 c01cd600
f4fbd978 c01cdc44 f7a79d58 f79d30f0 f79d3240 
[   16.692386]        00000004 00000036 f7a44400
f795f648 f89938b0 00000000 f7a44420 f7a44454 
[   16.692386] Call Trace:
[   16.692386]  [<c020a40f>] strlcpy+0x1f/0x60
[   16.692386]  [<f89f3f27>] set_type+0xd7/0x7d0
[tuner]
[   16.692386]  [<c01cd600>]
sysfs_ilookup_test+0x0/0x10
[   16.692386]  [<c01cdc44>]
sysfs_addrm_finish+0x14/0x1c0
[   16.692386]  [<f89938b0>]
saa7134_tuner_callback+0x0/0x100 [saa7134]
[   16.692386]  [<f89f55e8>]
tuner_command+0x6a8/0x1380 [tuner]
[   16.692386]  [<f89938b0>]
saa7134_tuner_callback+0x0/0x100 [saa7134]
[   16.692386]  [<c0303b6e>] klist_add_tail+0x1e/0x40
[   16.692386]  [<c02073bf>] kobject_get+0xf/0x20
[   16.692386]  [<c026bfce>] get_device+0xe/0x20
[   16.692386]  [<f899404e>] attach_inform+0x15e/0x200
[saa7134]
[   16.692386]  [<c026c44a>] device_add+0x2a/0x570
[   16.692386]  [<f89938b0>]
saa7134_tuner_callback+0x0/0x100 [saa7134]
[   16.692386]  [<f892eff4>]
i2c_attach_client+0xd4/0x150 [i2c_core]
[   16.692386]  [<f898d3f0>] v4l2_i2c_attach+0x60/0x90
[v4l2_common]
[   16.692386]  [<f89f46be>]
v4l2_i2c_drv_attach_legacy+0x1e/0x30 [tuner]
[   16.692386]  [<f89f4b10>] tuner_probe+0x0/0x430
[tuner]
[   16.692386]  [<f892ec1e>]
i2c_probe_address+0x3e/0x130 [i2c_core]
[   16.692386]  [<f892fcbb>] i2c_probe+0x1fb/0x210
[i2c_core]
[   16.692386]  [<f89f46a0>]
v4l2_i2c_drv_attach_legacy+0x0/0x30 [tuner]
[   16.692386]  [<f892fa70>]
i2c_device_remove+0x0/0x50 [i2c_core]
[   16.692386]  [<f89f46a0>]
v4l2_i2c_drv_attach_legacy+0x0/0x30 [tuner]
[   16.692386]  [<f892f315>]
i2c_register_driver+0xc5/0x120 [i2c_core]
[   16.692386]  [<f894a06a>]
v4l2_i2c_drv_init+0x6a/0xc9 [tuner]
[   16.692386]  [<c014a4bc>]
sys_init_module+0x11c/0x1b20
[   16.692386]  [<f892ed60>] i2c_master_send+0x0/0x50
[i2c_core]
[   16.692386]  [<c01087db>] sys_mmap2+0xcb/0xd0
[   16.692386]  [<c0104da4>]
sysenter_past_esp+0x6d/0xa9
[   16.692386]  [<c013007b>]
ptrace_request+0x22b/0x2c0
[   16.692386]  =======================
[   16.692386] Code: 00 56 89 c6 89 d0 88 c4 ac 38 e0
74 09 84 c0 75 f7 be 01 00 00 00 89 f0 48 5e c3 8d b6
00 00 00 00 57 b9 ff ff ff ff 89 c7 31 c0 <f2> ae f7
d1 49 5f 89 c8 c3 8d b6 00 00 00 00 8d bc 27 00 00 00 
[   16.692386] EIP: [<c020c2ea>] strlen+0xa/0x20
SS:ESP 0068:f7a79cfc
[   16.692391] ---[ end trace 3b4b6fb9b74102ec ]---
[   16.692530] tuner' 0-0060: Tuner has no way to set
tv freq
[   16.692581] tuner' 0-0060: Tuner has no way to set
tv freq
[   16.692675] saa7130[0]: registered device video0
[v4l2]
[   16.692754] saa7130[0]: registered device vbi0
[   16.692831] saa7130[0]: registered device radio0
[  191.107696] tuner' 0-0060: tuner has no way to set
radio frequency
[  191.839518] tuner' 0-0060: Tuner has no way to set
tv freq
[  191.129201] tuner' 0-0060: Tuner has no way to set
tv freq


      Get the name you always wanted with the new y7mail email address.
www.yahoo7.com.au/y7mail



_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: [linux-dvb] HVR1200 / HVR1700 / TDA10048 support
  2008-04-21  3:02 Trevor Boon
@ 2008-04-21  5:10 ` Amitay Isaacs
  0 siblings, 0 replies; 11+ messages in thread
From: Amitay Isaacs @ 2008-04-21  5:10 UTC (permalink / raw)
  To: linux-dvb


[-- Attachment #1.1: Type: text/plain, Size: 1643 bytes --]

Hi Trevor

On Mon, Apr 21, 2008 at 1:02 PM, Trevor Boon <trevor_boon@yahoo.com> wrote:

> Hi,
>
> I have a Leadtek DTV1000s, which uses the tda10048,
> and after compiling the latest build of v4l-dvb which
> include the tda10048 support, the driver crashes upon
> boot.
>
> I know the DTV100s is not yet officially supported,
> however now that the nxp18271 and the tda10048 drivers
> have been implemented, I thought I'd give it a go.
>
> Using Kernel 2.6.25 on Ubuntu Hardy 8.04
>
> I've already tried blacklisting the saa7134-alsa from
> a previous driver crash. (I believe that has been
> fixed however?)
>
> As the dmesg output shows, I specified card=21 as this
> worked for composite input previously. I've tried
> other card numbers as well with the same result. No
> card number just returns 0=autodetected (as expected)
> but it doesn't try to load the tda10048 module and
> therefore doesn't crash.
>
> Is there anything else I can do to try and help
> troubleshoot this issue/ expediate official dtv1000s
> support?


Leadtek card Winfast DTV1000S is currently not added in the DVB code.
I am attempting to add support for the card using the TDA10048 driver
committed by Steven. Since there is no other information available about
the DTV1000S card (other than it uses SAA7130, TDA18271 and TDA10048)
it's going to be a bit tricky getting all the bits together.

I could not find any documentation/details on adding support for new PCI
cards.
So going through various drivers to figure out the details. Can any one
point out
to a reference driver or any documentation which can be used to support a
new
PCI card?

Thanks.

Amitay.

[-- Attachment #1.2: Type: text/html, Size: 2025 bytes --]

[-- Attachment #2: Type: text/plain, Size: 150 bytes --]

_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: [linux-dvb] HVR1200 / HVR1700 / TDA10048 support
@ 2008-04-21  5:54 Trevor Boon
  2008-04-21  8:42 ` Amitay Isaacs
  0 siblings, 1 reply; 11+ messages in thread
From: Trevor Boon @ 2008-04-21  5:54 UTC (permalink / raw)
  To: linux-dvb

Hi Amitay,

Although, this is just speculation, the pcb label is
lr6655 which, afaik, is a Lifeview model code?

I've had a look at the driver inf file (lr6655.inf)
and can only see three files being used:

3xHybrid.sys
NXPMV32.dll
(34CoInstaller.dll) is remarked out in the lr6655.inf

I can also see 'Proteus' reference board being listed
in the driver .inf file. Does this help?



      Get the name you always wanted with the new y7mail email address.
www.yahoo7.com.au/y7mail



_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: [linux-dvb] HVR1200 / HVR1700 / TDA10048 support
  2008-04-21  5:54 Trevor Boon
@ 2008-04-21  8:42 ` Amitay Isaacs
  2008-04-21 13:19   ` hermann pitton
  0 siblings, 1 reply; 11+ messages in thread
From: Amitay Isaacs @ 2008-04-21  8:42 UTC (permalink / raw)
  To: linux-dvb


[-- Attachment #1.1: Type: text/plain, Size: 760 bytes --]

Hi Trevor,

I have the skeleton driver code ready. The driver calls tda10048_attach()
and I am
getting tda10048_readreg error (ret == -5). I need to find the demodulator
I2C address
for TDA10048 on DTV1000S board.

Is there any way to find out the demod_address?

Amitay.

On Mon, Apr 21, 2008 at 3:54 PM, Trevor Boon <trevor_boon@yahoo.com> wrote:

> Hi Amitay,
>
> Although, this is just speculation, the pcb label is
> lr6655 which, afaik, is a Lifeview model code?
>
> I've had a look at the driver inf file (lr6655.inf)
> and can only see three files being used:
>
> 3xHybrid.sys
> NXPMV32.dll
> (34CoInstaller.dll) is remarked out in the lr6655.inf
>
> I can also see 'Proteus' reference board being listed
> in the driver .inf file. Does this help?
>
>

[-- Attachment #1.2: Type: text/html, Size: 1063 bytes --]

[-- Attachment #2: Type: text/plain, Size: 150 bytes --]

_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: [linux-dvb] HVR1200 / HVR1700 / TDA10048 support
  2008-04-21  8:42 ` Amitay Isaacs
@ 2008-04-21 13:19   ` hermann pitton
  0 siblings, 0 replies; 11+ messages in thread
From: hermann pitton @ 2008-04-21 13:19 UTC (permalink / raw)
  To: Amitay Isaacs; +Cc: linux-dvb

Hi,

Am Montag, den 21.04.2008, 18:42 +1000 schrieb Amitay Isaacs:
> Hi Trevor,
> 
> I have the skeleton driver code ready. The driver calls
> tda10048_attach() and I am 
> getting tda10048_readreg error (ret == -5). I need to find the
> demodulator I2C address
> for TDA10048 on DTV1000S board. 
> 
> Is there any way to find out the demod_address?
> 
> Amitay.

tuner as in the logs 0xc0/0x60 and digital demod 0x10 >> 1 or 0x08.
You can try to verify it with the saa7134 i2c_scan=1 option.

It seems not to have an analog demodulator, so you would use tuner type
4, TUNER_ABSENT for the entry in saa7134-cards.c. You can also add it to
auto detection there as a saa7130 device and also add the card in
saa7134.h, but you seem to have this all already.

Cheers,
Hermann

> On Mon, Apr 21, 2008 at 3:54 PM, Trevor Boon <trevor_boon@yahoo.com>
> wrote:
>         Hi Amitay,
>         
>         Although, this is just speculation, the pcb label is
>         lr6655 which, afaik, is a Lifeview model code?
>         
>         I've had a look at the driver inf file (lr6655.inf)
>         and can only see three files being used:
>         
>         3xHybrid.sys
>         NXPMV32.dll
>         (34CoInstaller.dll) is remarked out in the lr6655.inf
>         
>         I can also see 'Proteus' reference board being listed
>         in the driver .inf file. Does this help?
>         



_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: [linux-dvb] HVR1200 / HVR1700 / TDA10048 support
       [not found] <mailman.73.1208797403.823.linux-dvb@linuxtv.org>
@ 2008-04-21 21:38 ` Trevor Boon
  2008-04-21 22:42   ` hermann pitton
  0 siblings, 1 reply; 11+ messages in thread
From: Trevor Boon @ 2008-04-21 21:38 UTC (permalink / raw)
  To: linux-dvb

Hi Amitay,

I specified the i2c_scan=1 option in my
/etc/modprobe.d/saa7134 file and the following
addresses were returned..

saa7130[0]: i2c scan: found device @ 0xa0  [eeprom]
saa7130[0]: i2c scan: found device @ 0xc0  [tuner
(analog)]

Regards,
Trevor.


      Get the name you always wanted with the new y7mail email address.
www.yahoo7.com.au/y7mail



_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: [linux-dvb] HVR1200 / HVR1700 / TDA10048 support
  2008-04-21 21:38 ` [linux-dvb] HVR1200 / HVR1700 / TDA10048 support Trevor Boon
@ 2008-04-21 22:42   ` hermann pitton
  2008-04-22  2:12     ` Steven Toth
  0 siblings, 1 reply; 11+ messages in thread
From: hermann pitton @ 2008-04-21 22:42 UTC (permalink / raw)
  To: Trevor Boon; +Cc: linux-dvb

Hi, Trevor and Amitay,

Am Dienstag, den 22.04.2008, 07:38 +1000 schrieb Trevor Boon:
> Hi Amitay,
> 
> I specified the i2c_scan=1 option in my
> /etc/modprobe.d/saa7134 file and the following
> addresses were returned..
> 
> saa7130[0]: i2c scan: found device @ 0xa0  [eeprom]
> saa7130[0]: i2c scan: found device @ 0xc0  [tuner
> (analog)]
> 
> Regards,
> Trevor.
> 

the 0x10 >> 1 for the digital demod is in the eeprom, if it follows
usual rules, at least the tuner is correct there.

Likely there are more possibilities, why the tda10048 does not appear,
powered off for example to safe energy, but since you also had a crash
previously, try a cold boot at first, means wait some time without any
power connected, depending on capacitors of the mobo, but 30 seconds
without any power should be always safe, and then just let it auto
detect card=0 without a tuner again and let i2c_scan=1 enabled one more
time.

If still the same, you are likely above that basic testing step and can
scratch heads on what doing next.

Good Luck,
Hermann









_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: [linux-dvb] HVR1200 / HVR1700 / TDA10048 support
  2008-04-21 22:42   ` hermann pitton
@ 2008-04-22  2:12     ` Steven Toth
  2008-04-22  3:07       ` Amitay Isaacs
  0 siblings, 1 reply; 11+ messages in thread
From: Steven Toth @ 2008-04-22  2:12 UTC (permalink / raw)
  To: Trevor Boon; +Cc: linux-dvb

hermann pitton wrote:
> Hi, Trevor and Amitay,
> 
> Am Dienstag, den 22.04.2008, 07:38 +1000 schrieb Trevor Boon:
>> Hi Amitay,
>>
>> I specified the i2c_scan=1 option in my
>> /etc/modprobe.d/saa7134 file and the following
>> addresses were returned..
>>
>> saa7130[0]: i2c scan: found device @ 0xa0  [eeprom]
>> saa7130[0]: i2c scan: found device @ 0xc0  [tuner
>> (analog)]
>>
>> Regards,
>> Trevor.
>>
> 
> the 0x10 >> 1 for the digital demod is in the eeprom, if it follows
> usual rules, at least the tuner is correct there.
> 
> Likely there are more possibilities, why the tda10048 does not appear,
> powered off for example to safe energy, but since you also had a crash
> previously, try a cold boot at first, means wait some time without any
> power connected, depending on capacitors of the mobo, but 30 seconds
> without any power should be always safe, and then just let it auto
> detect card=0 without a tuner again and let i2c_scan=1 enabled one more
> time.
> 
> If still the same, you are likely above that basic testing step and can
> scratch heads on what doing next.

If this doesn't work then you may need to drive a GPIO to being the part 
out of reset.

- Steve

_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: [linux-dvb] HVR1200 / HVR1700 / TDA10048 support
  2008-04-22  2:12     ` Steven Toth
@ 2008-04-22  3:07       ` Amitay Isaacs
  2008-04-22  3:19         ` Steven Toth
  0 siblings, 1 reply; 11+ messages in thread
From: Amitay Isaacs @ 2008-04-22  3:07 UTC (permalink / raw)
  To: linux-dvb, Steven Toth, Trevor Boon


[-- Attachment #1.1: Type: text/plain, Size: 4184 bytes --]

Hello everyone,

On Tue, Apr 22, 2008 at 12:12 PM, Steven Toth <stoth@linuxtv.org> wrote:

> hermann pitton wrote:
> > Hi, Trevor and Amitay,
> >
> > Am Dienstag, den 22.04.2008, 07:38 +1000 schrieb Trevor Boon:
> >> Hi Amitay,
> >>
> >> I specified the i2c_scan=1 option in my
> >> /etc/modprobe.d/saa7134 file and the following
> >> addresses were returned..
> >>
> >> saa7130[0]: i2c scan: found device @ 0xa0  [eeprom]
> >> saa7130[0]: i2c scan: found device @ 0xc0  [tuner
> >> (analog)]
> >>
> >> Regards,
> >> Trevor.
> >>
> >
> > the 0x10 >> 1 for the digital demod is in the eeprom, if it follows
> > usual rules, at least the tuner is correct there.
> >
> > Likely there are more possibilities, why the tda10048 does not appear,
> > powered off for example to safe energy, but since you also had a crash
> > previously, try a cold boot at first, means wait some time without any
> > power connected, depending on capacitors of the mobo, but 30 seconds
> > without any power should be always safe, and then just let it auto
> > detect card=0 without a tuner again and let i2c_scan=1 enabled one more
> > time.
> >
> > If still the same, you are likely above that basic testing step and can
> > scratch heads on what doing next.
>
> If this doesn't work then you may need to drive a GPIO to being the part
> out of reset.
>
> - Steve



Here is an update on the tests suggested on the list.

After a cold restart and with i2c_scan=1 options to saa7134 the output is as
follows.


[ 1638.631715] Linux video capture interface: v2.00
[ 1638.648219] saa7130/34: v4l2 driver version 0.2.14 loaded
[ 1638.649371] saa7130[0]: found at 0000:02:09.0, rev: 1, irq: 21, latency:
66, mmio: 0xf9e00000
[ 1638.649386] saa7130[0]: subsystem: 107d:6655, board: Leadtek Winfast
DTV-1000S [card=142,autodetected]
[ 1638.649406] saa7130[0]: board init: gpio is 222000
[ 1638.649409] saa7130[0]/core: hwinit1
[ 1638.798382] saa7130[0]: i2c eeprom 00: 7d 10 55 66 54 20 1c 00 43 43 a9
1c 55 d2 b2 92
[ 1638.798405] saa7130[0]: i2c eeprom 10: 00 ff 82 0e ff 20 ff ff ff ff ff
ff ff ff ff ff
[ 1638.798422] saa7130[0]: i2c eeprom 20: 01 40 01 01 01 ff 01 03 08 ff 00
8a ff ff ff ff
[ 1638.798440] saa7130[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff
ff ff ff ff ff
[ 1638.798457] saa7130[0]: i2c eeprom 40: ff 35 00 c0 00 10 03 02 ff 04 ff
ff ff ff ff ff
[ 1638.798474] saa7130[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff
ff ff ff ff ff
[ 1638.798491] saa7130[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff
ff ff ff ff ff
[ 1638.798508] saa7130[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff
ff ff ff ff ff
[ 1638.798524] saa7130[0]: i2c eeprom 80: ff ff ff ff ff ff ff ff ff ff ff
ff ff ff ff ff
[ 1638.798541] saa7130[0]: i2c eeprom 90: ff ff ff ff ff ff ff ff ff ff ff
ff ff ff ff ff
[ 1638.798558] saa7130[0]: i2c eeprom a0: ff ff ff ff ff ff ff ff ff ff ff
ff ff ff ff ff
[ 1638.798575] saa7130[0]: i2c eeprom b0: ff ff ff ff ff ff ff ff ff ff ff
ff ff ff ff ff
[ 1638.798592] saa7130[0]: i2c eeprom c0: ff ff ff ff ff ff ff ff ff ff ff
ff ff ff ff ff
[ 1638.798609] saa7130[0]: i2c eeprom d0: ff ff ff ff ff ff ff ff ff ff ff
ff ff ff ff ff
[ 1638.798626] saa7130[0]: i2c eeprom e0: ff ff ff ff ff ff ff ff ff ff ff
ff ff ff ff ff
[ 1638.798643] saa7130[0]: i2c eeprom f0: ff ff ff ff ff ff ff ff ff ff ff
ff ff ff ff ff
[ 1638.838381] saa7130[0]: i2c scan: found device @ 0xa0  [eeprom]
[ 1638.846378] saa7130[0]: i2c scan: found device @ 0xc0  [tuner (analog)]
[ 1638.852943] saa7130[0]/core: hwinit2
[ 1638.877459] saa7130[0]: registered device video0 [v4l2]
[ 1638.878602] saa7130[0]: registered device vbi0
[ 1638.879508] saa7130[0]: registered device radio0
[ 1638.999695] tda10048: tda10048_attach()
[ 1638.999705] tda10048: tda10048_readreg(reg = 0x00)
[ 1638.999883] tda10048_readreg: readreg error (ret == -5)
[ 1638.999955] saa7130[0]/dvb: frontend initialization failed

I2C scan reveals only tuner at 0xc0 and no tda10048.

I guess the next step is to try to drive a GPIO to bring the demod out of
reset as suggested by Steve.
Any suggestions on how to get GPIO addresses?

Also what are the contents of eeprom? Is there any useful information?

Amitay.

[-- Attachment #1.2: Type: text/html, Size: 4835 bytes --]

[-- Attachment #2: Type: text/plain, Size: 150 bytes --]

_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: [linux-dvb] HVR1200 / HVR1700 / TDA10048 support
  2008-04-22  3:07       ` Amitay Isaacs
@ 2008-04-22  3:19         ` Steven Toth
  0 siblings, 0 replies; 11+ messages in thread
From: Steven Toth @ 2008-04-22  3:19 UTC (permalink / raw)
  To: Amitay Isaacs; +Cc: Trevor Boon, linux-dvb

Amitay Isaacs wrote:
> Hello everyone,
> 
> On Tue, Apr 22, 2008 at 12:12 PM, Steven Toth <stoth@linuxtv.org 
> <mailto:stoth@linuxtv.org>> wrote:
> 
>     hermann pitton wrote:
>      > Hi, Trevor and Amitay,
>      >
>      > Am Dienstag, den 22.04.2008, 07:38 +1000 schrieb Trevor Boon:
>      >> Hi Amitay,
>      >>
>      >> I specified the i2c_scan=1 option in my
>      >> /etc/modprobe.d/saa7134 file and the following
>      >> addresses were returned..
>      >>
>      >> saa7130[0]: i2c scan: found device @ 0xa0  [eeprom]
>      >> saa7130[0]: i2c scan: found device @ 0xc0  [tuner
>      >> (analog)]
>      >>
>      >> Regards,
>      >> Trevor.
>      >>
>      >
>      > the 0x10 >> 1 for the digital demod is in the eeprom, if it follows
>      > usual rules, at least the tuner is correct there.
>      >
>      > Likely there are more possibilities, why the tda10048 does not
>     appear,
>      > powered off for example to safe energy, but since you also had a
>     crash
>      > previously, try a cold boot at first, means wait some time
>     without any
>      > power connected, depending on capacitors of the mobo, but 30 seconds
>      > without any power should be always safe, and then just let it auto
>      > detect card=0 without a tuner again and let i2c_scan=1 enabled
>     one more
>      > time.
>      >
>      > If still the same, you are likely above that basic testing step
>     and can
>      > scratch heads on what doing next.
> 
>     If this doesn't work then you may need to drive a GPIO to being the part
>     out of reset.
> 
>     - Steve
> 
> 
>  
> Here is an update on the tests suggested on the list.
> 
> After a cold restart and with i2c_scan=1 options to saa7134 the output 
> is as follows.
> 
> 
> [ 1638.631715] Linux video capture interface: v2.00
> [ 1638.648219] saa7130/34: v4l2 driver version 0.2.14 loaded
> [ 1638.649371] saa7130[0]: found at 0000:02:09.0, rev: 1, irq: 21, 
> latency: 66, mmio: 0xf9e00000
> [ 1638.649386] saa7130[0]: subsystem: 107d:6655, board: Leadtek Winfast 
> DTV-1000S [card=142,autodetected]
> [ 1638.649406] saa7130[0]: board init: gpio is 222000
> [ 1638.649409] saa7130[0]/core: hwinit1
> [ 1638.798382] saa7130[0]: i2c eeprom 00: 7d 10 55 66 54 20 1c 00 43 43 
> a9 1c 55 d2 b2 92
> [ 1638.798405] saa7130[0]: i2c eeprom 10: 00 ff 82 0e ff 20 ff ff ff ff 
> ff ff ff ff ff ff
> [ 1638.798422] saa7130[0]: i2c eeprom 20: 01 40 01 01 01 ff 01 03 08 ff 
> 00 8a ff ff ff ff
> [ 1638.798440] saa7130[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff 
> ff ff ff ff ff ff
> [ 1638.798457] saa7130[0]: i2c eeprom 40: ff 35 00 c0 00 10 03 02 ff 04 
> ff ff ff ff ff ff
> [ 1638.798474] saa7130[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff 
> ff ff ff ff ff ff
> [ 1638.798491] saa7130[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff 
> ff ff ff ff ff ff
> [ 1638.798508] saa7130[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff 
> ff ff ff ff ff ff
> [ 1638.798524] saa7130[0]: i2c eeprom 80: ff ff ff ff ff ff ff ff ff ff 
> ff ff ff ff ff ff
> [ 1638.798541] saa7130[0]: i2c eeprom 90: ff ff ff ff ff ff ff ff ff ff 
> ff ff ff ff ff ff
> [ 1638.798558] saa7130[0]: i2c eeprom a0: ff ff ff ff ff ff ff ff ff ff 
> ff ff ff ff ff ff
> [ 1638.798575] saa7130[0]: i2c eeprom b0: ff ff ff ff ff ff ff ff ff ff 
> ff ff ff ff ff ff
> [ 1638.798592] saa7130[0]: i2c eeprom c0: ff ff ff ff ff ff ff ff ff ff 
> ff ff ff ff ff ff
> [ 1638.798609] saa7130[0]: i2c eeprom d0: ff ff ff ff ff ff ff ff ff ff 
> ff ff ff ff ff ff
> [ 1638.798626] saa7130[0]: i2c eeprom e0: ff ff ff ff ff ff ff ff ff ff 
> ff ff ff ff ff ff
> [ 1638.798643] saa7130[0]: i2c eeprom f0: ff ff ff ff ff ff ff ff ff ff 
> ff ff ff ff ff ff
> [ 1638.838381] saa7130[0]: i2c scan: found device @ 0xa0  [eeprom]
> [ 1638.846378] saa7130[0]: i2c scan: found device @ 0xc0  [tuner (analog)]
> [ 1638.852943] saa7130[0]/core: hwinit2
> [ 1638.877459] saa7130[0]: registered device video0 [v4l2]
> [ 1638.878602] saa7130[0]: registered device vbi0
> [ 1638.879508] saa7130[0]: registered device radio0
> [ 1638.999695] tda10048: tda10048_attach()
> [ 1638.999705] tda10048: tda10048_readreg(reg = 0x00)
> [ 1638.999883] tda10048_readreg: readreg error (ret == -5)
> [ 1638.999955] saa7130[0]/dvb: frontend initialization failed
> 
> I2C scan reveals only tuner at 0xc0 and no tda10048.
> 
> I guess the next step is to try to drive a GPIO to bring the demod out 
> of reset as suggested by Steve.
> Any suggestions on how to get GPIO addresses?

saa7134-cards.c func saa7134_xc2028_callback(), this is example code 
that toggles the gpio specific for a 2028 tuner on another card, the 
mechanism and registers will be similar to this.

- Steve

_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

^ permalink raw reply	[flat|nested] 11+ messages in thread

end of thread, other threads:[~2008-04-22  3:20 UTC | newest]

Thread overview: 11+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
     [not found] <mailman.73.1208797403.823.linux-dvb@linuxtv.org>
2008-04-21 21:38 ` [linux-dvb] HVR1200 / HVR1700 / TDA10048 support Trevor Boon
2008-04-21 22:42   ` hermann pitton
2008-04-22  2:12     ` Steven Toth
2008-04-22  3:07       ` Amitay Isaacs
2008-04-22  3:19         ` Steven Toth
2008-04-21  5:54 Trevor Boon
2008-04-21  8:42 ` Amitay Isaacs
2008-04-21 13:19   ` hermann pitton
  -- strict thread matches above, loose matches on Subject: below --
2008-04-21  3:02 Trevor Boon
2008-04-21  5:10 ` Amitay Isaacs
2008-04-20 21:33 Steven Ellis

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox