summaryrefslogtreecommitdiff
path: root/drivers/base
diff options
context:
space:
mode:
authormatt mooney <mfm@muteddisk.com>2011-06-12 11:17:31 -0700
committerGreg Kroah-Hartman <gregkh@suse.de>2011-07-01 15:12:03 -0700
commit156faf9080e0acf2b301c982e7a77cd6fbb2d0ad (patch)
tree730a11ec8256c03f80f5e5d5020494ab5f63031f /drivers/base
parent113647a281037d8b6f32e07f42a1328c7cd3da3b (diff)
driver-core: modify FIRMWARE_IN_KERNEL help message
The help message for the configuration variable was inconsistent with the way "make firmware_install" really works. Signed-off-by: matt mooney <mfm@muteddisk.com> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Diffstat (limited to 'drivers/base')
-rw-r--r--drivers/base/Kconfig8
1 files changed, 4 insertions, 4 deletions
diff --git a/drivers/base/Kconfig b/drivers/base/Kconfig
index 5fe7fd23ed65..52c675883684 100644
--- a/drivers/base/Kconfig
+++ b/drivers/base/Kconfig
@@ -84,10 +84,10 @@ config FIRMWARE_IN_KERNEL
help
The kernel source tree includes a number of firmware 'blobs'
that are used by various drivers. The recommended way to
- use these is to run "make firmware_install" and to copy the
- resulting binary files created in usr/lib/firmware/ of the
- kernel tree to /lib/firmware/ on your system so that they can
- be loaded by userspace helpers on request.
+ use these is to run "make firmware_install", which, after
+ converting ihex files to binary, copies all of the needed
+ binary files in firmware/ to /lib/firmware/ on your system so
+ that they can be loaded by userspace helpers on request.
Enabling this option will build each required firmware blob
into the kernel directly, where request_firmware() will find