Oliver Endriss schreef op Sun 03-07-2011 om 23:27 [+0200]: > Update Kconfig description (ddbridge with cxd2099) > > Signed-off-by: Oliver Endriss <o.endr...@gmx.de> > --- > drivers/staging/cxd2099/Kconfig | 11 ++++++----- > 1 files changed, 6 insertions(+), 5 deletions(-) > > diff --git a/drivers/staging/cxd2099/Kconfig b/drivers/staging/cxd2099/Kconfig > index 9d638c3..b48aefd 100644 > --- a/drivers/staging/cxd2099/Kconfig > +++ b/drivers/staging/cxd2099/Kconfig > @@ -1,9 +1,10 @@ > config DVB_CXD2099 > - tristate "CXD2099AR Common Interface driver" > - depends on DVB_CORE && PCI && I2C && DVB_NGENE > - ---help--- > - Support for the CI module found on cineS2 DVB-S2, supported by > - the Micronas PCIe device driver (ngene). > + tristate "CXD2099AR Common Interface driver" > + depends on DVB_CORE && PCI && I2C > + ---help--- > + Support for the CI module found on cards based on > + - Micronas ngene PCIe bridge: cineS2 etc. > + - Digital Devices PCIe bridge: Octopus series > > For now, data is passed through '/dev/dvb/adapterX/sec0': > - Encrypted data must be written to 'sec0'. Hi Oliver, => can you explain a bit more on "data is passed through '/dev/dvb/adapterX/sec0':"
How is the idea behind the setup? Is each adapter having its own sec0? Walter -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
