From mboxrd@z Thu Jan 1 00:00:00 1970 From: Patrick Mansfield Date: Tue, 08 Nov 2005 18:37:19 +0000 Subject: Re: Kernel Firmware Loading Message-Id: <20051108183719.GA22829@us.ibm.com> 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 Tue, Nov 08, 2005 at 01:16:25PM +0500, Alexander E. Patrakov wrote: > Patrick Mansfield wrote: > > >So the proposed (or current?) hotplug firmware interface can block other > >PCI (or other) devices from binding? > > > > > I am not sure what exactly you mean. Attempting to answer anyway for the > current firmware implementation. > > For an experiment, I created a simple "driver" for a PCI device, that > only calls request_firmware() in its probe() function and does nothing > else. I built this driver as a non-module and booted the resulting kernel. > > The boot process was indeed delayed by 10 seconds while this driver > waited for its "firmware". After that delay, the kernel proceeded as > usual. If I provide the "firmware" in initramfs, no delay occurs. Thanks, I was wondering what happens in the above scenario, that and Greg's email explain it. -- Parick Mansfield ------------------------------------------------------- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _______________________________________________ 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