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] [thread-next>] [day] [month] [year] [list]
Date:   Sat, 16 Sep 2017 06:51:06 +0200
From:   Markus Trippelsdorf <>
To:     Greg KH <>
Cc:     Linus Torvalds <>,
        Andrew Morton <>,
Subject: Re: [GIT PULL] Firmware files removal for 4.14-rc1

On 2017.09.15 at 11:56 -0700, Greg KH wrote:
> The following changes since commit 569dbb88e80deb68974ef6fdd6a13edb9d686261:
>   Linux 4.13 (2017-09-03 13:56:17 -0700)
> are available in the git repository at:
>   git:// tags/firmware_removal-4.14-rc1
> for you to fetch changes up to 5620a0d1aacd554ebebcff373e31107bb1ef7769:
>   firmware: delete in-kernel firmware (2017-09-14 14:49:41 -0700)
> ----------------------------------------------------------------
> Firmware removal patch for 4.14-rc1
> Many many years ago (at the kernel summit in Boston), we all came to the
> agreement that the firmware/ tree should be dropped from the kernel, and
> everyone use the linux-firmware package instead.  For some minor reason,
> David Woodhouse didn't send the pull request at that point in time, and
> everyone forgot about this.
> The topic came up in the hallway track at the Plumbers conference this
> week, so here's a single patch that drops the whole firmware tree.  The
> last firmware update was back in 2013, and all distros have been using
> linux-firmware instead since at least that year, if not before.  The
> only commits to that directory since 2013 was some kbuild fixups for
> various build tool issues.
> So lets finally drop this, we don't need to lug them around in the
> kernel source tree anymore, especially as no one wants or uses them.

Well, it is one thing to drop the redundant binary blobs. But is another
to break perfectly fine setups that worked for years, e.g.:

CONFIG_EXTRA_FIRMWARE="amd-ucode/microcode_amd.bin radeon/R600_rlc.bin"

Please restore the support for built-in firmware.


Powered by blists - more mailing lists