linux-kernel - Re: Problems loading firmware using built-in drivers with kernels that use initramfs.

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: <s5h4mjnnobb.wl-tiwai@suse.de>
Date:	Tue, 25 Aug 2015 21:46:48 +0200
From:	Takashi Iwai <tiwai@...e.de>
To:	"Luis R. Rodriguez" <mcgrof@...e.com>
Cc:	Liam Girdwood <liam.r.girdwood@...el.com>,
	"Jie, Yang" <yang.jie@...el.com>, joonas.lahtinen@...ux.intel.com,
	Dmitry Torokhov <dmitry.torokhov@...il.com>,
	Tom Gundersen <teg@...m.no>, Ming Lei <ming.lei@...onical.com>,
	Al Viro <viro@...iv.linux.org.uk>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Kay Sievers <kay@...y.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	David Woodhouse <dwmw2@...radead.org>, mcgrof@...not-panic.com,
	linux-kernel@...r.kernel.org
Subject: Re: Problems loading firmware using built-in drivers with kernels that use initramfs.

On Tue, 25 Aug 2015 21:34:08 +0200,
Luis R. Rodriguez wrote:
> 
> On Tue, Aug 25, 2015 at 10:17:00AM +0100, David Woodhouse wrote:
> > Luis, did you tell me the other day that you made the kernel get firmware
> > directly from the file system? This regression would be yours then?
> 
> I didn't implement that, Linus did in 2012 (see commit abb139e75c2c titled
> "firmware: teach the kernel to load firmware files directly from the
> filesystem"). But we used to fallback to a userspace helper when the fw was
> not present and then Takashi made this optional via commit 7b1269f778782d
> titled "firmware: Make user-mode helper optional". Takashi noted in the
> Kconfig "The user-mode helper is no longer required unless you have a
> special firmware file that resides in a non-standard path". It was not
> clarified why that's true though, or what you'd need to do to ensure
> that the fw would be available. It would be good for us to elaborate
> on that.

The recent udev already dropped the firmware loading feature.


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