From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from sipsolutions.net (s3.sipsolutions.net [5.9.151.49]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 3tTCxq4phdzDvr1 for ; Wed, 30 Nov 2016 19:19:26 +1100 (AEDT) Message-ID: <1480493909.9990.31.camel@sipsolutions.net> Subject: Re: [RFC] fs: add userspace critical mounts event support From: Johannes Berg To: "Luis R. Rodriguez" , Tom Gundersen Cc: Linus Torvalds , Jiri Kosina , Jouni Malinen , Seth Forshee , Kay Sievers , Bjorn Andersson , Daniel Wagner , Daniel Wagner , "Rafael J. Wysocki" , "Herbert, Marc" , Daniel Vetter , Rob Landley , Mimi Zohar , Felix Fietkau , David Woodhouse , Roman Pen , Ming Lei , Andrew Morton , Michal Marek , Greg KH , Linux Kernel Mailing List , Vikram Mulukutla , Stephen Boyd , Mark Brown , Takashi Iwai , Christian Lamparter , Hauke Mehrtens , Josh Boyer , Dmitry Torokhov , Jiri Slaby , Andy Lutomirski , Wu Fengguang , Richard Purdie , Jeff Mahoney , Jacek Anaszewski , Abhay Salunke , Julia Lawall , Gilles.Muller@lip6.fr, nicolas.palix@imag.fr, David Howells , Alessandro Rubini , Kevin Cernekee , Kees Cook , Jonathan Corbet , Thierry Martinez , linux-serial , "open list:DOCUMENTATION" , linuxppc-dev , Josh Triplett Date: Wed, 30 Nov 2016 09:18:29 +0100 In-Reply-To: <20161129213739.GJ1402@wotan.suse.de> References: <20160825194133.GC3296@wotan.suse.de> <20160902235916.GO3296@wotan.suse.de> <20160903002014.GP3296@wotan.suse.de> <6332a54e-74c6-eafd-368e-71e87a3fa34e@landley.net> <20161005180017.GD3296@wotan.suse.de> <20161005194633.GE3296@wotan.suse.de> <20161108224726.GD13978@wotan.suse.de> <1479202125.12007.24.camel@sipsolutions.net> <20161129213739.GJ1402@wotan.suse.de> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Tue, 2016-11-29 at 22:37 +0100, Luis R. Rodriguez wrote: > On Tue, Nov 29, 2016 at 10:10:56PM +0100, Tom Gundersen wrote: > > > > On Tue, Nov 15, 2016 at 10:28 AM, Johannes Berg > > wrote: > > > > > > My argument basically goes like this: > > > > > > First, given good drivers (i.e. using request_firmware_nowait()) > > > putting firmware even for a built-in driver into initramfs or not > > > should be a system integrator decision. If they don't need the > > > device > > > that early, it should be possible for them to delay it. Or, > > > perhaps, if > > > the firmware is too big, etc. I'm sure we can all come up with > > > more > > > examples of why you'd want to do it one way or another. > > > > This is how I understood the the situation, but I never quite > > bought > > it. What is wrong with the kernel saying "you must put your module > > and > > your firmware together"? Sure, people may want to do things > > differently, but what is the real blocker? > > 0) Firmware upgrades are possible > 1) Some firmware is optional > 2) Firmware licenses may often not be GPLv2 compatible > 3) Some firmwares may be stupid large (remote-proc) as such >    neither built-in firmware nor using the firmware in initramfs >    is reasonable. 4) "firmware" may be on a separate flash partition because it's really    calibration data required by the (wifi) chip/driver    (to allow kernel updates without having to taylor the kernel image    to each and every device!! johannes