From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kay Sievers Date: Mon, 31 Oct 2005 14:35:25 +0000 Subject: Re: Kernel Firmware Loading Message-Id: <20051031143525.GA780@vrfy.org> List-Id: References: <4365DBD9.2040407@ukonline.co.uk> In-Reply-To: <4365DBD9.2040407@ukonline.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org On Mon, Oct 31, 2005 at 02:27:35PM +0100, Duncan Sands wrote: > On Monday 31 October 2005 14:10, Kay Sievers wrote: > > On Mon, Oct 31, 2005 at 11:59:05AM +0100, Duncan Sands wrote: > > > It would be nice if the driver was more helpful here, > > > by trying to load the firmware more than once. It's > > > a bit tricky though. For example, you could say: "if > > > the firmware wasn't found, then try to load it when > > > someone opens a connection". Unfortunately, while this > > > is possible with the speedtch modem, this isn't possible > > > with the connexant access runner: you can't correctly create > > > an ATM device unless the firmware was already loaded into > > > the modem, which means it's impossible to even try to > > > open a connection before the firmware is loaded. Another > > > possibility is to try to load the firmware every couple > > > of seconds. I could certainly do that, but it's not very > > > elegant. > > > > > > In any case, I too am interested in hearing what the hotplug > > > people have to say. > > > > I like to see the stupid timeout in the request_firmware to completely > > go away. It doesn't make any sense. The drivers should use the async > > version of request_firmware() anyway and the so called syncronous version > > should be removed. > > that's fine with me, even though the loading in the speedtouch driver is > fundamentally synchronous (no useful work can be done until the firmware > is loaded): it is easy to build what I want on top of the async version. > > > If the kernel sends the request out and it gets lost during early boot, > > you can just fulfill it any time later by looking at the outstanding > > requests in sysfs. > > But isn't the problem different: the request did not get lost: it reached > the script (or whatever), the script couldn't find the firmware file and > cancelled the load? This has nothing to do with timeouts and events > getting lost... Well, just check with the firmware script and never cancel a request if you are in initramfs. Kay ------------------------------------------------------- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today * Register for a JBoss Training Course Free Certification Exam for All Training Attendees Through End of 2005 Visit http://www.jboss.com/services/certification for more information _______________________________________________ Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net Linux-hotplug-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel