All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Gamari <bgamari.foss@gmail.com>
To: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: wl1271 NVS file loading
Date: Sun, 01 Apr 2012 20:10:23 -0400	[thread overview]
Message-ID: <87pqbrj8nk.fsf@gmail.com> (raw)
In-Reply-To: <877gxz6n9i.fsf@gmail.com>

Ben Gamari <bgamari.foss@gmail.com> writes:

> Hello all,
>
> I'm running a PandaBoard with Linaro 12.03 and a patched 3.3
> kernel. While wl1271 works perfectly with the Linaro kernel, it fails to
> load in the case of my patched kernel with,
>
>      wl12xx: ERROR could not get nvs file ti-connectivity/wl1271-nvs.bin: -2
>
> What is even more perplexing is the fact that the file in question
> clearly exists,
>
>         $ ls /lib/firmware/ti-connectivity/*-nvs.bin -l
>         -rw-r--r-- 1 root root  912 2012-03-24 16:28 /lib/firmware/ti-connectivity/wl1271-nvs.bin
>         -rw-r--r-- 1 root root  912 2012-03-24 16:28 /lib/firmware/ti-connectivity/wl127x-nvs.bin
>         -rw-r--r-- 1 root root 1113 2012-03-24 16:28 /lib/firmware/ti-connectivity/wl128x-nvs.bin
>         lrwxrwxrwx 1 root root   14 2012-01-24 13:10 /lib/firmware/ti-connectivity/wl12xx-nvs.bin -> wl127x-nvs.bin
>
> It seems that there is no easy way to troubleshoot udev's
> /lib/udev/firmware script, so I have really no way of tracking this down
> any further. Any ideas what might be going on here?
>
It turns out I had neglected to compile wl1271 as a module and the
firmware hadn't made it into the initrd.  I apologize for the noise.

Cheers,

- Ben


       reply	other threads:[~2012-04-02  0:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <877gxz6n9i.fsf@gmail.com>
2012-04-02  0:10 ` Ben Gamari [this message]
2012-04-02  8:54   ` wl1271 NVS file loading Luciano Coelho
2013-07-09 14:16     ` Ben Gamari

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=87pqbrj8nk.fsf@gmail.com \
    --to=bgamari.foss@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.