Mailing List archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[vdr] Re: CAM Aston 1.05 workaround
- To: vdr@linuxtv.org
- Subject: [vdr] Re: CAM Aston 1.05 workaround
- From: Klaus Schmidinger <Klaus.Schmidinger@cadsoft.de>
- Date: Sun, 07 Sep 2003 16:43:28 +0200
- Content-type: text/plain; charset=us-ascii
- Organization: CadSoft Computer GmbH
- References: <1058777636.2099.6.camel@darwin.roma1.infn.it> <3F2281E5.517D7357@cadsoft.de> <1059459115.2120.8.camel@darwin.roma1.infn.it> <3F2BBF1C.82D3CB4E@cadsoft.de> <1059944076.2151.3.camel@darwin.roma1.infn.it> <01f401c35a02$e6f90620$0c01010a@lappland> <3F34DDB0.F7301753@cadsoft.de> <003f01c35e70$1157a310$0c01010a@lappland> <3F34E74C.35C7B59A@cadsoft.de> <012101c35eb8$0ae0e490$0c01010a@lappland> <1060502061.3406.8.camel@darwin.roma1.infn.it> <3F360B28.7AF8929@cadsoft.de> <1060576096.2123.1.camel@darwin.roma1.infn.it> <3F374762.20866489@cadsoft.de> <1060838872.2154.3.camel@darwin.roma1.infn.it> <3F3CF11C.65C23333@cadsoft.de> <1061122891.5293.49.camel@darwin.roma1.infn.it> <3F51D59D.50F4E2FF@cadsoft.de> <3F577E83.10707@ieee.org>
- Reply-to: vdr@linuxtv.org
- Sender: vdr-bounce@linuxtv.org
Miguel Sanchez wrote:
>
> Hi Klaus,
>
> I've done some debugging on the Aston 1.05 CAM problem. As it works
> (decrypts successfully) with Hauppauge Windows software and DVBTV, I've
> included what I think it is the dialog between the CAM and the card
> software:
>
> ...
> Klaus: If this is not useful, do you know any other test I could conduct
> to help you figure out what the problem could be?
I'm afraid this didn't give me any new insights.
I just posted this in an other thread regarding the SkyCrypt CAM, but maybe
you could do the same tests:
Please take VDR 1.2.5pre2, the latest CVS driver (both available
in ftp://ftp.cadsoft.de/vdr/Developer) and apply this patch
to VDR/dvbdevice.c:
--- dvbdevice.c 2003/09/06 13:19:33 1.64
+++ dvbdevice.c 2003/09/07 14:28:00
@@ -272,20 +272,29 @@
if (ciHandler) {
if (ciHandler->Process() && useCa) {
if (tunerStatus != tsCam) {//XXX TODO update in case the CA descriptors have changed
+ static bool CaMode = false;
for (int Slot = 0; Slot < ciHandler->NumSlots(); Slot++) {
uchar buffer[2048];
int length = cSIProcessor::GetCaDescriptors(channel.Source(), channel.Frequency(), channel.Sid(), ciHandler->GetCaSystemIds(Slot), sizeof(buffer), buffer);
if (length > 0) {
cCiCaPmt CaPmt(channel.Sid());
- CaPmt.AddCaDescriptor(length, buffer);
- if (channel.Vpid())
+ if (!CaMode) CaPmt.AddCaDescriptor(length, buffer);
+ if (channel.Vpid()) {
CaPmt.AddPid(channel.Vpid());
- if (channel.Apid1())
+ if (CaMode) CaPmt.AddCaDescriptor(length, buffer);
+ }
+ if (channel.Apid1()) {
CaPmt.AddPid(channel.Apid1());
- if (channel.Apid2())
+ if (CaMode) CaPmt.AddCaDescriptor(length, buffer);
+ }
+ if (channel.Apid2()) {
CaPmt.AddPid(channel.Apid2());
- if (channel.Dpid1())
+ if (CaMode) CaPmt.AddCaDescriptor(length, buffer);
+ }
+ if (channel.Dpid1()) {
CaPmt.AddPid(channel.Dpid1());
+ if (CaMode) CaPmt.AddCaDescriptor(length, buffer);
+ }
if (ciHandler->SetCaPmt(CaPmt, Slot)) {
tunerStatus = tsCam;
startTime = 0;
With this version please try receiving encrypted channels, once leaving 'CaMode'
at the value 'false', then setting it to true.
Can you observe a different behaviour in the two cases?
Does it work in any of them?
NB: make sure you use the LL firmware (the logfile should list "...firmware supports
CI link layer interface").
Klaus
--
Info:
To unsubscribe send a mail to ecartis@linuxtv.org with "unsubscribe vdr" as subject.
Home |
Main Index |
Thread Index