From: Mauro Carvalho Chehab <mchehab@infradead.org>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: linux-media@vger.kernel.org, Henrik Kurelid <henrik@kurelid.se>
Subject: Re: [PATCH] firedtv: add parameter to fake ca_system_ids in CA_INFO
Date: Sat, 06 Mar 2010 10:52:37 -0300 [thread overview]
Message-ID: <4B925E25.2070105@infradead.org> (raw)
In-Reply-To: <tkrat.a8cdf995cdc06e83@s5r6.in-berlin.de>
Stefan Richter wrote:
> The Digital Everywhere firmware have the shortcoming that ca_info_enq and
> ca_info are not supported. This means that we can never retrieve the correct
> ca_system_id to present in the CI message CA_INFO. Currently the driver uses
> the application id retrieved using app_info_req and app_info, but this id
> only match the correct ca_system_id as given in ca_info in some cases.
> This patch adds a parameter to the driver in order for the user to override
> what will be returned in the CA_INFO CI message. Up to four ca_system_ids can
> be specified.
> This is needed for users with CAMs that have different manufacturer id and
> ca_system_id and that uses applications that take this into account, like
> MythTV.
This seems an ugly workaround. The better seems to patch MythTV to accept a different
CAM.
> +static int num_fake_ca_system_ids;
...
> + for (i = 0; i < num_fake_ca_system_ids; i++) {
> + app_info[4 + i * 2] =
> + (fake_ca_system_ids[i] >> 8) & 0xff;
...
NAK. If someone put an arbitrary high value for num_fake_ca_system_id's, it will write outside
the app_info array space, as the num_fake_ca_system_ids is not validated against the size
of app_info. Also, it makes no sense a negative value for this parameter.
--
Cheers,
Mauro
next prev parent reply other threads:[~2010-03-06 13:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-01 10:59 [PATCH] firedtv: correct version number and current/next in CA_PMT Stefan Richter
2010-03-01 11:03 ` [PATCH] firedtv: add parameter to fake ca_system_ids in CA_INFO Stefan Richter
2010-03-01 11:23 ` Stefan Richter
2010-03-01 11:56 ` [PATCH update] " Stefan Richter
2010-03-06 13:52 ` Mauro Carvalho Chehab [this message]
2010-03-06 14:10 ` [PATCH] " Stefan Richter
2010-03-06 14:14 ` Stefan Richter
2010-03-06 14:46 ` Mauro Carvalho Chehab
2010-03-06 14:43 ` Mauro Carvalho Chehab
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=4B925E25.2070105@infradead.org \
--to=mchehab@infradead.org \
--cc=henrik@kurelid.se \
--cc=linux-media@vger.kernel.org \
--cc=stefanr@s5r6.in-berlin.de \
/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