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] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LFD.1.10.0807150931010.3017@woody.linux-foundation.org>
Date:	Tue, 15 Jul 2008 09:35:56 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Frans Pop <elendil@...net.nl>
cc:	jeff@...zik.org, arjan@...radead.org, akpm@...ux-foundation.org,
	dwmw2@...radead.org, alan@...rguk.ukuu.org.uk,
	linux-kernel@...r.kernel.org
Subject: Re: [GIT *] Allow request_firmware() to be satisfied from in-kernel,
 use it in more drivers.



On Tue, 15 Jul 2008, Linus Torvalds wrote:
> 
> Why don't you just take the kernel-supplied firmware and make it part of 
> the kernel package? The same way the kernel-supplied modules are part of 
> it?

And, btw, if there is something we can do to help, we obviously should.

So ask yourself (and DavidW) things like

 - Is "make firmware_install" not enough for the package build system?

 - Does it need some other way to figure out what firmware is needed for 
   just the configured set of drivers, eg "make firmware_list"?

 - Do we need to make the firmware loader have multiple directories it 
   looks at? Do we want first a kernel-version-specific one, then a 
   generic fallback one, so that we can easily have per-kernel firmware, 
   the same way we have per-kernel modules?

 - Add your interesting question here.

There are obviously all these kinds of _productive_ questions you can ask. 
But people seem to be mostly in an unproductive "Mommy, it hurts when I do 
something stupid" mode.

			Linus
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ