Message-ID: <53B049A3.7000803@dpets.co.uk> (sfid-20140629_192316_237097_2AFC0D41)
Date: Sun, 29 Jun 2014 18:15:15 +0100
From: John Talbut <jt@dpets.co.uk>
MIME-Version: 1.0
To: linux-wireless@vger.kernel.org
Subject: Firmware loading with static kernel and initramfs
Content-Type: text/plain; charset=UTF-8; format=flowed
Sender: linux-wireless-owner@vger.kernel.org

There seems to be a general problem when using a static kernel and 
initramfs in that the wireless drivers try to load firmware before the 
disks are mounted and the /lib/firmware folder is available.  Various 
people seem to have come across problems with firmware not loading, some 
of which seem to relate to this problem, which they have approached as 
if it is a problem with their particular driver.  However it seems to be 
a general problem and I have had it with three different drivers.

There seems to be a number of possible approaches to this: loading the 
firmware in an initramfs; changing the sequence in which wireless 
drivers start so that they wait until the disks are mounted; compiling 
the firmware into the kernel and loading the firmware as part of ifup. 
I see that the latter has been done for one driver 
(http://thread.gmane.org/gmane.linux.kernel.wireless.general/3390).

What is the current situation with this problem and what needs doing?