From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mms2.broadcom.com ([216.31.210.18]:4978 "EHLO mms2.broadcom.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758943Ab2EKKzw (ORCPT ); Fri, 11 May 2012 06:55:52 -0400 Message-ID: <4FACF02B.7070006@broadcom.com> (sfid-20120511_125610_842797_99EB0665) Date: Fri, 11 May 2012 12:55:39 +0200 From: "Arend van Spriel" MIME-Version: 1.0 To: "Kay Sievers" , "linux-wireless@vger.kernel.org" , "linux-kernel@vger.kernel.org" Subject: in-kernel drivers and firmware loader Content-Type: text/plain; charset=iso-8859-1 Sender: linux-wireless-owner@vger.kernel.org List-ID: Hi Kay, To my memory (which fails from time to time) you posted a message on using the asynchronous API for firmware loading as some drivers were blocking on it in the module initialization. So for our driver we decoupled the initialization from probe and subsequently the firmware request. Assuming this solves the udev issue, but I am currently looking into a somewhat related issue with our driver built-in. I am testing on a PandaBoard which boots a linux kernel without a initrd and our device is detected before the root filesystem is mounted. I was expecting the async firmware request to get called back immediatly with firmware pointer being NULL. The behaviour is slightly different as this callback is coming after 60 seconds, which is the timeout. I guess the uevent just gets lost without the kernel knowing it. Is that correct? Gr. AvS