media: dvb uAPI docs: Prefer use "Digital TV instead of "DVB"

tjh.dev / kernel

fork atom

Linux kernel mirror (for testing) git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git

kernel os linux

fork atom

media: dvb uAPI docs: Prefer use "Digital TV instead of "DVB"

The usage of the term "DVB" at the dvb API docs is confusing,
as, right now, it can refer to either the European digital TV
standard or to the subsystem.

So, prefer calling it as "Digital TV" on most places, to avoid
ambiguity.

Signed-off-by: Mauro Carvalho Chehab <mchehab@s-opensource.com>

Mauro Carvalho Chehab 8 years ago 699f19e3 0de6357a

+149 -126

41 changed files

expand all collapse all

Documentation

media

uapi

dvb

audio-channel-select.rst

audio-fclose.rst

audio-fopen.rst

audio-fwrite.rst

audio-set-av-sync.rst

audio-set-bypass-mode.rst

audio-set-mute.rst

audio.rst

ca-fclose.rst

ca-fopen.rst

ca.rst

demux.rst

dmx-fclose.rst

dmx-fopen.rst

dmx-fread.rst

dmx-fwrite.rst

dvbapi.rst

dvbproperty.rst

examples.rst

fe-diseqc-reset-overload.rst

fe-get-info.rst

fe-get-property.rst

fe-read-status.rst

fe_property_parameters.rst

frontend-property-terrestrial-systems.rst

frontend.rst

frontend_f_close.rst

frontend_f_open.rst

frontend_legacy_dvbv3_api.rst

intro.rst

legacy_dvb_apis.rst

net-add-if.rst

net.rst

query-dvb-frontend-info.rst

video-continue.rst

video-freeze.rst

video-get-event.rst

video-play.rst

video-select-source.rst

video-stop.rst

video.rst

+1 -1

Documentation/media/uapi/dvb/audio-channel-select.rst

reviewed

··· 44 44 Description 45 45 ----------- 46 46 47 47 - This ioctl is for DVB devices only. To control a V4L2 decoder use the 47 47 + This ioctl is for Digital TV devices only. To control a V4L2 decoder use the 48 48 V4L2 ``V4L2_CID_MPEG_AUDIO_DEC_PLAYBACK`` control instead. 49 49 50 50 This ioctl call asks the Audio Device to select the requested channel if

+4 -4

Documentation/media/uapi/dvb/audio-fclose.rst

reviewed

··· 2 2 3 3 .. _audio_fclose: 4 4 5 5 - ================= 6 6 - DVB audio close() 7 7 - ================= 5 5 + ======================== 6 6 + Digital TV audio close() 7 7 + ======================== 8 8 9 9 Name 10 10 ---- 11 11 12 12 - DVB audio close() 12 12 + Digital TV audio close() 13 13 14 14 .. attention:: This ioctl is deprecated 15 15

+4 -4

Documentation/media/uapi/dvb/audio-fopen.rst

reviewed

··· 2 2 3 3 .. _audio_fopen: 4 4 5 5 - ================ 6 6 - DVB audio open() 7 7 - ================ 5 5 + ======================= 6 6 + Digital TV audio open() 7 7 + ======================= 8 8 9 9 Name 10 10 ---- 11 11 12 12 - DVB audio open() 12 12 + Digital TV audio open() 13 13 14 14 .. attention:: This ioctl is deprecated 15 15

+4 -4

Documentation/media/uapi/dvb/audio-fwrite.rst

reviewed

··· 2 2 3 3 .. _audio_fwrite: 4 4 5 5 - ================= 6 6 - DVB audio write() 7 7 - ================= 5 5 + ========================= 6 6 + Digital TV audio write() 7 7 + ========================= 8 8 9 9 Name 10 10 ---- 11 11 12 12 - DVB audio write() 12 12 + Digital TV audio write() 13 13 14 14 .. attention:: This ioctl is deprecated 15 15

+1 -1

Documentation/media/uapi/dvb/audio-set-av-sync.rst

reviewed

··· 38 38 39 39 - boolean state 40 40 41 41 - - Tells the DVB subsystem if A/V synchronization shall be ON or OFF. 41 41 + - Tells the Digital TV subsystem if A/V synchronization shall be ON or OFF. 42 42 43 43 TRUE: AV-sync ON 44 44

+3 -3

Documentation/media/uapi/dvb/audio-set-bypass-mode.rst

reviewed

··· 38 38 - boolean mode 39 39 40 40 - Enables or disables the decoding of the current Audio stream in 41 41 - the DVB subsystem. 41 41 + the Digital TV subsystem. 42 42 43 43 TRUE: Bypass is disabled 44 44 ··· 50 50 51 51 This ioctl call asks the Audio Device to bypass the Audio decoder and 52 52 forward the stream without decoding. This mode shall be used if streams 53 53 - that can’t be handled by the DVB system shall be decoded. Dolby 54 54 - DigitalTM streams are automatically forwarded by the DVB subsystem if 53 53 + that can’t be handled by the Digial TV system shall be decoded. Dolby 54 54 + DigitalTM streams are automatically forwarded by the Digital TV subsystem if 55 55 the hardware can handle it. 56 56 57 57

+1 -1

Documentation/media/uapi/dvb/audio-set-mute.rst

reviewed

··· 48 48 Description 49 49 ----------- 50 50 51 51 - This ioctl is for DVB devices only. To control a V4L2 decoder use the 51 51 + This ioctl is for Digital TV devices only. To control a V4L2 decoder use the 52 52 V4L2 :ref:`VIDIOC_DECODER_CMD` with the 53 53 ``V4L2_DEC_CMD_START_MUTE_AUDIO`` flag instead. 54 54

+7 -6

Documentation/media/uapi/dvb/audio.rst

reviewed

··· 2 2 3 3 .. _dvb_audio: 4 4 5 5 - ################ 6 6 - DVB Audio Device 7 7 - ################ 8 8 - The DVB audio device controls the MPEG2 audio decoder of the DVB 9 9 - hardware. It can be accessed through ``/dev/dvb/adapter?/audio?``. Data 5 5 + ####################### 6 6 + Digital TV Audio Device 7 7 + ####################### 8 8 + 9 9 + The Digital TV audio device controls the MPEG2 audio decoder of the Digital 10 10 + TV hardware. It can be accessed through ``/dev/dvb/adapter?/audio?``. Data 10 11 types and and ioctl definitions can be accessed by including 11 12 ``linux/dvb/audio.h`` in your application. 12 13 13 13 - Please note that some DVB cards don’t have their own MPEG decoder, which 14 14 + Please note that some Digital TV cards don’t have their own MPEG decoder, which 14 15 results in the omission of the audio and video device. 15 16 16 17 These ioctls were also used by V4L2 to control MPEG decoders implemented

+4 -4

Documentation/media/uapi/dvb/ca-fclose.rst

reviewed

··· 2 2 3 3 .. _ca_fclose: 4 4 5 5 - ============== 6 6 - DVB CA close() 7 7 - ============== 5 5 + ===================== 6 6 + Digital TV CA close() 7 7 + ===================== 8 8 9 9 Name 10 10 ---- 11 11 12 12 - DVB CA close() 12 12 + Digital TV CA close() 13 13 14 14 15 15 Synopsis

+5 -5

Documentation/media/uapi/dvb/ca-fopen.rst

reviewed

··· 2 2 3 3 .. _ca_fopen: 4 4 5 5 - ============= 6 6 - DVB CA open() 7 7 - ============= 5 5 + ==================== 6 6 + Digital TV CA open() 7 7 + ==================== 8 8 9 9 Name 10 10 ---- 11 11 12 12 - DVB CA open() 12 12 + Digital TV CA open() 13 13 14 14 15 15 Synopsis ··· 23 23 --------- 24 24 25 25 ``name`` 26 26 - Name of specific DVB CA device. 26 26 + Name of specific Digital TV CA device. 27 27 28 28 ``flags`` 29 29 A bit-wise OR of the following flags:

+6 -5

Documentation/media/uapi/dvb/ca.rst

reviewed

··· 2 2 3 3 .. _dvb_ca: 4 4 5 5 - ############# 6 6 - DVB CA Device 7 7 - ############# 8 8 - The DVB CA device controls the conditional access hardware. It can be 9 9 - accessed through ``/dev/dvb/adapter?/ca?``. Data types and and ioctl 5 5 + #################### 6 6 + Digital TV CA Device 7 7 + #################### 8 8 + 9 9 + The Digital TV CA device controls the conditional access hardware. It 10 10 + can be accessed through ``/dev/dvb/adapter?/ca?``. Data types and and ioctl 10 11 definitions can be accessed by including ``linux/dvb/ca.h`` in your 11 12 application. 12 13

+9 -4

Documentation/media/uapi/dvb/demux.rst

reviewed

··· 2 2 3 3 .. _dvb_demux: 4 4 5 5 - ################ 6 6 - DVB Demux Device 7 7 - ################ 8 8 - The DVB demux device controls the filters of the DVB hardware/software. 5 5 + ####################### 6 6 + Digital TV Demux Device 7 7 + ####################### 8 8 + 9 9 + The Digital TV demux device controls the MPEG-TS filters for the 10 10 + digital TV. If the driver and hardware supports, those filters are 11 11 + implemented at the hardware. Otherwise, the Kernel provides a software 12 12 + emulation. 13 13 + 9 14 It can be accessed through ``/dev/adapter?/demux?``. Data types and and 10 15 ioctl definitions can be accessed by including ``linux/dvb/dmx.h`` in 11 16 your application.

+4 -4

Documentation/media/uapi/dvb/dmx-fclose.rst

reviewed

··· 2 2 3 3 .. _dmx_fclose: 4 4 5 5 - ================= 6 6 - DVB demux close() 7 7 - ================= 5 5 + ======================== 6 6 + Digital TV demux close() 7 7 + ======================== 8 8 9 9 Name 10 10 ---- 11 11 12 12 - DVB demux close() 12 12 + Digital TV demux close() 13 13 14 14 15 15 Synopsis

+5 -5

Documentation/media/uapi/dvb/dmx-fopen.rst

reviewed

··· 2 2 3 3 .. _dmx_fopen: 4 4 5 5 - ================ 6 6 - DVB demux open() 7 7 - ================ 5 5 + ======================= 6 6 + Digital TV demux open() 7 7 + ======================= 8 8 9 9 Name 10 10 ---- 11 11 12 12 - DVB demux open() 12 12 + Digital TV demux open() 13 13 14 14 15 15 Synopsis ··· 22 22 --------- 23 23 24 24 ``name`` 25 25 - Name of specific DVB demux device. 25 25 + Name of specific Digital TV demux device. 26 26 27 27 ``flags`` 28 28 A bit-wise OR of the following flags:

+4 -4

Documentation/media/uapi/dvb/dmx-fread.rst

reviewed

··· 2 2 3 3 .. _dmx_fread: 4 4 5 5 - ================ 6 6 - DVB demux read() 7 7 - ================ 5 5 + ======================= 6 6 + Digital TV demux read() 7 7 + ======================= 8 8 9 9 Name 10 10 ---- 11 11 12 12 - DVB demux read() 12 12 + Digital TV demux read() 13 13 14 14 15 15 Synopsis

+4 -4

Documentation/media/uapi/dvb/dmx-fwrite.rst

reviewed

··· 2 2 3 3 .. _dmx_fwrite: 4 4 5 5 - ================= 6 6 - DVB demux write() 7 7 - ================= 5 5 + ======================== 6 6 + Digital TV demux write() 7 7 + ======================== 8 8 9 9 Name 10 10 ---- 11 11 12 12 - DVB demux write() 12 12 + Digital TV demux write() 13 13 14 14 15 15 Synopsis

+19 -6

Documentation/media/uapi/dvb/dvbapi.rst

reviewed

··· 10 10 11 11 .. note:: 12 12 13 13 - This API is also known as **DVB API**, although it is generic 14 14 - enough to support all digital TV standards. 13 13 + This API is also known as Linux **DVB API**. 14 14 + 15 15 + It it was originally written to support the European digital TV 16 16 + standard (DVB), and later extended to support all digital TV standards. 17 17 + 18 18 + In order to avoid confusion, within this document, it was opted to refer to 19 19 + it, and to associated hardware as **Digital TV**. 20 20 + 21 21 + The word **DVB** is reserved to be used for: 22 22 + 23 23 + - the Digital TV API version 24 24 + (e. g. DVB API version 3 or DVB API version 5); 25 25 + - digital TV data types (enums, structs, defines, etc); 26 26 + - digital TV device nodes (``/dev/dvb/...``); 27 27 + - the European DVB standard. 15 28 16 29 **Version 5.10** 17 30 ··· 54 41 55 42 - J. K. Metzler, Ralph <rjkm@metzlerbros.de> 56 43 57 57 - - Original author of the DVB API documentation. 44 44 + - Original author of the Digital TV API documentation. 58 45 59 46 - O. C. Metzler, Marcus <rjkm@metzlerbros.de> 60 47 61 61 - - Original author of the DVB API documentation. 48 48 + - Original author of the Digital TV API documentation. 62 49 63 50 - Carvalho Chehab, Mauro <m.chehab@kernel.org> 64 51 ··· 76 63 77 64 DocBook improvements and cleanups, in order to document the system calls 78 65 on a more standard way and provide more description about the current 79 79 - DVB API. 66 66 + Digital TV API. 80 67 81 68 :revision: 2.0.4 / 2011-05-06 (*mcc*) 82 69 83 83 - Add more information about DVB APIv5, better describing the frontend 70 70 + Add more information about DVBv5 API, better describing the frontend 84 71 GET/SET props ioctl's. 85 72 86 73

+2 -2

Documentation/media/uapi/dvb/dvbproperty.rst

reviewed

··· 13 13 systems). The actual parameters are specific to each particular digital 14 14 TV standards, and may change as the digital TV specs evolves. 15 15 16 16 - In the past (up to DVB API version 3), the strategy used was to have a 16 16 + In the past (up to DVB API version 3 - DVBv3), the strategy used was to have a 17 17 union with the parameters needed to tune for DVB-S, DVB-C, DVB-T and 18 18 ATSC delivery systems grouped there. The problem is that, as the second 19 19 generation standards appeared, the size of such union was not big ··· 41 41 support to new standards and/or new hardware. 42 42 43 43 3. Nowadays, most frontends support multiple delivery systems. 44 44 - Only with DVB v5 calls it is possible to switch between 44 44 + Only with DVB API version 5 calls it is possible to switch between 45 45 the multiple delivery systems supported by a frontend. 46 46 47 47 4. DVB API version 5 is also called *S2API*, as the first

+2 -2

Documentation/media/uapi/dvb/examples.rst

reviewed

··· 6 6 Examples 7 7 ******** 8 8 9 9 - In this section we would like to present some examples for using the DVB 10 10 - API. 9 9 + In this section we would like to present some examples for using the Digital 10 10 + TV API. 11 11 12 12 .. note:: 13 13

+1 -1

Documentation/media/uapi/dvb/fe-diseqc-reset-overload.rst

reviewed

··· 31 31 If the bus has been automatically powered off due to power overload, 32 32 this ioctl call restores the power to the bus. The call requires 33 33 read/write access to the device. This call has no effect if the device 34 34 - is manually powered off. Not all DVB adapters support this ioctl. 34 34 + is manually powered off. Not all Digital TV adapters support this ioctl. 35 35 36 36 37 37 Return Value

+3 -2

Documentation/media/uapi/dvb/fe-get-info.rst

reviewed

··· 9 9 Name 10 10 ==== 11 11 12 12 - FE_GET_INFO - Query DVB frontend capabilities and returns information about the - front-end. This call only requires read-only access to the device 12 12 + FE_GET_INFO - Query Digital TV frontend capabilities and returns information 13 13 + about the - front-end. This call only requires read-only access to the device. 13 14 14 15 15 16 Synopsis ··· 34 33 Description 35 34 =========== 36 35 37 37 - All DVB frontend devices support the ``FE_GET_INFO`` ioctl. It is used 36 36 + All Digital TV frontend devices support the ``FE_GET_INFO`` ioctl. It is used 38 37 to identify kernel devices compatible with this specification and to 39 38 obtain information about driver and hardware capabilities. The ioctl 40 39 takes a pointer to dvb_frontend_info which is filled by the driver.

+1 -1

Documentation/media/uapi/dvb/fe-get-property.rst

reviewed

··· 35 35 Description 36 36 =========== 37 37 38 38 - All DVB frontend devices support the ``FE_SET_PROPERTY`` and 38 38 + All Digital TV frontend devices support the ``FE_SET_PROPERTY`` and 39 39 ``FE_GET_PROPERTY`` ioctls. The supported properties and statistics 40 40 depends on the delivery system and on the device: 41 41

+1 -1

Documentation/media/uapi/dvb/fe-read-status.rst

reviewed

··· 33 33 Description 34 34 =========== 35 35 36 36 - All DVB frontend devices support the ``FE_READ_STATUS`` ioctl. It is 36 36 + All Digital TV frontend devices support the ``FE_READ_STATUS`` ioctl. It is 37 37 used to check about the locking status of the frontend after being 38 38 tuned. The ioctl takes a pointer to an integer where the status will be 39 39 written.

+2 -2

Documentation/media/uapi/dvb/fe_property_parameters.rst

reviewed

··· 819 819 DTV_API_VERSION 820 820 =============== 821 821 822 822 - Returns the major/minor version of the DVB API 822 822 + Returns the major/minor version of the Digital TV API 823 823 824 824 825 825 .. _DTV-CODE-RATE-HP: ··· 919 919 Used on DVB-S2, DVB-T2 and ISDB-S. 920 920 921 921 DVB-S2, DVB-T2 and ISDB-S support the transmission of several streams on 922 922 - a single transport stream. This property enables the DVB driver to 922 922 + a single transport stream. This property enables the digital TV driver to 923 923 handle substream filtering, when supported by the hardware. By default, 924 924 substream filtering is disabled. 925 925

+1 -1

Documentation/media/uapi/dvb/frontend-property-terrestrial-systems.rst

reviewed

··· 100 100 very sophisticated devices won't need certain parameters to tune. 101 101 102 102 The information given here should help application writers to know how 103 103 - to handle ISDB-T and ISDB-Tsb hardware using the Linux DVB-API. 103 103 + to handle ISDB-T and ISDB-Tsb hardware using the Linux Digital TV API. 104 104 105 105 The details given here about ISDB-T and ISDB-Tsb are just enough to 106 106 basically show the dependencies between the needed parameter values, but

+5 -5

Documentation/media/uapi/dvb/frontend.rst

reviewed

··· 2 2 3 3 .. _dvb_frontend: 4 4 5 5 - ################ 6 6 - DVB Frontend API 7 7 - ################ 5 5 + ####################### 6 6 + Digital TV Frontend API 7 7 + ####################### 8 8 9 9 - The DVB frontend API was designed to support three groups of delivery 9 9 + The Digital TV frontend API was designed to support three groups of delivery 10 10 systems: Terrestrial, cable and Satellite. Currently, the following 11 11 delivery systems are supported: 12 12 ··· 17 17 18 18 - Satellite systems: DVB-S, DVB-S2, DVB Turbo, ISDB-S, DSS 19 19 20 20 - The DVB frontend controls several sub-devices including: 20 20 + The Digital TV frontend controls several sub-devices including: 21 21 22 22 - Tuner 23 23

+3 -3

Documentation/media/uapi/dvb/frontend_f_close.rst

reviewed

··· 2 2 3 3 .. _frontend_f_close: 4 4 5 5 - ******************** 6 6 - DVB frontend close() 7 7 - ******************** 5 5 + *************************** 6 6 + Digital TV frontend close() 7 7 + *************************** 8 8 9 9 Name 10 10 ====

+3 -3

Documentation/media/uapi/dvb/frontend_f_open.rst

reviewed

··· 2 2 3 3 .. _frontend_f_open: 4 4 5 5 - ******************* 6 6 - DVB frontend open() 7 7 - ******************* 5 5 + *************************** 6 6 + Digital TV frontend open() 7 7 + *************************** 8 8 9 9 Name 10 10 ====

+3 -3

Documentation/media/uapi/dvb/frontend_legacy_dvbv3_api.rst

reviewed

··· 2 2 3 3 .. _frontend_legacy_dvbv3_api: 4 4 5 5 - **************************************** 6 6 - DVB Frontend legacy API (a. k. a. DVBv3) 7 7 - **************************************** 5 5 + *********************************************** 6 6 + Digital TV Frontend legacy API (a. k. a. DVBv3) 7 7 + *********************************************** 8 8 9 9 The usage of this API is deprecated, as it doesn't support all digital 10 10 TV standards, doesn't provide good statistics measurements and provides

+9 -9

Documentation/media/uapi/dvb/intro.rst

reviewed

··· 33 33 History 34 34 ======= 35 35 36 36 - The first API for DVB cards we used at Convergence in late 1999 was an 36 36 + The first API for Digital TV cards we used at Convergence in late 1999 was an 37 37 extension of the Video4Linux API which was primarily developed for frame 38 38 - grabber cards. As such it was not really well suited to be used for DVB 39 39 - cards and their new features like recording MPEG streams and filtering 38 38 + grabber cards. As such it was not really well suited to be used for Digital 39 39 + TV cards and their new features like recording MPEG streams and filtering 40 40 several section and PES data streams at the same time. 41 41 42 42 In early 2000, Convergence was approached by Nokia with a proposal for a new 43 43 - standard Linux DVB API. As a commitment to the development of terminals 43 43 + standard Linux Digital TV API. As a commitment to the development of terminals 44 44 based on open standards, Nokia and Convergence made it available to all 45 45 Linux developers and published it on https://linuxtv.org in September 46 46 2000. With the Linux driver for the Siemens/Hauppauge DVB PCI card, 47 47 - Convergence provided a first implementation of the Linux DVB API. 48 48 - Convergence was the maintainer of the Linux DVB API in the early 47 47 + Convergence provided a first implementation of the Linux Digital TV API. 48 48 + Convergence was the maintainer of the Linux Digital TV API in the early 49 49 days. 50 50 51 51 Now, the API is maintained by the LinuxTV community (i.e. you, the reader ··· 88 88 89 89 Not every digital TV hardware provides conditional access hardware. 90 90 91 91 - Demultiplexer which filters the incoming DVB stream 91 91 + Demultiplexer which filters the incoming Digital TV MPEG-TS stream 92 92 The demultiplexer splits the TS into its components like audio and 93 93 video streams. Besides usually several of such audio and video 94 94 streams it also contains data streams with information about the ··· 124 124 currently six Unix-style character devices for video, audio, frontend, 125 125 demux, CA and IP-over-DVB networking. The video and audio devices 126 126 control the MPEG2 decoder hardware, the frontend device the tuner and 127 127 - the DVB demodulator. The demux device gives you control over the PES and 128 128 - section filters of the hardware. If the hardware does not support 127 127 + the Digital TV demodulator. The demux device gives you control over the PES 128 128 + and section filters of the hardware. If the hardware does not support 129 129 filtering these filters can be implemented in software. Finally, the CA 130 130 device controls all the conditional access capabilities of the hardware. 131 131 It can depend on the individual security requirements of the platform,

+3 -3

Documentation/media/uapi/dvb/legacy_dvb_apis.rst

reviewed

··· 2 2 3 3 .. _legacy_dvb_apis: 4 4 5 5 - ******************* 6 6 - DVB Deprecated APIs 7 7 - ******************* 5 5 + *************************** 6 6 + Digital TV Deprecated APIs 7 7 + *************************** 8 8 9 9 The APIs described here are kept only for historical reasons. There's 10 10 just one driver for a very legacy hardware that uses this API. No modern

+1 -1

Documentation/media/uapi/dvb/net-add-if.rst

reviewed

··· 64 64 65 65 - ifnum 66 66 67 67 - - number of the DVB interface. 67 67 + - number of the Digital TV interface. 68 68 69 69 - .. row 4 70 70

+7 -6

Documentation/media/uapi/dvb/net.rst

reviewed

··· 2 2 3 3 .. _net: 4 4 5 5 - ############### 6 6 - DVB Network API 7 7 - ############### 8 8 - The DVB net device controls the mapping of data packages that are part 5 5 + ###################### 6 6 + Digital TV Network API 7 7 + ###################### 8 8 + 9 9 + The Digital TV net device controls the mapping of data packages that are part 9 10 of a transport stream to be mapped into a virtual network interface, 10 11 visible through the standard Linux network protocol stack. 11 12 ··· 29 28 30 29 .. _net_fcalls: 31 30 32 32 - DVB net Function Calls 33 33 - ###################### 31 31 + Digital TV net Function Calls 32 32 + ############################# 34 33 35 34 .. toctree:: 36 35 :maxdepth: 1

+2 -2

Documentation/media/uapi/dvb/query-dvb-frontend-info.rst

reviewed

··· 9 9 Usually, the first thing to do when the frontend is opened is to check 10 10 the frontend capabilities. This is done using 11 11 :ref:`FE_GET_INFO`. This ioctl will enumerate the 12 12 - DVB API version and other characteristics about the frontend, and can be 13 13 - opened either in read only or read/write mode. 12 12 + Digital TV API version and other characteristics about the frontend, and can 13 13 + be opened either in read only or read/write mode.

+1 -1

Documentation/media/uapi/dvb/video-continue.rst

reviewed

+2 -2

Documentation/media/uapi/dvb/video-freeze.rst

reviewed

··· 44 44 Description 45 45 ----------- 46 46 47 47 - This ioctl is for DVB devices only. To control a V4L2 decoder use the 47 47 + This ioctl is for Digital TV devices only. To control a V4L2 decoder use the 48 48 V4L2 :ref:`VIDIOC_DECODER_CMD` instead. 49 49 50 50 This ioctl call suspends the live video stream being played. Decoding 51 51 and playing are frozen. It is then possible to restart the decoding and 52 52 playing process of the video stream using the VIDEO_CONTINUE command. 53 53 If VIDEO_SOURCE_MEMORY is selected in the ioctl call 54 54 - VIDEO_SELECT_SOURCE, the DVB subsystem will not decode any more data 54 54 + VIDEO_SELECT_SOURCE, the Digital TV subsystem will not decode any more data 55 55 until the ioctl call VIDEO_CONTINUE or VIDEO_PLAY is performed. 56 56 57 57

+1 -1

Documentation/media/uapi/dvb/video-get-event.rst

reviewed

··· 50 50 Description 51 51 ----------- 52 52 53 53 - This ioctl is for DVB devices only. To get events from a V4L2 decoder 53 53 + This ioctl is for Digital TV devices only. To get events from a V4L2 decoder 54 54 use the V4L2 :ref:`VIDIOC_DQEVENT` ioctl instead. 55 55 56 56 This ioctl call returns an event of type video_event if available. If

+1 -1

Documentation/media/uapi/dvb/video-play.rst

reviewed

+1 -1

Documentation/media/uapi/dvb/video-select-source.rst

reviewed

··· 50 50 Description 51 51 ----------- 52 52 53 53 - This ioctl is for DVB devices only. This ioctl was also supported by the 53 53 + This ioctl is for Digital TV devices only. This ioctl was also supported by the 54 54 V4L2 ivtv driver, but that has been replaced by the ivtv-specific 55 55 ``IVTV_IOC_PASSTHROUGH_MODE`` ioctl. 56 56

+1 -1

Documentation/media/uapi/dvb/video-stop.rst

reviewed

··· 60 60 Description 61 61 ----------- 62 62 63 63 - This ioctl is for DVB devices only. To control a V4L2 decoder use the 63 63 + This ioctl is for Digital TV devices only. To control a V4L2 decoder use the 64 64 V4L2 :ref:`VIDIOC_DECODER_CMD` instead. 65 65 66 66 This ioctl call asks the Video Device to stop playing the current

+8 -7

Documentation/media/uapi/dvb/video.rst

reviewed

··· 2 2 3 3 .. _dvb_video: 4 4 5 5 - ################ 6 6 - DVB Video Device 7 7 - ################ 8 8 - The DVB video device controls the MPEG2 video decoder of the DVB 9 9 - hardware. It can be accessed through **/dev/dvb/adapter0/video0**. Data 5 5 + ####################### 6 6 + Digital TV Video Device 7 7 + ####################### 8 8 + 9 9 + The Digital TV video device controls the MPEG2 video decoder of the Digital 10 10 + TV hardware. It can be accessed through **/dev/dvb/adapter0/video0**. Data 10 11 types and and ioctl definitions can be accessed by including 11 12 **linux/dvb/video.h** in your application. 12 13 13 13 - Note that the DVB video device only controls decoding of the MPEG video 14 14 + Note that the Digital TV video device only controls decoding of the MPEG video 14 15 stream, not its presentation on the TV or computer screen. On PCs this 15 16 is typically handled by an associated video4linux device, e.g. 16 17 **/dev/video**, which allows scaling and defining output windows. 17 18 18 18 - Some DVB cards don’t have their own MPEG decoder, which results in the 19 19 + Some Digital TV cards don’t have their own MPEG decoder, which results in the 19 20 omission of the audio and video device as well as the video4linux 20 21 device. 21 22