lkml.org 
[lkml]   [2017]   [Dec]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    Patch in this message
    /
    From
    Subject[PATCH 4.14 030/164] firmware: cleanup FIRMWARE_IN_KERNEL message
    Date
    4.14-stable review patch.  If anyone has any objections, please let me know.

    ------------------

    From: Robin H. Johnson <robbat2@gentoo.org>

    commit 0946b2fb38fdb6585a5ac3ca84ac73924f645952 upstream.

    The help for FIRMWARE_IN_KERNEL still references the firmware_install
    command that was recently removed by commit 5620a0d1aacd ("firmware:
    delete in-kernel firmware").

    Clean up the message to direct the user to their distribution's
    linux-firmware package, and remove any reference to firmware being
    included in the kernel source tree.

    Fixes: 5620a0d1aacd ("firmware: delete in-kernel firmware").
    Cc: Masahiro Yamada <yamada.masahiro@socionext.com>
    Cc: David Woodhouse <dwmw2@infradead.org>
    Signed-off-by: Robin H. Johnson <robbat2@gentoo.org>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

    ---
    drivers/base/Kconfig | 25 +++++++++++++------------
    1 file changed, 13 insertions(+), 12 deletions(-)

    --- a/drivers/base/Kconfig
    +++ b/drivers/base/Kconfig
    @@ -91,22 +91,23 @@ config FIRMWARE_IN_KERNEL
    depends on FW_LOADER
    default y
    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", 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.
    + Various drivers in the kernel source tree may require firmware,
    + which is generally available in your distribution's linux-firmware
    + package.
    +
    + The linux-firmware package should install firmware into
    + /lib/firmware/ on your system, so 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
    - them without having to call out to userspace. This may be
    - useful if your root file system requires a device that uses
    - such firmware and do not wish to use an initrd.
    + specified by EXTRA_FIRMWARE into the kernel directly, where
    + request_firmware() will find them without having to call out to
    + userspace. This may be useful if your root file system requires a
    + device that uses such firmware and you do not wish to use an
    + initrd.

    This single option controls the inclusion of firmware for
    - every driver that uses request_firmware() and ships its
    - firmware in the kernel source tree, which avoids a
    + every driver that uses request_firmware(), which avoids a
    proliferation of 'Include firmware for xxx device' options.

    Say 'N' and let firmware be loaded from userspace.

    \
     
     \ /
      Last update: 2017-12-12 15:02    [W:4.144 / U:0.288 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site