Andreas Oberritter writes: > 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? > They should be in different adapterX directories. Even on the cards where you can connect up to 4 dual frontends or CAM adapters I currently use one adapter directory for every frontend and CAM. If you want to "save" adapters one could put them in the same directory and caX would belong to camX. More ca than cam devices could only occur on cards with mixed old and new style hardware. I am not aware of such cards. I think there are cards with dual frontend and two CAM adapters where normally data from frontendX is passed through caX (they are in the same adapter directory) but the paths can also be switched. I do not now how this is handled. Regards, Ralph -- 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
