Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S269104AbUIXULX (ORCPT ); Fri, 24 Sep 2004 16:11:23 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S269107AbUIXULX (ORCPT ); Fri, 24 Sep 2004 16:11:23 -0400 Received: from coyote.holtmann.net ([217.160.111.169]:51615 "EHLO mail.holtmann.net") by vger.kernel.org with ESMTP id S269104AbUIXULV (ORCPT ); Fri, 24 Sep 2004 16:11:21 -0400 Subject: Re: suspend/resume support for driver requires an external firmware From: Marcel Holtmann To: "Zhu, Yi" Cc: Patrick Mochel , Linux Kernel Mailing List In-Reply-To: References: Content-Type: text/plain Message-Id: <1096056665.6925.45.camel@pegasus> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Fri, 24 Sep 2004 22:11:05 +0200 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 808 Lines: 22 Hi, > Current state is the patch makes ipw2100 suspend/resume work in the expense > of addtional ~200k kernel runtime memory. So I'd rather look on it as a > workaround instead of a finial solution. it consumes extra runtime memory, but why not build a simple firmware cache behind the request_firmware() interface. In this case it can be transparent for the driver and we won't have an extra workaround for suspend/resume stuff for every driver. How many firmwares do a normal system really have to hold in memory for suspend/resume actions? Regards Marcel - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/