[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LFD.1.10.0807141729200.3017@woody.linux-foundation.org>
Date: Mon, 14 Jul 2008 17:33:58 -0700 (PDT)
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: david@...g.hm
cc: Arjan van de Ven <arjan@...radead.org>,
Andrew Morton <akpm@...ux-foundation.org>,
David Woodhouse <dwmw2@...radead.org>,
alan@...rguk.ukuu.org.uk, linux-kernel@...r.kernel.org
Subject: Re: [GIT *] Allow request_firmware() to be satisfied from in-kernel,
use it in more drivers.
On Mon, 14 Jul 2008, david@...g.hm wrote:
>
> there was also the issue that was raised about how to handle firmware during
> suspend/resume. I don't remember seeing a happy solution to that one.
I don't understand why this even keeps coming up.
The only reliable way to handle it is to load the firmware before the
suspend happens - preferably by simply never unloading it in the first
place.
Anything else is fraught with problems.
Stuff that expects to eject itself anyway(*) over a suspend event can
obviously decide to throw it away and require a reload at resume time (by
virtue of simply re-discovering the whole device!).
Everybody else should just keep the firmware in memory in the driver.
Does it waste some ram? Sure. Tough.
Linus
(*) eg some random USB device that really _really_ doesn't care and isn't
expected to be involved in any filesystem access - say a webcam.
--
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