linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Roskin <proski@gnu.org>
To: Pavel Roskin <proski@gnu.org>
Cc: Christian Lamparter <chunkeey@googlemail.com>,
	linux-wireless@vger.kernel.org
Subject: Re: Binary for carl9170
Date: Fri, 15 Jul 2011 18:49:00 -0400	[thread overview]
Message-ID: <4E20C3DC.3020200@gnu.org> (raw)
In-Reply-To: <20110715151642.0j86tyrj4k0g4sg4-cebfxv@webmail.spamcop.net>

On 07/15/2011 03:16 PM, Pavel Roskin wrote:
> Quoting Christian Lamparter <chunkeey@googlemail.com>:
>
>> So, since you already have a working version, why simply put it on the
>> wiki?
>
> Yes, I have a working version now (compiled with all defaults) and I'll
> try to upload it myself.

Oh well, I can upload it to wiki, but not to your page at 
http://www.kernel.org/pub/linux/kernel/people/chr/carl9170/fw/

That page is linked to on
http://linuxwireless.org/en/users/Drivers/carl9170.fw

I don't want to setup an alternative competing repository for carl9170 
firmwares.

The wiki allows attachments, so I uploaded the firmware as an 
attachment.  First I put is on the main carl9170 page, but it turned out 
that MoinMoin doesn't appear to have any way to specify the attachment 
name in the link.  Since I called the attachment "carl9170-1.fw-1.9.4", 
it would only download under that name, rather than as "carl9170-1.fw". 
  I don't want to call the attachment "carl9170-1.fw" since nobody, 
including me, would be able to replace it with another version ever.

So I created a separate wiki page for the 1.9.4 version of the firmware 
and attached the firmware to it as "carl9170-1.fw".  That's an 
equivalent of having directories with files having the same name.

The carl9170 page recommends 1.9.2 for all kernels up to 3.0.  The 1.9.4 
is recommended for compat-wireless.  If that's not your recommendation, 
please feel free to update the wiki.

I was able to verify that carl9170 from the Fedora kernel 
2.6.38.8-35.fc15.x86_64 works with firmware 1.9.4, even though it 
complains about unsupported features:

[  117.159395] usb 1-7: driver   API: 1.9.0 2010-10-29 [1-1]
[  117.164830] usb 1-7: firmware API: 1.9.4 2011-06-30
[  117.169740] usb 1-7: Unprotected firmware image.
[  117.174375] usb 1-7: driver does not support all firmware features.

Perhaps we could recommend 1.9.4 for more kernels?

Also, it would be nice to have the 1.9.4 firmware on 
http://www.kernel.org/pub/linux/kernel/people/chr/carl9170/fw/

-- 
Regards,
Pavel Roskin

  reply	other threads:[~2011-07-15 22:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CACAiNS3-3K06Cro+VWypyWGetUW-v0qeJ29noXi7WNtUaCWzTw@mail.gmail.com>
2011-07-14  9:19 ` Binary for carl9170 Christian Lamparter
     [not found]   ` <CACAiNS3rirp4i=pGK2j1Q8CSbVGXthGuHx+nwr21FEyCd3=F_Q@mail.gmail.com>
2011-07-15 13:09     ` Christian Lamparter
2011-07-15 17:02       ` Pavel Roskin
2011-07-15 18:39         ` Christian Lamparter
2011-07-15 19:16           ` Pavel Roskin
2011-07-15 22:49             ` Pavel Roskin [this message]
2011-07-15 23:36               ` Christian Lamparter
2011-07-16  2:26                 ` Pavel Roskin
2011-07-16  8:43               ` Johannes Berg

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=4E20C3DC.3020200@gnu.org \
    --to=proski@gnu.org \
    --cc=chunkeey@googlemail.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 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).