linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christian Lamparter <chunkeey@googlemail.com>
To: Marius Ladegaard Meyer <marius.l.meyer@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: carl9170 fw 1.9.3 on the binary archive page
Date: Wed, 25 May 2011 22:27:25 +0200	[thread overview]
Message-ID: <201105252227.25812.chunkeey@googlemail.com> (raw)
In-Reply-To: <BANLkTikR9pRgvFEh9ahFSk1KpdP9Oxz1Yw@mail.gmail.com>

On Wednesday 25 May 2011 21:26:32 Marius Ladegaard Meyer wrote:
> I built the firmware again today. After building the toolchain, I ran the
> autogen.sh script and selected the default values on all the things I was
> asked about. The script completed succesfully and created the files
> carl9170.bin, carl9170.dsc, carl9170.elf and carl9170.fw in the carlfw
> folder. I have attached the output in a text file.
output looks sane.

> It is at this point I cannot figure out what to do. The carl9170-1.fw files
> on the mirror just needs to be put in the /lib/firmware directory, and the
> kernel will find them when I plug in the device. I tried to copy all the
> aforementioned carl9170.* files to /lib/firmware, but all I see from dmesg
> is
> 
> [ 5416.799516] usb 2-6: new high speed USB device using ehci_hcd and address
> 5
> [ 5417.092852] usb 2-6: reset high speed USB device using ehci_hcd and
> address 5
> [ 5417.257236] usb 2-6: firmware not found.

the firmware filename is important. The driver can only load the firmware if it
is stored in the firmware folder with the right filename: "carl9170-1.fw"

the "-1" was introduced as a result of a rather long discussion about
firmware versioning best practices:
http://wireless.kernel.org/en/developers/Documentation/firmware-versioning

anyway cd into carl9170fw-source/carlfw and
cp carl9170.fw /lib/firmware/carl9170-1.fw
[If /lib/firmware is the correct directory]

this should do the trick.
> and iwconfig gives me no interface. I'm 100% sure that the error is between
> the chair and the keyboard on this one, but I cannot find any documentation
> on this anywhere.
oh no, you are 100% right. This was not documented anywhere in plain English,
but now it should be [just pushed].

Thanks,
	Chr

      parent reply	other threads:[~2011-05-25 20:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <BANLkTinenbgnE0c8ZQh2wfBOjWNc=T++Dw@mail.gmail.com>
2011-05-24 16:11 ` carl9170 fw 1.9.3 on the binary archive page Christian Lamparter
     [not found]   ` <BANLkTik7Gg81+KaB2eGnkpG8kSzTD7cwaw@mail.gmail.com>
2011-05-25 12:45     ` Christian Lamparter
     [not found]       ` <BANLkTikR9pRgvFEh9ahFSk1KpdP9Oxz1Yw@mail.gmail.com>
2011-05-25 20:27         ` Christian Lamparter [this message]

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=201105252227.25812.chunkeey@googlemail.com \
    --to=chunkeey@googlemail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=marius.l.meyer@gmail.com \
    /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).