summaryrefslogtreecommitdiffstats
path: root/drivers/base/Kconfig
diff options
context:
space:
mode:
authorAdrian Bunk <bunk@kernel.org>2008-06-10 19:04:08 +0300
committerGreg Kroah-Hartman <gregkh@suse.de>2008-07-21 21:54:58 -0700
commitd9b19199e4894089456aaad295023263b5225c1a (patch)
tree97408cdde56ac71d05d3d0429617a1a2d3ba25da /drivers/base/Kconfig
parent4f7e53096c93f0bdf2205134dfc541d0c3cc6e41 (diff)
downloadop-kernel-dev-d9b19199e4894089456aaad295023263b5225c1a.zip
op-kernel-dev-d9b19199e4894089456aaad295023263b5225c1a.tar.gz
always enable FW_LOADER unless EMBEDDED=y
James Bottomley recently discovered that we have {request,release}_firmware() dummies for the case of the actual functions not being available and has a fix for the bug that was actually causing build errors for built-in users with CONFIG_FW_LOADER=m. But now missing selects on FW_LOADER are no longer visible at compile-time at all and can become runtime problems. FW_LOADER is infrastructure with relatively small codesize we can safely enable for everyone, and only for people who really need small kernels (and can be expected to know what they are doing) it matters being able to disable it. This patch therefore always sets FW_LOADER=y and allows users only to disable it with EMBEDDED=y. As a bonus, we can then get rid of all "select FW_LOADER" plus the due to it required "depends on HOTPLUG" which removes some complexity from our Kconfig files. Signed-off-by: Adrian Bunk <bunk@kernel.org> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Diffstat (limited to 'drivers/base/Kconfig')
-rw-r--r--drivers/base/Kconfig3
1 files changed, 2 insertions, 1 deletions
diff --git a/drivers/base/Kconfig b/drivers/base/Kconfig
index d47482f..6318f6b 100644
--- a/drivers/base/Kconfig
+++ b/drivers/base/Kconfig
@@ -27,8 +27,9 @@ config PREVENT_FIRMWARE_BUILD
If unsure say Y here.
config FW_LOADER
- tristate "Userspace firmware loading support"
+ tristate "Userspace firmware loading support" if EMBEDDED
depends on HOTPLUG
+ default y
---help---
This option is provided for the case where no in-kernel-tree modules
require userspace firmware loading support, but a module built outside
OpenPOWER on IntegriCloud