summaryrefslogtreecommitdiffstats
path: root/usr.sbin/pccard
diff options
context:
space:
mode:
authorsheldonh <sheldonh@FreeBSD.org>2000-03-01 14:09:25 +0000
committersheldonh <sheldonh@FreeBSD.org>2000-03-01 14:09:25 +0000
commitb2240fc1c08ba82628285458b057b5f795a68a43 (patch)
tree5acb2bdc9bc2d2c26e220a424cc6f0b29df60dec /usr.sbin/pccard
parent3197c29bd1de99eb5100db75bfb4d651f6878fa7 (diff)
downloadFreeBSD-src-b2240fc1c08ba82628285458b057b5f795a68a43.zip
FreeBSD-src-b2240fc1c08ba82628285458b057b5f795a68a43.tar.gz
Remove single-space hard sentence breaks. These degrade the quality
of the typeset output, tend to make diffs harder to read and provide bad examples for new-comers to mdoc.
Diffstat (limited to 'usr.sbin/pccard')
-rw-r--r--usr.sbin/pccard/pccardc/pccardc.83
-rw-r--r--usr.sbin/pccard/pccardd/pccard.conf.530
-rw-r--r--usr.sbin/pccard/pccardd/pccardd.815
3 files changed, 32 insertions, 16 deletions
diff --git a/usr.sbin/pccard/pccardc/pccardc.8 b/usr.sbin/pccard/pccardc/pccardc.8
index a5d0968..c790d2d 100644
--- a/usr.sbin/pccard/pccardc/pccardc.8
+++ b/usr.sbin/pccard/pccardc/pccardc.8
@@ -171,7 +171,8 @@ It turns ON/OFF a power supply of a card in the slot specified in
.Pp
.Bl -tag -width Ds
.It Ar 0
-turn OFF a power supply. If a card becomes unstable when it is removed at
+turn OFF a power supply.
+If a card becomes unstable when it is removed at
activate state,
this can force it to turn into inactive state first and remove it safely.
.It Ar 1
diff --git a/usr.sbin/pccard/pccardd/pccard.conf.5 b/usr.sbin/pccard/pccardd/pccard.conf.5
index c10c4d2..999f18e 100644
--- a/usr.sbin/pccard/pccardd/pccard.conf.5
+++ b/usr.sbin/pccard/pccardd/pccard.conf.5
@@ -58,9 +58,11 @@ Each PC-CARD card contains configuration tuples that provide
the manufacturer and card version; these are used
to identify the card specification in the configuration
file, and from this find a driver that can be used to
-interface to the particular card. There is a many-to-one mapping
+interface to the particular card.
+There is a many-to-one mapping
between cards to drivers i.e a single driver may interface to
-multiple types of cards. To aid this, card parameters may be
+multiple types of cards.
+To aid this, card parameters may be
specified separately from the driver to initialize the card or
extract (in the case of a network card) an Ethernet address.
.Pp
@@ -77,7 +79,8 @@ and
.Em remove
commands allow a shell command line to be executed.
The command to be executed is the rest of the line after
-the keyword. The line can be continued using a backslash.
+the keyword.
+The line can be continued using a backslash.
A simple
macro substitution allows the current kernel device name
.Em ( $device )
@@ -101,7 +104,8 @@ A hash character comments out the rest of the line.
.Ss "Resource pool"
The (optional) section specifies a pool of system resources
such as ISA bus memory address space, Input/Output ports and
-interrupt request numbers. This resource pool is used
+interrupt request numbers.
+This resource pool is used
to allocate address space and interrupt numbers dynamically
according to the requirements specified in each driver
description.
@@ -134,18 +138,21 @@ The syntax for card identifiers is:
.Pp
The first line is mandatory;
the latter statements are optional and can appear in
-any order. There may be multiple
+any order.
+There may be multiple
.Em config
lines.
The
.Em card
parameters are the Manufacturer name and card version that
-is used to match the values from the card's CIS memory. The
+is used to match the values from the card's CIS memory.
+The
.Em config
parameters select the particular card's configuration index
from the range available in the card's CIS, the driver that
is to be associated with this configuration, and the interrupt
-level (if any) to be assigned. An optional set of flags may
+level (if any) to be assigned.
+An optional set of flags may
be assigned.
In
.Ar index ,
@@ -156,9 +163,11 @@ from the CIS and status of using I/O resources.
The optional
.Em ether
keyword is used when network cards have their physical Ethernet address
-located within the attribute memory of the card. The parameter of this
+located within the attribute memory of the card.
+The parameter of this
statement indicates the offset within the attribute memory of the
-Ethernet address. This value can be used within insert/remove
+Ethernet address.
+This value can be used within insert/remove
commands using the
.Em $ether
macro.
@@ -168,7 +177,8 @@ The
and
.Em remove
sections allow shell commands to be specified that are executed
-when the card is inserted or removed. Multiple
+when the card is inserted or removed.
+Multiple
.Em insert
and
.Em remove
diff --git a/usr.sbin/pccard/pccardd/pccardd.8 b/usr.sbin/pccard/pccardd/pccardd.8
index 8fb912d..6013255 100644
--- a/usr.sbin/pccard/pccardd/pccardd.8
+++ b/usr.sbin/pccard/pccardd/pccardd.8
@@ -82,7 +82,8 @@ this card.
If the attach succeeds, then specific shell commands
may be executed to configure the device, such as
.Xr ifconfig 8
-to set up a network interface. Separate commands may be specified
+to set up a network interface.
+Separate commands may be specified
for each card, driver or device, and are executed in that order.
.El
.Pp
@@ -91,7 +92,8 @@ When
detects that a card has been removed, the following sequence occurs:
.Bl -enum
.It
-The shell commands associated with card removal are executed. These
+The shell commands associated with card removal are executed.
+These
are intended to reset any device associated with the removed card.
Separate commands may exist for card, driver and device instances.
.It
@@ -100,15 +102,18 @@ The PC-CARD slot resources are freed.
.Pp
Once a card/driver instance is configured, the resources
bound to that instance are remembered, and if the card is removed
-and reinserted, the same driver is allocated. The primary reason
+and reinserted, the same driver is allocated.
+The primary reason
is that once a driver is associated with a card, the
driver's
.Fn probe
routine has been called, and this usually causes driver specific
data areas to be initialized with the I/O ports or memory resources
-allocated to the card. Most drivers are not designed to be
+allocated to the card.
+Most drivers are not designed to be
disassociated from the hardware and then reassociated with different
-parameters. This will change significantly when loadable kernel
+parameters.
+This will change significantly when loadable kernel
modules are supported.
.Pp
The start options understood by
OpenPOWER on IntegriCloud