Re: Confusion about API: please clarify

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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 <jw@xxxxxxxxxxxxx> escreveu:
> > 
> > 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 anything that looks
> > like tag/value.
> 
> That refers basically to DVB frontend API. Please see:
> 	https://www.linuxtv.org/downloads/v4l-dvb-apis-new/uapi/dvb/dvbproperty.html

Thanks for the clarification, Mauro!

So all the other "subsystems" (like demux device etc/pp) still use the struct
based API?

What about DiSEqC? struct dvb_diseqc_master_cmd seems to still be limited to 6
bytes. With Unicable/JESS longer sequences are needed. Especially for configuring
multiswitches, sequences of up to 16 bytes are needed. How would this be done
with the limitation to 6 bytes?

Thanks,

-- 
Josef Wolf
jw@xxxxxxxxxxxxx



[Index of Archives]     [Linux Input]     [Video for Linux]     [Gstreamer Embedded]     [Mplayer Users]     [Linux USB Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]
  Powered by Linux