summaryrefslogtreecommitdiffstats
path: root/share
diff options
context:
space:
mode:
authorsam <sam@FreeBSD.org>2008-08-02 17:51:38 +0000
committersam <sam@FreeBSD.org>2008-08-02 17:51:38 +0000
commitdc31c987908c02ffe5657ad49907f92497939ffe (patch)
treed8cdae80f71ee9cb3506ce409513f4ebfcfe2fd6 /share
parentf28149353a8d84e6d26ce1feac18f3225125ceaf (diff)
downloadFreeBSD-src-dc31c987908c02ffe5657ad49907f92497939ffe.zip
FreeBSD-src-dc31c987908c02ffe5657ad49907f92497939ffe.tar.gz
Try to fixup last (inadvertent) commit: firmware_drain was never added so
yank it's description; likewise for the FIRMWARE_WAIT flag to firmware_put. For the record, the last commit was to cleanup various mistakes and correct the example of embedding to reflect the npe firmware now being distributed with the system.
Diffstat (limited to 'share')
-rw-r--r--share/man/man9/firmware.916
1 files changed, 1 insertions, 15 deletions
diff --git a/share/man/man9/firmware.9 b/share/man/man9/firmware.9
index e010159..87d43e3 100644
--- a/share/man/man9/firmware.9
+++ b/share/man/man9/firmware.9
@@ -23,7 +23,7 @@
.\"
.\" $FreeBSD$
.\"
-.Dd May 18, 2008
+.Dd August 2, 2008
.Os
.Dt FIRMWARE 9
.Sh NAME
@@ -31,7 +31,6 @@
.Nm firmware_unregister ,
.Nm firmware_get ,
.Nm firmware_put
-.Nm firmware_drain
.Nd firmware image loading and management
.Sh SYNOPSIS
.In sys/param.h
@@ -60,8 +59,6 @@ struct firmware {
.Fn firmware_get "const char *imagename"
.Ft void
.Fn firmware_put "const struct firmware *fp" "int flags"
-.Ft void
-.Fn firmware_drain "void"
.Sh DESCRIPTION
The
.Nm firmware
@@ -164,17 +161,6 @@ By default a firmware image will be deferred to a
.Xr taskqueue 9
thread so the call may be done while holding a lock.
In certain cases, such as on driver detach, this cannot be allowed.
-If the
-.Dv FIRMWARE_WAIT
-flag is or'd into
-.Fa flags
-then
-.Fn firmware_put
-will wait for the asynchronous operation to complete.
-This can also be accomplished by calling the
-.Fn firmware_drain
-routine after
-.Fn firmware_put .
.Sh FIRMWARE LOADING MECHANISMS
As mentioned before, any component of the system can register
firmware images at any time by simply calling
OpenPOWER on IntegriCloud