linux-kernel - Re: [GIT *] Allow request_firmware() to be satisfied from in-kernel, use it in more drivers.

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 for Android: free password hash cracker in your pocket

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

Date:	Wed, 16 Jul 2008 02:04:07 -0400
From:	Jeff Garzik <jeff@...zik.org>
To:	Chris Adams <cmadams@...aay.net>
CC:	linux-kernel@...r.kernel.org
Subject: Re: [GIT *] Allow request_firmware() to be satisfied from in-kernel,
  use it in more drivers.

Chris Adams wrote:
> Once upon a time, Jeff Garzik  <jeff@...zik.org> said:
>> * Red Hat driver disks.  The build process is unaware of the need to 
>> bundle firmware.  Any use with Fedora (or, later, RHEL) will result in a 
>> non-working driver, for the simple reason that firmware is not copied 
>> onto the image.
> 
> Then Red Hat driver disks are already broken, as there are current
> modules (e.g. qla2xxx) that require external firmware.

That doesn't change the problem any.  There are still users of this 
thing, regardless of what appellations are attached.

>> * Embedded projects like OpenWRT, that divide up kernel modules into 
>> multiple packages.  Since it's not just one big package, you have to 
>> update each package's list of files to include the newly split-out 
>> firmwares.  Failure to do so results in a successful build set of 
>> packages... of drivers that lack their firmware.
> 
> AFAIK OpenWRT and the like don't just throw in random new kernel
> releases without at least reading release notes and testing.

Sure.  The difference here is that we usually take care to make sure 
there is some way for the distributor to continue configuring their 
system in the manner known to work, while developing and testing new stuff.

But in this case, that option was not available to distributors (but 
hopefully it will be, in another day or two).

	Jeff

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/