linux-kernel - Re: [PATCH] firmware: Restore support for built-in firmware

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Sat, 16 Sep 2017 09:57:05 -0700
From:   Greg KH <gregkh@...uxfoundation.org>
To:     Markus Trippelsdorf <markus@...ppelsdorf.de>
Cc:     Linus Torvalds <torvalds@...ux-foundation.org>,
        Kyle McMartin <kyle@...nel.org>,
        Andrew Morton <akpm@...ux-foundation.org>,
        Michal Marek <mmarek@...e.com>,
        Masahiro Yamada <yamada.masahiro@...ionext.com>,
        David Woodhouse <dwmw2@...radead.org>,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] firmware: Restore support for built-in firmware

On Sat, Sep 16, 2017 at 11:01:16AM +0200, Markus Trippelsdorf wrote:
> Commit 5620a0d1aac ("firmware: delete in-kernel firmware") removed the
> entire firmware directory. Unfortunately it thereby also removed the
> support for built-in firmware.

The goal was to delete the in-kernel firmware, why do you want to add it
back?

> This restores the ability to build firmware directly into the kernel by
> pruning the original Makefile to the necessary minimum. The default for
> EXTRA_FIRMWARE_DIR is now the standard directory /lib/firmware/.

But what firmware is this fixing the build for?

As I asked in the other email, I don't understand the problem here, but
it's early, and the Plumbers closing party lasted really late...

thanks,

greg k-h