Remove 'tty' and 'vector' from sio(4) device lines in kernel
configuration examples. These flags are depricated and will actually cause config(8) to fail with a 'syntax error.' Reviewed by: -doc (one approval, no dissent)
This commit is contained in:
parent
b438cb9104
commit
cdae0fc73e
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=12197
1 changed files with 20 additions and 22 deletions
|
@ -1985,14 +1985,14 @@
|
||||||
add <literal>options COM_MULTIPORT</literal> or it will not
|
add <literal>options COM_MULTIPORT</literal> or it will not
|
||||||
work very well!</para>
|
work very well!</para>
|
||||||
|
|
||||||
<programlisting>device sio4 at isa? port 0x100 tty flags 0xb05
|
<programlisting>device sio4 at isa? port 0x100 flags 0xb05
|
||||||
device sio5 at isa? port 0x108 tty flags 0xb05
|
device sio5 at isa? port 0x108 flags 0xb05
|
||||||
device sio6 at isa? port 0x110 tty flags 0xb05
|
device sio6 at isa? port 0x110 flags 0xb05
|
||||||
device sio7 at isa? port 0x118 tty flags 0xb05
|
device sio7 at isa? port 0x118 flags 0xb05
|
||||||
device sio8 at isa? port 0x120 tty flags 0xb05
|
device sio8 at isa? port 0x120 flags 0xb05
|
||||||
device sio9 at isa? port 0x128 tty flags 0xb05
|
device sio9 at isa? port 0x128 flags 0xb05
|
||||||
device sio10 at isa? port 0x130 tty flags 0xb05
|
device sio10 at isa? port 0x130 flags 0xb05
|
||||||
device sio11 at isa? port 0x138 tty flags 0xb05 irq 9 vector siointr</programlisting>
|
device sio11 at isa? port 0x138 flags 0xb05 irq 9</programlisting>
|
||||||
|
|
||||||
<para>The trick in setting this up is that the MSB of the
|
<para>The trick in setting this up is that the MSB of the
|
||||||
flags represent the last SIO port, in this case 11 so flags
|
flags represent the last SIO port, in this case 11 so flags
|
||||||
|
@ -2053,21 +2053,19 @@ device sio11 at isa? port 0x138 tty flags 0xb05 irq 9 vector siointr<
|
||||||
<step>
|
<step>
|
||||||
<para>Where the current <literal>device
|
<para>Where the current <literal>device
|
||||||
sio<replaceable>n</replaceable></literal> lines are, you
|
sio<replaceable>n</replaceable></literal> lines are, you
|
||||||
will need to add 16 more devices. Only the last device
|
will need to add 16 more devices. The
|
||||||
includes the interrupt vector for the board. (See the
|
|
||||||
&man.sio.4; manual page for detail as to why.) The
|
|
||||||
following example is for a Boca Board with an interrupt
|
following example is for a Boca Board with an interrupt
|
||||||
of 3, and a base IO address 100h. The IO address for
|
of 3, and a base IO address 100h. The IO address for
|
||||||
Each port is +8 hexadecimal from the previous port, thus
|
Each port is +8 hexadecimal from the previous port, thus
|
||||||
the 100h, 108h, 110h... addresses.</para>
|
the 100h, 108h, 110h... addresses.</para>
|
||||||
|
|
||||||
<programlisting>device sio1 at isa? port 0x100 tty flags 0x1005
|
<programlisting>device sio1 at isa? port 0x100 flags 0x1005
|
||||||
device sio2 at isa? port 0x108 tty flags 0x1005
|
device sio2 at isa? port 0x108 flags 0x1005
|
||||||
device sio3 at isa? port 0x110 tty flags 0x1005
|
device sio3 at isa? port 0x110 flags 0x1005
|
||||||
device sio4 at isa? port 0x118 tty flags 0x1005
|
device sio4 at isa? port 0x118 flags 0x1005
|
||||||
…
|
…
|
||||||
device sio15 at isa? port 0x170 tty flags 0x1005
|
device sio15 at isa? port 0x170 flags 0x1005
|
||||||
device sio16 at isa? port 0x178 tty flags 0x1005 irq 3 vector siointr</programlisting>
|
device sio16 at isa? port 0x178 flags 0x1005 irq 3</programlisting>
|
||||||
|
|
||||||
<para>The flags entry <emphasis>must</emphasis> be changed
|
<para>The flags entry <emphasis>must</emphasis> be changed
|
||||||
from this example unless you are using the exact same
|
from this example unless you are using the exact same
|
||||||
|
@ -2249,11 +2247,11 @@ IRQ 2 3 4 5 Diode</programlisting>
|
||||||
this example, we would configure:</para>
|
this example, we would configure:</para>
|
||||||
|
|
||||||
<programlisting># standard on-board COM1 port
|
<programlisting># standard on-board COM1 port
|
||||||
device sio0 at isa? port "IO_COM1" tty flags 0x10
|
device sio0 at isa? port "IO_COM1" flags 0x10
|
||||||
# patched-up multi-I/O extension board
|
# patched-up multi-I/O extension board
|
||||||
options COM_MULTIPORT
|
options COM_MULTIPORT
|
||||||
device sio1 at isa? port "IO_COM2" tty flags 0x205
|
device sio1 at isa? port "IO_COM2" flags 0x205
|
||||||
device sio2 at isa? port "IO_COM3" tty flags 0x205 irq 3</programlisting>
|
device sio2 at isa? port "IO_COM3" flags 0x205 irq 3</programlisting>
|
||||||
|
|
||||||
<para>Note that the <literal>flags</literal> setting for
|
<para>Note that the <literal>flags</literal> setting for
|
||||||
<devicename>sio1</devicename> and
|
<devicename>sio1</devicename> and
|
||||||
|
@ -2303,7 +2301,7 @@ sio2: type 16550A (multiport master)</screen>
|
||||||
kernel configuration (note that your irq and iomem
|
kernel configuration (note that your irq and iomem
|
||||||
settings may differ).</para>
|
settings may differ).</para>
|
||||||
|
|
||||||
<programlisting>device cy0 at isa? tty irq 10 iomem 0xd4000 iosiz 0x2000 vector cyintr</programlisting>
|
<programlisting>device cy0 at isa? irq 10 iomem 0xd4000 iosiz 0x2000</programlisting>
|
||||||
</step>
|
</step>
|
||||||
|
|
||||||
<step>
|
<step>
|
||||||
|
@ -2386,7 +2384,7 @@ ttyc7 "/usr/libexec/getty std.38400" unknown on insecure</programlisting>
|
||||||
your kernel configuration file, changing the numbers as
|
your kernel configuration file, changing the numbers as
|
||||||
appropriate:</para>
|
appropriate:</para>
|
||||||
|
|
||||||
<programlisting>device si0 at isa? tty iomem 0xd0000 irq 11</programlisting>
|
<programlisting>device si0 at isa? iomem 0xd0000 irq 11</programlisting>
|
||||||
|
|
||||||
<para>Valid IRQ numbers are 9, 10, 11, 12 and 15 for SX ISA host
|
<para>Valid IRQ numbers are 9, 10, 11, 12 and 15 for SX ISA host
|
||||||
cards and 11, 12 and 15 for SI/XIO ISA host cards.</para>
|
cards and 11, 12 and 15 for SI/XIO ISA host cards.</para>
|
||||||
|
|
Loading…
Reference in a new issue