Return-path: Received: from mail-ee0-f46.google.com ([74.125.83.46]:62408 "EHLO mail-ee0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751441Ab2ABDY6 (ORCPT ); Sun, 1 Jan 2012 22:24:58 -0500 From: Marek Vasut To: Michael =?iso-8859-1?q?B=FCsch?= Subject: Re: loading firmware while usermodehelper disabled. Date: Mon, 2 Jan 2012 04:24:54 +0100 Cc: Alan Cox , Oliver Neukum , Linus Torvalds , Dave Jones , Linux Kernel , Larry Finger , Chaoming Li , "John W. Linville" , Matthew Garrett , "Greg Kroah-Hartman" , USB list , Linux Wireless List References: <20111230235421.GA6054@redhat.com> <20120101203945.0ebc2f55@pyramind.ukuu.org.uk> <20120101215000.04b13f43@milhouse> In-Reply-To: <20120101215000.04b13f43@milhouse> MIME-Version: 1.0 Content-Type: Text/Plain; charset="us-ascii" Message-Id: <201201020424.54444.marek.vasut@gmail.com> (sfid-20120102_042557_653023_52DB182C) Sender: linux-wireless-owner@vger.kernel.org List-ID: > On Sun, 1 Jan 2012 20:39:45 +0000 > > Alan Cox wrote: > > When you suspend the power gets killed so the device loses its firmware > > and goes back to being a firmware requesting thing on resume. > > > > Worse still - you don't easily know if the device is in fact new and was > > added while suspended, or was always there. > > > > So for those devices you do need to load the firmware into them > > automatically after the resume to work out what they are and get the MAC > > to see if its the same wireless card or not. > > Well, that does not prevent you from caching the firmware once you > got it from userspace and keep it until module unload (or probably device > close), so that it is already available on resume. That's actually wrong. If you cached every single firmware, the kernel would gulp down a lot of space that can't be swapped out! M