[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <201201020424.54444.marek.vasut@gmail.com>
Date: Mon, 2 Jan 2012 04:24:54 +0100
From: Marek Vasut <marek.vasut@...il.com>
To: Michael Büsch <m@...s.ch>
Cc: Alan Cox <alan@...rguk.ukuu.org.uk>,
Oliver Neukum <oliver@...kum.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Dave Jones <davej@...hat.com>,
Linux Kernel <linux-kernel@...r.kernel.org>,
Larry Finger <Larry.Finger@...inger.net>,
Chaoming Li <chaoming_li@...lsil.com.cn>,
"John W. Linville" <linville@...driver.com>,
Matthew Garrett <mjg@...hat.com>,
"Greg Kroah-Hartman" <gregkh@...e.de>,
USB list <linux-usb@...r.kernel.org>,
Linux Wireless List <linux-wireless@...r.kernel.org>
Subject: Re: loading firmware while usermodehelper disabled.
> On Sun, 1 Jan 2012 20:39:45 +0000
>
> Alan Cox <alan@...rguk.ukuu.org.uk> 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
--
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/
Powered by blists - more mailing lists