From: Roger James <roger@beardandsandals.co.uk>
To: linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] TT S2-3200 + CI Extension
Date: Mon, 25 Aug 2008 17:46:20 +0100 [thread overview]
Message-ID: <48B2E1DC.2080605@beardandsandals.co.uk> (raw)
In-Reply-To: <20080825122741.GB17421@optima.lan>
Martin Hurton wrote:
> Hi List,
>
> I have the TT-budget S2-3200 card with CI Extension and have problem
> to get it work with my CAM module. I have tried different CI Extensions,
> different CI cables, different CAM modules, and also different computers
> but still without any success. I am using multiproto driver.
>
> Debugging the driver I have found the problem is in the following code:
> (budget-ci.c).
>
> 507 ci_version = ttpci_budget_debiread(&budget_ci->budget, DEBICICTL, DEBIADDR_CIVERSION, 1, 1, 0);
> 508 if ((ci_version & 0xa0) != 0xa0) {
> 509 result = -ENODEV;
> 510 goto error;
> 511 }
>
> it seems the driver expects the high nibble of ci_version to be 0xa but in my case,
> the ci_version is always zero. And because of this, the CA is not supported.
>
> Did anybody have this same problem? Or can somebody explains why this happens?
> Any help will be greatly appreciated.
>
>
>
Martin,
I am investigating a simillar (but not the same) problem with a TT-3200
and a T-Rex/Dragon CAM (see my postings in the last week). I am
beginning to come to the conclusion that either I have a hardware
problem or the TT-3200 does not like certain CAMs, this is partially
born out by the fact the some incompatible cams are listed on the wiki
http://www.linuxtv.org/wiki/index.php/DVB_Conditional_Access_Modules . I
don't know whether this is a hardware or software (or both)
incompatibility. If it software it could be fixable. Does anyone know?
I did come across a post, which I have been unable to find again! This
referred to the fact that the Dragon CAM was asserting a line on PCMCIA
interface that said it was a low voltage device (3.5V) and that this was
outside the CI spec and causing a problem with the budget CI.
However this link says that it should work. I don't know if your CAM is
on it. I suspect this is referring to the supplied windows driver
http://www.dvbnetwork.de/index.php?option=com_fireboard&func=view&id=927&catid=2&Itemid=26
I would love to investigate further but really need some specs of the
software interface to the 3200. Can anyone point me at further info? All
I have at the momenet is the spec for the SAA7146 chip and the en50221
CI spec.
Sorry I cannot offer any direct help. But I thought you might like to
know you are not the only one fighting with this piece of hardware :-)
Roger
_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
next prev parent reply other threads:[~2008-08-25 16:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-25 12:27 [linux-dvb] TT S2-3200 + CI Extension Martin Hurton
2008-08-25 16:46 ` Roger James [this message]
2008-08-26 19:35 ` Werner Hauger
2008-08-27 9:19 ` Martin Hurton
2008-08-27 19:06 ` Werner Hauger
2008-08-27 10:01 ` Roger James
2008-08-27 18:47 ` Roger James
2008-08-27 19:38 ` Werner Hauger
2008-08-27 23:22 ` Roger James
2008-08-28 12:29 ` Roger James
2008-08-30 12:58 ` Roger James
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=48B2E1DC.2080605@beardandsandals.co.uk \
--to=roger@beardandsandals.co.uk \
--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