linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Talbut <jt@dpets.co.uk>
To: linux-wireless@vger.kernel.org
Subject: Firmware loading with static kernel and initramfs
Date: Sun, 29 Jun 2014 18:15:15 +0100	[thread overview]
Message-ID: <53B049A3.7000803@dpets.co.uk> (raw)

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?

             reply	other threads:[~2014-06-29 17:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-29 17:15 John Talbut [this message]
2014-06-29 18:31 ` Firmware loading with static kernel and initramfs Larry Finger
2014-06-29 19:19   ` John Talbut
2014-06-29 22:11     ` Larry Finger
2014-06-30  5:09       ` John Talbut
2014-06-30  8:22         ` Arend van Spriel
2014-06-30  9:08           ` John Talbut

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=53B049A3.7000803@dpets.co.uk \
    --to=jt@dpets.co.uk \
    --cc=linux-wireless@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).