Fix a couple of misuses of <acronym> to wrap COM[0-9] device names and

add <devicename> tags around the remaining untagged instances of the same.

PR:		docs/69221
Submitted by:	Warren Block <wblock@wonkity.com>
This commit is contained in:
Giorgos Keramidas 2004-07-18 12:54:14 +00:00
parent 4b8dbcb2ee
commit 46f0515db1
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=21561
6 changed files with 18 additions and 18 deletions

View file

@ -1124,7 +1124,7 @@ exit 0</programlisting>
<para>We run &os; 4 on a couple of &i386; PCs for various peripheral
uses. &os; usually uses a screen and keyboard for the
console, but can be configured to use a serial port (usually the
first serial port known as COM1 in DOS/&windows; or
first serial port known as <devicename>COM1</devicename> in DOS/&windows; or
<devicename>ttyd0</devicename> in &unix;).</para>
<para>The cabling for these servers depends on the PC harware. If
@ -1296,7 +1296,7 @@ exit 0</programlisting>
<para>Check that the kernel configuration file has
<literal>flags 0x10</literal> in the config line for the
<devicename>sio0</devicename> device. This signals this device (known
as <literal>COM1</literal> in DOS/&windows; or
as <devicename>COM1</devicename> in DOS/&windows; or
<devicename>/dev/ttyd0</devicename> in &os;) can be used as a
console. This flag is set on the <filename>GENERIC</filename> and
<filename>LINT</filename> sample configs, so is likely to be set in

View file

@ -1154,16 +1154,16 @@
<para>The 8250/16450/16550 UART occupies eight contiguous I/O
port addresses. In the IBM PC, there are two defined
locations for these eight ports and they are known
collectively as COM1 and COM2. The makers of PC-clones and
add-on cards have created two additional areas known as COM3
and COM4, but these extra COM ports conflict with other
collectively as <devicename>COM1</devicename> and <devicename>COM2</devicename>. The makers of PC-clones and
add-on cards have created two additional areas known as <devicename>COM3</devicename>
and <devicename>COM4</devicename>, but these extra COM ports conflict with other
hardware on some systems. The most common conflict is with
video adapters that provide IBM 8514 emulation.</para>
<para>COM1 is located from 0x3f8 to 0x3ff and normally uses
IRQ 4 COM2 is located from 0x2f8 to 0x2ff and normally uses
IRQ 3 COM3 is located from 0x3e8 to 0x3ef and has no
standardized IRQ COM4 is located from 0x2e8 to 0x2ef and has
<para><devicename>COM1</devicename> is located from 0x3f8 to 0x3ff and normally uses
IRQ 4. <devicename>COM2</devicename> is located from 0x2f8 to 0x2ff and normally uses
IRQ 3. <devicename>COM3</devicename> is located from 0x3e8 to 0x3ef and has no
standardized IRQ. <devicename>COM4</devicename> is located from 0x2e8 to 0x2ef and has
no standardized IRQ.</para>
<para>A description of the I/O ports of the 8250/16450/16550

View file

@ -10391,7 +10391,7 @@ sio1: type 16550A</programlisting>
<answer>
<para>The third serial port, <devicename>sio2</devicename>
(see &man.sio.4;, known as COM3 in DOS), is on
(see &man.sio.4;, known as <devicename>COM3</devicename> in DOS), is on
<devicename>/dev/cuaa2</devicename> for dial-out devices,
and on <devicename>/dev/ttyd2</devicename> for dial-in
devices. What is the difference between these two classes

View file

@ -1124,12 +1124,12 @@ device sio1 at isa? port IO_COM2 irq 3
device sio2 at isa? disable port IO_COM3 irq 5
device sio3 at isa? disable port IO_COM4 irq 9</programlisting>
<para>These are the four serial ports referred to as COM1 through COM4
<para>These are the four serial ports referred to as <devicename>COM1</devicename> through <devicename>COM4</devicename>
in the &ms-dos/&windows; world.</para>
<note>
<para>If you have an internal modem on COM4 and a serial port at
COM2, you will have to change the IRQ of the modem to 2 (for
<para>If you have an internal modem on <devicename>COM4</devicename> and a serial port at
<devicename>COM2</devicename>, you will have to change the IRQ of the modem to 2 (for
obscure technical reasons, IRQ2 = IRQ 9) in order to access it
from &os;. If you have a multiport serial card, check the
manual page for &man.sio.4; for more information on the proper
@ -1137,11 +1137,11 @@ device sio3 at isa? disable port IO_COM4 irq 9</programlisting>
S3 chips) use IO addresses in the form of
<literal>0x*2e8</literal>, and since many cheap serial cards do
not fully decode the 16-bit IO address space, they clash with
these cards making the COM4 port practically unavailable.</para>
these cards making the <devicename>COM4</devicename> port practically unavailable.</para>
<para>Each serial port is required to have a unique IRQ (unless you
are using one of the multiport cards where shared interrupts are
supported), so the default IRQs for COM3 and COM4 cannot be
supported), so the default IRQs for <devicename>COM3</devicename> and <devicename>COM4</devicename> cannot be
used.</para>
</note>

View file

@ -1788,7 +1788,7 @@ exit 1
<devicename>sio</devicename> devices. These are the COM
ports we need. If your modem acts like a standard serial
port then you should see it listed on
<devicename>sio1</devicename>, or COM2. If so, you are not
<devicename>sio1</devicename>, or <devicename>COM2</devicename>. If so, you are not
required to rebuild the kernel, you just need to make the
serial device. You can do this by changing your directory
to <filename>/dev</filename> and running the
@ -1799,7 +1799,7 @@ exit 1
<para>which will create the serial devices for your system.
When matching up sio modem is on <devicename>sio1</devicename> or
<acronym>COM2</acronym> if you are in DOS, then your
<devicename>COM2</devicename> if you are in DOS, then your
modem device would be <devicename>/dev/cuaa1</devicename>.</para>
</sect2>

View file

@ -1945,7 +1945,7 @@ raisechar=^^</programlisting>
<step>
<para>Connect the serial port. The serial console will be
on COM1.</para>
on <devicename>COM1</devicename>.</para>
</step>
<step>