Steven Toth writes: > The simple thing about a solution like this is that: > a. a/t/szap -a <fenum> worked with zero changes. > b. The recent cx88 bus arbitration patches ensured that only one of > adapter0/fe0 or adapter1/fe could be opened at any one time. (As expected). > > I don't see solution #2 as a replacement for solution #1, but the > patches are pretty trivial and localised within a single framework. > > A few consideration: > > How will new or existing applications deal with solution#2? > Do any existing drivers deliver adapter0/fe0 and adapter0/fe1 and which > applications support that? > How do other products with multiple transport paths and frontends expose > their features in /dev/dvb? I am using the adapter0/fe[01] scheme in one driver right now. tzap/szap also works fine with that. Ralph _______________________________________________ linux-dvb mailing list linux-dvb@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
