Message-ID: <46B87ACA.7010501@urjc.es>
Date: Tue, 07 Aug 2007 15:59:38 +0200
From: Javier Pello <javier.pello@urjc.es>
Organization: Universidad Rey Juan Carlos
User-Agent: Thunderbird 2.0.0.0 (X11/20070503)
MIME-Version: 1.0
To: Kay Sievers <kay.sievers@vrfy.org>
CC: Cornelia Huck <cornelia.huck@de.ibm.com>, linux-kernel@vger.kernel.org,
       Greg KH <greg@kroah.com>
Subject: Re: [PATCH] request_firmware: skip timeout if userspace was not 
	notified
References: <46B37CF7.2020803@urjc.es> 
		<20070806142451.5d28d41c@gondolin.boeb lingen.de.ibm.com> 
		<46B7832B.6010808@urjc.es> <20070807125844.4d756b04@gondo 
		l	in.boeblingen.de.ibm.com> 
		<3ae72650708070446y6452d13jb7cd802119dab3ce@mail .gmail.com> 
		<20070807141030.1bb0f76a@gondolin.boeblingen.de.ibm.com> 
		<46B869C6.3090708@urjc.es> <1186491472.3611.33.camel@lov.localdomain>
In-Reply-To: <1186491472.3611.33.camel@lov.localdomain>
Content-Type: text/plain;
	charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1056
Lines: 27

On Tue, 07 Aug 2007, Kay Sievers wrote:

> If you don't have modules and the initial request fails, how do you
> load the firmware later?

I trigger a rebinding of the device to the driver in an init file:
# echo -n [device] >/sys/.../bind

> The real fix would be to change the driver not to block in the
> firmware request and use async version of firmware loading. The
> whole firmware class with its silly timeout is just a piece of
> crap, that needs to be replaced.

I don't think that would be a real fix. You've done away with the
kernel blocking, but the timeout is still there, only that in the
background, and my point is still true: it is useless to wait at
all if userspace didn't receive the event. Waiting asynchronously
is less annoying than waiting synchronously, but equally useless.

Javier


-
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/