[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120102235044.23935096@pyramind.ukuu.org.uk>
Date: Mon, 2 Jan 2012 23:50:44 +0000
From: Alan Cox <alan@...rguk.ukuu.org.uk>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Jack Stone <jwjstone@...tmail.fm>,
Alan Stern <stern@...land.harvard.edu>,
Oliver Neukum <oliver@...kum.org>,
Matthew Garrett <mjg@...hat.com>,
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>,
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.
> 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
--
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