From: Johannes Berg <johannes@sipsolutions.net>
To: Dan Williams <dcbw@redhat.com>
Cc: Andrey Yurovsky <andrey@cozybit.com>,
David Woodhouse <dwmw2@infradead.org>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: libertas firmware naming confusing
Date: Fri, 22 May 2009 17:31:57 +0200 [thread overview]
Message-ID: <1243006317.4606.27.camel@johannes.local> (raw)
In-Reply-To: <1243005119.2461.15.camel@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1173 bytes --]
On Fri, 2009-05-22 at 11:11 -0400, Dan Williams wrote:
> > 2) in the USB case change the driver to load libertas/usb8688.bin
> > instead of just usb8688.bin and move one of the versions to that
> > filename in the linux-firmware tree.
>
> Yes, this should be done. I was unsure what the policy of breaking
> firmware filenames is, however.
You can always try to load the new name, and fall back to the old name.
> > The current situation is very stupid -- users can find the firmware in a
> > proper repository but it doesn't work out of the box!
>
> Nope, though these cards aren't usually found by "normal" users anyway.
True.
> However, I'd like to preserve the the distribution of different firmware
> versions in linux-firmware, so maybe we should simply point the drivers
> at specific versions and use module parameters to change the firmware
> version?
>
> modprobe libertas_sdio fwver=8
>
> would select libertas/86xx_v8_helper.bin for example, but by default we
> use v9 or something like that. Would that be acceptable?
Sure. Might make sense to document why you would ever want to use that
though.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
prev parent reply other threads:[~2009-05-22 15:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-22 8:02 libertas firmware naming confusing Johannes Berg
2009-05-22 15:11 ` Dan Williams
2009-05-22 15:31 ` Johannes Berg [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=1243006317.4606.27.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=andrey@cozybit.com \
--cc=dcbw@redhat.com \
--cc=dwmw2@infradead.org \
--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