Index: usr.sbin/pccard/pccardd/pccardd.8
===================================================================
RCS file: /home/ncvs/src/usr.sbin/pccard/pccardd/pccardd.8,v
retrieving revision 1.26
diff -u -r1.26 pccardd.8
--- usr.sbin/pccard/pccardd/pccardd.8	2002/07/14 14:44:49	1.26
+++ usr.sbin/pccard/pccardd/pccardd.8	2002/07/29 04:15:31
@@ -110,18 +110,6 @@
 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
-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
-disassociated from the hardware and then reassociated with different
-parameters.
-This will change significantly when loadable kernel
-modules are supported.
 .Pp
 SIGHUP causes
 .Nm