&sub-dvbproperty;
Frontend Function CallsDVB frontend open()
&manvol;
fe-openOpen a frontend device#include <fcntl.h>int openconst char *device_nameint flagsArgumentsdevice_nameDevice to be opened.flagsOpen flags. Access can either be
O_RDWR or O_RDONLY.Multiple opens are allowed with O_RDONLY. In this mode, only query and read ioctls are allowed.Only one open is allowed in O_RDWR. In this mode, all ioctls are allowed.When the O_NONBLOCK flag is given, the system calls may return &EAGAIN; when no data is available or when the device driver is temporarily busy.Other flags have no effect.DescriptionThis system call opens a named frontend device (/dev/dvb/adapter?/frontend?)
for subsequent use. Usually the first thing to do after a successful open is to
find out the frontend type with FE_GET_INFO.The device can be opened in read-only mode, which only allows monitoring of
device status and statistics, or read/write mode, which allows any kind of use
(e.g. performing tuning operations.)
In a system with multiple front-ends, it is usually the case that multiple devices
cannot be open in read/write mode simultaneously. As long as a front-end
device is opened in read/write mode, other open() calls in read/write mode will
either fail or block, depending on whether non-blocking or blocking mode was
specified. A front-end device opened in blocking mode can later be put into
non-blocking mode (and vice versa) using the F_SETFL command of the fcntl
system call. This is a standard system call, documented in the Linux manual
page for fcntl. When an open() call has succeeded, the device will be ready
for use in the specified mode. This implies that the corresponding hardware is
powered up, and that other front-ends may have been powered down to make
that possible.Return ValueOn success open returns the new file
descriptor. On error -1 is returned, and the errno
variable is set appropriately. Possible error codes are:EACCESThe caller has no permission to access the
device.EBUSYThe the device driver is already in use.ENXIONo device corresponding to this device special file
exists.ENOMEMNot enough kernel memory was available to complete the
request.EMFILEThe process already has the maximum number of
files open.ENFILEThe limit on the total number of files open on the
system has been reached.ENODEVThe device got removed.DVB frontend close()
&manvol;
fe-closeClose a frontend device#include <unistd.h>int closeint fdArgumentsfd&fd;DescriptionThis system call closes a previously opened front-end device. After closing
a front-end device, its corresponding hardware might be powered down
automatically.Return ValueThe function returns 0 on
success, -1 on failure and the
errno is set appropriately. Possible error
codes:EBADFfd is not a valid open file
descriptor.
&sub-fe-get-info;
&sub-fe-read-status;
&sub-fe-get-property;
&sub-fe-diseqc-reset-overload;
&sub-fe-diseqc-send-master-cmd;
&sub-fe-diseqc-recv-slave-reply;
&sub-fe-diseqc-send-burst;
&sub-fe-set-tone;
&sub-fe-set-voltage;
&sub-fe-enable-high-lnb-voltage;
&sub-fe-set-frontend-tune-mode;
DVB Frontend legacy API (a. k. a. DVBv3)The usage of this API is deprecated, as it doesn't support all digital
TV standards, doesn't provide good statistics measurements and provides
incomplete information. This is kept only to support legacy applications.
&sub-frontend_legacy_api;