Oliver Endriss wrote:
Hi,
On Saturday 12 March 2011 14:29:08 Andreas Oberritter wrote:
On 03/11/2011 10:44 PM, Martin Vidovic wrote:
Andreas Oberritter wrote:
It's rather unintuitive that some CAMs appear as ca0, while others as
cam0.
Ngene CI appears as both ca0 and cam0 (or sec0). The ca0 node is used
as usual, to setup the CAM. The cam0 (or sec0) node is used to read/write
transport stream. To me it looks like an extension of the current API.
I see. This raises another problem. How to find out, which ca device
cam0 relates to, in case there are more ca devices than cam devices?
Hm, I do not see a problem here. The API extension is simple:
(1) camX is optional. If camX exists, it is tied to caX.
(2) If there is no camX, the CI/CAM operates in 'legacy mode'.
(3) If camX exists, the encrypted transport stream of the CI/CAM is sent
through camX, and the decrypted stream is received from camX.
caX behaves the same way as in (2).
Btw, we should choose a more meaningful name for 'camX'.
I would prefer something like cainoutX or caioX or cinoutX or cioX.
I agree, camX could be misleading since it's not necessarily a CAM
application.
According to EN 50221 the two interfaces are named Command Interface
(for caX)
and Transport Stream Interface (for camX). Then maybe 'tsiX' would be an
appropriate
name?
Anyway, 'cioX' sounds good too.
Regards,
Martin
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
