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 -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
