From: Bas v.d. Wiel <bas@kompasmedia.nl>
To: linux-dvb@linuxtv.org
Subject: [linux-dvb] Mantis 2033: tuning still fails
Date: Mon, 14 Apr 2008 11:06:01 +0200 [thread overview]
Message-ID: <da94aba5e3e1f0c3c823a33d94b32f9b@localhost> (raw)
Hello all,
Slowly my Twinhan card is coming to life. Sadly though, tuning fails on all
frequencies. I saw a post on this subject from a few weeks ago. Changing
the tuner from tda10021 to tda10023 helped a lot in that case, but I have
absolutely no idea how to do this. I looked over a lot of source code to
see if I could find where the tuner chip gets determined, but to no avail.
My C skills aren't good enough I fear.. The output of dmesg shows this:
ACPI: PCI interrupt for device 0000:01:09.0 disabled
ACPI: PCI Interrupt 0000:01:09.0[A] -> Link [APC2] -> GSI 17 (level, low)
-> IRQ 20
irq: 20, latency: 32
memory: 0xfdeff000, mmio: 0xde8c4000
found a VP-2033 PCI DVB-C device on (01:09.0),
Mantis Rev 1 [1822:0008], irq: 20, latency: 32
memory: 0xfdeff000, mmio: 0xde8c4000
MAC Address=[00:08:ca:1b:e8:b8]
mantis_alloc_buffers (0): DMA=0x1d700000 cpu=0xdd700000 size=65536
mantis_alloc_buffers (0): RISC=0x1cd56000 cpu=0xdcd56000 size=1000
DVB: registering new adapter (Mantis dvb adapter)
mantis_frontend_init (0): Probing for CU1216 (DVB-C)
TDA10021: i2c-addr = 0x0c, id = 0x7d
mantis_frontend_init (0): found Philips CU1216 DVB-C frontend (TDA10021) @
0x0c
mantis_frontend_init (0): Mantis DVB-C Philips CU1216 frontend attach
success
DVB: registering frontend 0 (Philips TDA10021 DVB-C)...
CA: Registering Mantis Adapter(0) Slot(0)
Any help would be greatly appreciated!
Bas
_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
next reply other threads:[~2008-04-14 9:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-14 9:06 Bas v.d. Wiel [this message]
2008-04-17 20:11 ` [linux-dvb] Mantis 2033: tuning still fails Marko Ristola
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=da94aba5e3e1f0c3c823a33d94b32f9b@localhost \
--to=bas@kompasmedia.nl \
--cc=linux-dvb@linuxtv.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox