From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755656AbbHYTqv (ORCPT ); Tue, 25 Aug 2015 15:46:51 -0400 Received: from mx2.suse.de ([195.135.220.15]:57315 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751042AbbHYTqu (ORCPT ); Tue, 25 Aug 2015 15:46:50 -0400 Date: Tue, 25 Aug 2015 21:46:48 +0200 Message-ID: From: Takashi Iwai To: "Luis R. Rodriguez" Cc: Liam Girdwood , "Jie, Yang" , joonas.lahtinen@linux.intel.com, Dmitry Torokhov , Tom Gundersen , Ming Lei , Al Viro , Greg Kroah-Hartman , Kay Sievers , Linus Torvalds , David Woodhouse , mcgrof@do-not-panic.com, linux-kernel@vger.kernel.org Subject: Re: Problems loading firmware using built-in drivers with kernels that use initramfs. In-Reply-To: <20150825193408.GR8051@wotan.suse.de> References: <1440449403.2469.35.camel@loki> <1440489900.2419.4.camel@loki> <20150825193408.GR8051@wotan.suse.de> User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL/10.8 Emacs/24.5 (x86_64-suse-linux-gnu) MULE/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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