Re: Confusion about API: please clarify

2018-04-12 Thread Josef Wolf
On Di, Apr 10, 2018 at 05:22:39 -0300, Mauro Carvalho Chehab wrote: > That's said, adding suport for DiSEqC with more than 6 bytes should > likely be enabled driver per driver, after checking that the device > supports it. Do you know which length saa7146/stv0299 could do? -- Josef Wolf

Re: Confusion about API: please clarify

2018-04-10 Thread Mauro Carvalho Chehab
Em Tue, 10 Apr 2018 21:14:23 +0200 Josef Wolf escreveu: > On Di, Apr 10, 2018 at 11:58:15 -0300, Mauro Carvalho Chehab wrote: > > Em Tue, 10 Apr 2018 12:43:27 +0200 > > Josef Wolf escreveu: > > > > > > The linuxtv wiki pages state that the current v5

Re: Confusion about API: please clarify

2018-04-10 Thread Josef Wolf
On Di, Apr 10, 2018 at 11:58:15 -0300, Mauro Carvalho Chehab wrote: > Em Tue, 10 Apr 2018 12:43:27 +0200 > Josef Wolf escreveu: > > > > The linuxtv wiki pages state that the current v5 API (also called S2API) is > > tag/value based: > > > > > >

Re: Confusion about API: please clarify

2018-04-10 Thread Mauro Carvalho Chehab
Em Tue, 10 Apr 2018 12:43:27 +0200 Josef Wolf escreveu: > Hello, > > The linuxtv wiki pages state that the current v5 API (also called S2API) is > tag/value based: > > > https://www.linuxtv.org/wiki/index.php/Development:_Linux_DVB_API_history_and_future >

Confusion about API: please clarify

2018-04-10 Thread Josef Wolf
Hello, The linuxtv wiki pages state that the current v5 API (also called S2API) is tag/value based: https://www.linuxtv.org/wiki/index.php/Development:_Linux_DVB_API_history_and_future https://www.linuxtv.org/wiki/index.php/S2API But in the API documentation (version 5.10), I can't find