Yeah, Andrew and I already got a taste of that. We tried 3 different CAMs so far (Andrew tried one, I tried two others), and they all behave differently on the physical layer already. One type of CAM, Neotion's Free-X TV / ZetaCAM, is downright physically _incompatible_ with the Budget-CI and cannot be used with it (I sent in my Budget-CI and CAM to TT and they confirmed that it doesn't work and that there is no software workaround possible).
We've been figuring out an initialisation method which works for the CAMs we have (Neotion's only until the first I/O access, at which it no longer works right), but it's possible that other CAMs may behave in non-standard ways we haven't experienced yet. EN50221 must be one of the most violated standards in existence. I wonder why manufacturers have such difficulties understanding it... :( Regards, -- Robert Schlabbach e-mail: [EMAIL PROTECTED] Berlin, Germany ----- Original Message ----- From: "Jerico Webmail" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Saturday, March 27, 2004 11:40 PM Subject: [linux-dvb] CAM interfacing. > Hi, > > With respect to CAM's, I don't know how much of a discussion has been made about > interfacing with different manufacturers modules but having been in the > position to speak to a number of manufacturers I thought I might just feed back > a point that many have them made. > > Aparently interoperability is one of the biggest challenges of working with > CAM's. A French developer has had great challeges implementing decoding of > Conax despite having already integrated another CA system into their product. > Also an associate at Conax has said to me that they often exchange hardware > prototypes with developers just so they can ensure correct compatability. > > So just be aware that not all CAM's talk the same way as we would like them to > do. > > Bob -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as subject.
