On Tue, 2007-05-29 at 13:00 +0100, Michael-Luke Jones wrote: > Rafael J. Wysocki wrote: > > On Tuesday, 29 May 2007 08:55, Kay Sievers wrote: > >> The shiny userspace firmware loading causes problems since it exists, > >> every second box has problems with it, in all sorts of situations. If > >> people are still sold to the idea of userspace firmware loading, why > >> don't we keep the data in the driver, instead of immediately > >> discarding it after the first upload? Not to waste a few hundred > >> kilobytes? That doesn't sound like a convincing deal, after all the > >> years people try to work around the issues it causes. > > > > Agreed. > > > > Rafael > > Rather than most drivers being told to make this step, can this be added > to the firmware_class such that firmware objects are cached in RAM and > subsequent calls to request_firmware() don't have to query userspace. > > This seems the least intrusive solution to this problem.
Who is going to keep track of the data hiding in the firmware_class? On driver unbind, module unload, you want to release the data. Kay - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
