From 60c906cc9624b1c6e91b8577f8c75de8b9867a3b Mon Sep 17 00:00:00 2001 From: matt mooney Date: Sun, 12 Jun 2011 11:17:31 -0700 Subject: [PATCH] --- yaml --- r: 259186 b: refs/heads/master c: 156faf9080e0acf2b301c982e7a77cd6fbb2d0ad h: refs/heads/master v: v3 --- [refs] | 2 +- trunk/drivers/base/Kconfig | 8 ++++---- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/[refs] b/[refs] index a055e2a2dfc8..3027a1007c4d 100644 --- a/[refs] +++ b/[refs] @@ -1,2 +1,2 @@ --- -refs/heads/master: 113647a281037d8b6f32e07f42a1328c7cd3da3b +refs/heads/master: 156faf9080e0acf2b301c982e7a77cd6fbb2d0ad diff --git a/trunk/drivers/base/Kconfig b/trunk/drivers/base/Kconfig index 5fe7fd23ed65..52c675883684 100644 --- a/trunk/drivers/base/Kconfig +++ b/trunk/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