[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070528205951.GB5911@ucw.cz>
Date: Mon, 28 May 2007 20:59:51 +0000
From: Pavel Machek <pavel@....cz>
To: Ray Lee <ray-lk@...rabbit.org>
Cc: "Rafael J. Wysocki" <rjw@...k.pl>,
Alan Stern <stern@...land.harvard.edu>,
pm list <linux-pm@...ts.linux-foundation.org>,
LKML <linux-kernel@...r.kernel.org>,
Matthew Garrett <mjg59@...f.ucam.org>,
Nigel Cunningham <nigel@...el.suspend2.net>,
Oliver Neukum <oliver@...kum.org>
Subject: Re: [RFC][PATCH -mm 3/3] PM: Disable _request_firmware before hibernation/suspend
Hi!
> >In fact, I'd like drivers to use notifiers to actually
> >load the firmware into
> >memory before hibernation/suspend. Namely, if there's
> >PM_PRE_FREEZE, the
> >driver calls request_firmware() from within the
> >notifier and saves the firmware
> >in memory for future use, if need be. Later, when
> >PM_POST_THAW comes, the
> >memory holding the firmware is released.
> >
> >Unfortunately there are drivers that call
> >request_firmware() directly from
> >.resume() which blocks until timeout expires and fails
> >anyway. I just wanted
> >this to fail immediately, without waiting.
>
> Stupid question time. Wouldn't it just be easier to have
> request_firmware() keep a copy of the firmware once it's
> been loaded?
> We're not talking about a lot of memory that would be
> wasted, and that
> way no drivers have to be changed.
Actually, I like this idea. Firmware problems magically disappear.
...unless someone uses x86 emulator in userland to POST graphics card.
You can't 'cache' that. But that's separate problem.
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-
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