linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christian Lamparter <chunkeey@googlemail.com>
To: Pavel Roskin <proski@gnu.org>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Binary for carl9170
Date: Sat, 16 Jul 2011 01:36:43 +0200	[thread overview]
Message-ID: <201107160136.44182.chunkeey@googlemail.com> (raw)
In-Reply-To: <4E20C3DC.3020200@gnu.org>

On Saturday 16 July 2011 00:49:00 Pavel Roskin wrote:
> 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/
The question is, is kernel.org really a good address to host those firmwares.
especially in a personal folder.

> I don't want to setup an alternative competing repository for carl9170 
> firmwares. Also, it would be nice to have the 1.9.4 firmware on 
> http://www.kernel.org/pub/linux/kernel/people/chr/carl9170/fw/

I would rather have them on wireless.kernel.org. Just like the ath9k_htc
firmware.
> 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.
Good thinking, we could add a changelog, the configuration and
some infos like supported features [e.g.: number of supported virtual
interfaces, supported WoWLAN triggers, etc...] to the same page.

> 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.
oh no, this should be just fine.

Thanks,
	Christian

  reply	other threads:[~2011-07-15 23:34 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
2011-07-15 23:36               ` Christian Lamparter [this message]
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=201107160136.44182.chunkeey@googlemail.com \
    --to=chunkeey@googlemail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=proski@gnu.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).