From: Andreas Oberritter <obi@xxxxxxxxxxx> > Also, there's still no mapping between ca and caio devices. Imagine a > built-in descrambler ca0 and two CI slots ca1 and ca2. > > ca0 won't get a caio device, at least for now. > ca1 and ca2 might or might not have a caio device. > > If there is caio0, how am I supposed to know that it's related to ca1 or > ca2 (or ca0, if someone implements a caio device to bypass the software > demux to use a built-in descrambler)? You must not assume that there are > either none or two (or three) caio interfaces. You need to be able to > detect (or set up) the connection between the interfaces. Otherwise this > "API" will be a mess. > > Regards, > Andreas To my understanding, in such a described case, - ca0 would be reached from /dev/dvb/adapter0/ca0 - ca[12], depending on if they are connected to the same physical adapter (PCI, USB, ...), would be reached from /dev/dvb/adapter1/ca[12] or /dev/dvb/adapter1/ca1 and /dev/dvb/adapter2/ca2 and there respective caio devices. - If the 3 ca devices are on the same adapter, then the driver writer should take care of the order of the mapping so that ca1 always map caio1 and ca2/caio2, ...; and if this is not feasable, then the driver writer should span the ca/caio devices on different /dev/dvb/adapter folders. -- 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
