summaryrefslogtreecommitdiffstats
path: root/usr.sbin/pccard
diff options
context:
space:
mode:
Diffstat (limited to 'usr.sbin/pccard')
-rw-r--r--usr.sbin/pccard/pccardd/pccard.conf.54
-rw-r--r--usr.sbin/pccard/pccardd/pccardd.84
2 files changed, 4 insertions, 4 deletions
diff --git a/usr.sbin/pccard/pccardd/pccard.conf.5 b/usr.sbin/pccard/pccardd/pccard.conf.5
index 96ad0cf..68a8421 100644
--- a/usr.sbin/pccard/pccardd/pccard.conf.5
+++ b/usr.sbin/pccard/pccardd/pccard.conf.5
@@ -59,7 +59,7 @@ file, and from this find a driver that can be used to
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
-specified separately from the driver to initialise the card or
+specified separately from the driver to initialize the card or
extract (in the case of a network card) an Ethernet address.
.Pp
Once a driver is allocated to a card, it stays
@@ -112,7 +112,7 @@ The syntax of the resources is as follows:
.Pp
Each of the statements define I/O, memory or IRQ
blocks that can be used to allocate to drivers when
-they are initialised.
+they are initialized.
.Pp
Multiple lines of any of the above statements may be
present to allow separate blocks of each resource to be
diff --git a/usr.sbin/pccard/pccardd/pccardd.8 b/usr.sbin/pccard/pccardd/pccardd.8
index a4ebb74..cf4d4c7 100644
--- a/usr.sbin/pccard/pccardd/pccardd.8
+++ b/usr.sbin/pccard/pccardd/pccardd.8
@@ -23,7 +23,7 @@
.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
.\"
-.\" $Id: pccardd.8,v 1.7 1997/02/22 16:08:58 peter Exp $
+.\" $Id: pccardd.8,v 1.8 1997/10/06 11:36:07 charnier Exp $
.\"
.Dd November 1, 1994
.Dt PCCARD 8
@@ -103,7 +103,7 @@ 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 initialised with the I/O ports or memory resources
+data areas to be initialized with the I/O ports or memory resources
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
OpenPOWER on IntegriCloud