162306a36Sopenharmony_ci.. SPDX-License-Identifier: GPL-2.0 262306a36Sopenharmony_ci 362306a36Sopenharmony_ciDigital TV Conditional Access Interface 462306a36Sopenharmony_ci======================================= 562306a36Sopenharmony_ci 662306a36Sopenharmony_ci 762306a36Sopenharmony_ci.. note:: 862306a36Sopenharmony_ci 962306a36Sopenharmony_ci This documentation is outdated. 1062306a36Sopenharmony_ci 1162306a36Sopenharmony_ciThis document describes the usage of the high level CI API as 1262306a36Sopenharmony_ciin accordance to the Linux DVB API. This is a not a documentation for the, 1362306a36Sopenharmony_ciexisting low level CI API. 1462306a36Sopenharmony_ci 1562306a36Sopenharmony_ci.. note:: 1662306a36Sopenharmony_ci 1762306a36Sopenharmony_ci For the Twinhan/Twinhan clones, the dst_ca module handles the CI 1862306a36Sopenharmony_ci hardware handling. This module is loaded automatically if a CI 1962306a36Sopenharmony_ci (Common Interface, that holds the CAM (Conditional Access Module) 2062306a36Sopenharmony_ci is detected. 2162306a36Sopenharmony_ci 2262306a36Sopenharmony_cica_zap 2362306a36Sopenharmony_ci~~~~~~ 2462306a36Sopenharmony_ci 2562306a36Sopenharmony_ciA userspace application, like ``ca_zap`` is required to handle encrypted 2662306a36Sopenharmony_ciMPEG-TS streams. 2762306a36Sopenharmony_ci 2862306a36Sopenharmony_ciThe ``ca_zap`` userland application is in charge of sending the 2962306a36Sopenharmony_cidescrambling related information to the Conditional Access Module (CAM). 3062306a36Sopenharmony_ci 3162306a36Sopenharmony_ciThis application requires the following to function properly as of now. 3262306a36Sopenharmony_ci 3362306a36Sopenharmony_cia) Tune to a valid channel, with szap. 3462306a36Sopenharmony_ci 3562306a36Sopenharmony_ci eg: $ szap -c channels.conf -r "TMC" -x 3662306a36Sopenharmony_ci 3762306a36Sopenharmony_cib) a channels.conf containing a valid PMT PID 3862306a36Sopenharmony_ci 3962306a36Sopenharmony_ci eg: TMC:11996:h:0:27500:278:512:650:321 4062306a36Sopenharmony_ci 4162306a36Sopenharmony_ci here 278 is a valid PMT PID. the rest of the values are the 4262306a36Sopenharmony_ci same ones that szap uses. 4362306a36Sopenharmony_ci 4462306a36Sopenharmony_cic) after running a szap, you have to run ca_zap, for the 4562306a36Sopenharmony_ci descrambler to function, 4662306a36Sopenharmony_ci 4762306a36Sopenharmony_ci eg: $ ca_zap channels.conf "TMC" 4862306a36Sopenharmony_ci 4962306a36Sopenharmony_cid) Hopefully enjoy your favourite subscribed channel as you do with 5062306a36Sopenharmony_ci a FTA card. 5162306a36Sopenharmony_ci 5262306a36Sopenharmony_ci.. note:: 5362306a36Sopenharmony_ci 5462306a36Sopenharmony_ci Currently ca_zap, and dst_test, both are meant for demonstration 5562306a36Sopenharmony_ci purposes only, they can become full fledged applications if necessary. 5662306a36Sopenharmony_ci 5762306a36Sopenharmony_ci 5862306a36Sopenharmony_ciCards that fall in this category 5962306a36Sopenharmony_ci~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 6062306a36Sopenharmony_ci 6162306a36Sopenharmony_ciAt present the cards that fall in this category are the Twinhan and its 6262306a36Sopenharmony_ciclones, these cards are available as VVMER, Tomato, Hercules, Orange and 6362306a36Sopenharmony_ciso on. 6462306a36Sopenharmony_ci 6562306a36Sopenharmony_ciCI modules that are supported 6662306a36Sopenharmony_ci~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 6762306a36Sopenharmony_ci 6862306a36Sopenharmony_ciThe CI module support is largely dependent upon the firmware on the cards 6962306a36Sopenharmony_ciSome cards do support almost all of the available CI modules. There is 7062306a36Sopenharmony_cinothing much that can be done in order to make additional CI modules 7162306a36Sopenharmony_ciworking with these cards. 7262306a36Sopenharmony_ci 7362306a36Sopenharmony_ciModules that have been tested by this driver at present are 7462306a36Sopenharmony_ci 7562306a36Sopenharmony_ci(1) Irdeto 1 and 2 from SCM 7662306a36Sopenharmony_ci(2) Viaccess from SCM 7762306a36Sopenharmony_ci(3) Dragoncam 78