S2API: Difference between revisions

From LinuxTVWiki
Jump to navigation Jump to search
Line 15: Line 15:


The development repository is at http://linuxtv.org/hg/~stoth/s2 and a tuning application is at http://www.steventoth.net/linux/s2/. Work still needs to be done to finish the API design and port the existing DVB-S2 drivers to work with it. Older
The development repository is at http://linuxtv.org/hg/~stoth/s2 and a tuning application is at http://www.steventoth.net/linux/s2/. Work still needs to be done to finish the API design and port the existing DVB-S2 drivers to work with it. Older
drivers not requiring the new features can remain unchanged. Support for the
drivers not requiring the new features can remain unchanged. Device support in the tree currently
cx24116 demodulator driver and the [[Hauppauge_WinTV-HVR-4000]] family of DVB-S2 products is now in the tree.
includes the cx24116 demodulator driver and the [[Hauppauge_WinTV-HVR-4000]] family of DVB-S2 products,
and the TeVii S460, which have been tested successfully using the new API.
A small patch which adds support for the TeVii S460 has been
posted at http://linuxtv.org/pipermail/linux-dvb/2008-September/028544.html and will probably be added to the
(http://linuxtv.org/pipermail/linux-dvb/2008-September/028544.html).
tree soon.


Driver code is largely independent of the API used, and hooking up an existing driver to work with a
Driver code is largely independent of the API used, and hooking up an existing driver to work with a

Revision as of 16:09, 8 September 2008

S2API is a tag/value-based API which is a proposal for version 3.3 of the Linux DVB API, adding support for new DVB transmission standards including DVB-S2. It is currently under rapid development with the intention of merging it into the Linux kernel soon.

Introduction

Following long standing frustration amongst developers and users about the lack of progress in getting multiproto into the Linux kernel, a group of four senior developers including the maintainer has proposed an alternative (Aug 29 2008) and announced that they no longer support multiproto. See http://linuxtv.org/pipermail/linux-dvb/2008-August/028313.html. The idea had been proposed earlier http://linuxtv.org/pipermail/linux-dvb/2007-November/021618.html. See also http://article.gmane.org/gmane.linux.drivers.dvb/36643.

Technically it is quite different from multiproto. Control of the frontend is implemented using a command sequence of (tag,value) pairs to set all the required parameters and then initiate tuning. Thus it no longer depends on fixed structs to hold parameter data.

A notable advantage of the tag/value technique is that it should make it much easier to keep up with future DVB transmission standards because this will at most require the definition of additional tags (i.e. commands) rather than a revision of the API. Transmission standards continue to multiply: some developers already have hardware using standards unsupported by multiproto, such as ISDB-T and DMB-T/H.

Commands can be made atomic by passing a whole command sequence in a single ioctl (for example a set of parameters followed by the tune command). Alternatively a sequence may be sent one command at a time. S2API thus offers an extra degree of flexibility over a multiproto-style approach, and the better application-to-driver communication could potentially be exploited for more advanced application functionality in in the future.

The development repository is at http://linuxtv.org/hg/~stoth/s2 and a tuning application is at http://www.steventoth.net/linux/s2/. Work still needs to be done to finish the API design and port the existing DVB-S2 drivers to work with it. Older drivers not requiring the new features can remain unchanged. Device support in the tree currently includes the cx24116 demodulator driver and the Hauppauge_WinTV-HVR-4000 family of DVB-S2 products, and the TeVii S460, which have been tested successfully using the new API. (http://linuxtv.org/pipermail/linux-dvb/2008-September/028544.html).

Driver code is largely independent of the API used, and hooking up an existing driver to work with a different API is quite simple (much easier than writing the driver in the first place), so this can be expected to progress rapidly. Similarly, for application code (e.g. Kaffeine, MythTV or VDR) the number of lines of code required to tune to a channel is small, and can easily be changed for a different API.

S2API will be reviewed at the Linux Plumbers' Conference in September 2008: http://linuxplumbersconf.org/program/microconfs/getmc.php?mc=chehab08.