Return-path: Received: from lxorguk.ukuu.org.uk ([81.2.110.251]:39964 "EHLO lxorguk.ukuu.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753302Ab2ABXuj (ORCPT ); Mon, 2 Jan 2012 18:50:39 -0500 Date: Mon, 2 Jan 2012 23:50:44 +0000 From: Alan Cox To: Linus Torvalds Cc: Jack Stone , Alan Stern , Oliver Neukum , Matthew Garrett , Dave Jones , Linux Kernel , Larry Finger , Chaoming Li , "John W. Linville" , Greg Kroah-Hartman , USB list , Linux Wireless List Subject: Re: loading firmware while usermodehelper disabled. Message-ID: <20120102235044.23935096@pyramind.ukuu.org.uk> (sfid-20120103_005116_568271_29E5ECEB) In-Reply-To: References: <4F02165C.1060400@fastmail.fm> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-wireless-owner@vger.kernel.org List-ID: > So the only thing we need is to fix the braindamaged firmware > interfaces. We need caching, and we need to replace (or at least > extend) "load_firware()" with "[get|put]_firmware()". So at what moment after a resume does a firmware that was in use with a device go away and what do we do about devices inserted while suspended ? Remembering that - there is no moment when USB says 'we have finished re-enumeration'. There is no point at which you can say 'we have finished re-enumeration, we are now starting on enumeration of new stuff'. New stuff wanting firmware will pop up on resume mixed in with old stuff. - we don't seem to have any device or bus infrastructure for doing a 'post resume' purge of such data if we could decide when that moment is ? Alan