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

[media] DocBook: Use constant tag for monospaced fonts

As reminded by Jonathan, several places where emphasys
role="tt" were used are actually trying to change the font to
monospaced.

We do that, on other places, by using the constant tag.

So, use it here too.

Reported-by: Jonathan Corbet <corbet@lwn.net>
Signed-off-by: Mauro Carvalho Chehab <mchehab@osg.samsung.com>

+32 -32
+3 -3
Documentation/DocBook/media/dvb/audio.xml
··· 1 1 <title>DVB Audio Device</title> 2 2 <para>The DVB audio device controls the MPEG2 audio decoder of the DVB hardware. It 3 - can be accessed through <emphasis role="bold">/dev/dvb/adapter0/audio0</emphasis>. Data types and and 4 - ioctl definitions can be accessed by including <emphasis role="bold">linux/dvb/audio.h</emphasis> in your 3 + can be accessed through <constant>/dev/dvb/adapter?/audio?</constant>. Data types and and 4 + ioctl definitions can be accessed by including <constant>linux/dvb/audio.h</constant> in your 5 5 application. 6 6 </para> 7 7 <para>Please note that some DVB cards don&#8217;t have their own MPEG decoder, which results in ··· 32 32 </programlisting> 33 33 <para>AUDIO_SOURCE_DEMUX selects the demultiplexer (fed either by the frontend or the 34 34 DVR device) as the source of the video stream. If AUDIO_SOURCE_MEMORY 35 - is selected the stream comes from the application through the <emphasis role="bold">write()</emphasis> system 35 + is selected the stream comes from the application through the <constant>write()</constant> system 36 36 call. 37 37 </para> 38 38
+2 -2
Documentation/DocBook/media/dvb/ca.xml
··· 1 1 <title>DVB CA Device</title> 2 2 <para>The DVB CA device controls the conditional access hardware. It can be accessed through 3 - <emphasis role="bold">/dev/dvb/adapter0/ca0</emphasis>. Data types and and ioctl definitions can be accessed by 4 - including <emphasis role="bold">linux/dvb/ca.h</emphasis> in your application. 3 + <constant>/dev/dvb/adapter?/ca?</constant>. Data types and and ioctl definitions can be accessed by 4 + including <constant>linux/dvb/ca.h</constant> in your application. 5 5 </para> 6 6 7 7 <section id="ca_data_types">
+5 -5
Documentation/DocBook/media/dvb/demux.xml
··· 1 1 <title>DVB Demux Device</title> 2 2 3 3 <para>The DVB demux device controls the filters of the DVB hardware/software. It can be 4 - accessed through <emphasis role="bold">/dev/adapter0/demux0</emphasis>. Data types and and ioctl definitions can be 5 - accessed by including <emphasis role="bold">linux/dvb/dmx.h</emphasis> in your application. 4 + accessed through <constant>/dev/adapter?/demux?</constant>. Data types and and ioctl definitions can be 5 + accessed by including <constant>linux/dvb/dmx.h</constant> in your application. 6 6 </para> 7 7 <section id="dmx_types"> 8 8 <title>Demux Data Types</title> ··· 21 21 DMX_OUT_TSDEMUX_TAP /&#x22C6; Like TS_TAP but retrieved from the DMX device &#x22C6;/ 22 22 } dmx_output_t; 23 23 </programlisting> 24 - <para><emphasis role="bold">DMX_OUT_TAP</emphasis> delivers the stream output to the demux device on which the ioctl is 24 + <para><constant>DMX_OUT_TAP</constant> delivers the stream output to the demux device on which the ioctl is 25 25 called. 26 26 </para> 27 - <para><emphasis role="bold">DMX_OUT_TS_TAP</emphasis> routes output to the logical DVR device <emphasis role="bold">/dev/dvb/adapter0/dvr0</emphasis>, 28 - which delivers a TS multiplexed from all filters for which <emphasis role="bold">DMX_OUT_TS_TAP</emphasis> was 27 + <para><constant>DMX_OUT_TS_TAP</constant> routes output to the logical DVR device <constant>/dev/dvb/adapter?/dvr?</constant>, 28 + which delivers a TS multiplexed from all filters for which <constant>DMX_OUT_TS_TAP</constant> was 29 29 specified. 30 30 </para> 31 31 </section>
+2 -2
Documentation/DocBook/media/dvb/frontend.xml
··· 14 14 <listitem><para>Satellite Equipment Control (SEC) hardware (only for Satellite).</para></listitem> 15 15 </itemizedlist> 16 16 <para>The frontend can be accessed through 17 - <emphasis role="bold">/dev/dvb/adapter?/frontend?</emphasis>. Data types and 17 + <constant>/dev/dvb/adapter?/frontend?</constant>. Data types and 18 18 ioctl definitions can be accessed by including 19 - <emphasis role="bold">linux/dvb/frontend.h</emphasis> in your application. 19 + <constant>linux/dvb/frontend.h</constant> in your application. 20 20 </para> 21 21 22 22 <para>NOTE: Transmission via the internet (DVB-IP)
+15 -15
Documentation/DocBook/media/dvb/intro.xml
··· 129 129 platform, if and how many of the CA functions are made available to the 130 130 application through this device.</para> 131 131 132 - <para>All devices can be found in the <emphasis role="bold">/dev</emphasis> 133 - tree under <emphasis role="bold">/dev/dvb</emphasis>. The individual devices 132 + <para>All devices can be found in the <constant>/dev</constant> 133 + tree under <constant>/dev/dvb</constant>. The individual devices 134 134 are called:</para> 135 135 136 136 <itemizedlist> 137 137 <listitem> 138 138 139 - <para><emphasis role="bold">/dev/dvb/adapterN/audioM</emphasis>,</para> 139 + <para><constant>/dev/dvb/adapterN/audioM</constant>,</para> 140 140 </listitem> 141 141 <listitem> 142 - <para><emphasis role="bold">/dev/dvb/adapterN/videoM</emphasis>,</para> 142 + <para><constant>/dev/dvb/adapterN/videoM</constant>,</para> 143 143 </listitem> 144 144 <listitem> 145 - <para><emphasis role="bold">/dev/dvb/adapterN/frontendM</emphasis>,</para> 145 + <para><constant>/dev/dvb/adapterN/frontendM</constant>,</para> 146 146 </listitem> 147 147 <listitem> 148 148 149 - <para><emphasis role="bold">/dev/dvb/adapterN/netM</emphasis>,</para> 149 + <para><constant>/dev/dvb/adapterN/netM</constant>,</para> 150 150 </listitem> 151 151 <listitem> 152 152 153 - <para><emphasis role="bold">/dev/dvb/adapterN/demuxM</emphasis>,</para> 153 + <para><constant>/dev/dvb/adapterN/demuxM</constant>,</para> 154 154 </listitem> 155 155 <listitem> 156 156 157 - <para><emphasis role="bold">/dev/dvb/adapterN/dvrM</emphasis>,</para> 157 + <para><constant>/dev/dvb/adapterN/dvrM</constant>,</para> 158 158 </listitem> 159 159 <listitem> 160 160 161 - <para><emphasis role="bold">/dev/dvb/adapterN/caM</emphasis>,</para></listitem></itemizedlist> 161 + <para><constant>/dev/dvb/adapterN/caM</constant>,</para></listitem></itemizedlist> 162 162 163 163 <para>where N enumerates the DVB PCI cards in a system starting 164 164 from&#x00A0;0, and M enumerates the devices of each type within each 165 - adapter, starting from&#x00A0;0, too. We will omit the &#8220;<emphasis 166 - role="bold">/dev/dvb/adapterN/</emphasis>&#8221; in the further dicussion 165 + adapter, starting from&#x00A0;0, too. We will omit the &#8220; 166 + <constant>/dev/dvb/adapterN/</constant>&#8221; in the further dicussion 167 167 of these devices. The naming scheme for the devices is the same wheter 168 168 devfs is used or not.</para> 169 169 ··· 202 202 </programlisting> 203 203 204 204 <para>To enable applications to support different API version, an 205 - additional include file <emphasis 206 - role="bold">linux/dvb/version.h</emphasis> exists, which defines the 207 - constant <emphasis role="bold">DVB_API_VERSION</emphasis>. This document 208 - describes <emphasis role="bold">DVB_API_VERSION 5.10</emphasis>. 205 + additional include file 206 + <constant>linux/dvb/version.h</constant> exists, which defines the 207 + constant <constant>DVB_API_VERSION</constant>. This document 208 + describes <constant>DVB_API_VERSION 5.10</constant>. 209 209 </para> 210 210 211 211 </section>
+2 -2
Documentation/DocBook/media/dvb/kdapi.xml
··· 1 1 <title>Kernel Demux API</title> 2 2 <para>The kernel demux API defines a driver-internal interface for registering low-level, 3 3 hardware specific driver to a hardware independent demux layer. It is only of interest for 4 - DVB device driver writers. The header file for this API is named <emphasis role="bold">demux.h</emphasis> and located in 5 - <emphasis role="bold">drivers/media/dvb-core</emphasis>. 4 + DVB device driver writers. The header file for this API is named <constant>demux.h</constant> and located in 5 + <constant>">drivers/media/dvb-core</constant>. 6 6 </para> 7 7 <para>Maintainer note: This section must be reviewed. It is probably out of date. 8 8 </para>
+2 -2
Documentation/DocBook/media/dvb/net.xml
··· 13 13 <para>In order to create the Linux virtual network interfaces, an application 14 14 needs to tell to the Kernel what are the PIDs and the encapsulation types 15 15 that are present on the transport stream. This is done through 16 - <emphasis role="bold">/dev/dvb/adapter?/net?</emphasis> device node. 16 + <constant>/dev/dvb/adapter?/net?</constant> device node. 17 17 The data will be available via virtual <constant>dvb?_?</constant> 18 18 network interfaces, and will be controled/routed via the standard 19 19 ip tools (like ip, route, netstat, ifconfig, etc).</para> 20 20 <para> Data types and and ioctl definitions are defined via 21 - <emphasis role="bold">linux/dvb/net.h</emphasis> header.</para> 21 + <constant>linux/dvb/net.h</constant> header.</para> 22 22 23 23 <section id="net_fcalls"> 24 24 <title>DVB net Function Calls</title>
+1 -1
Documentation/DocBook/media/dvb/video.xml
··· 24 24 25 25 <section id="video-format-t"> 26 26 <title>video_format_t</title> 27 - <para>The <emphasis role="bold">video_format_t</emphasis> data type defined by 27 + <para>The <constant>video_format_t</constant> data type defined by 28 28 </para> 29 29 <programlisting> 30 30 typedef enum {