From: Christian Lamparter <chunkeey@googlemail.com>
To: Pavel Roskin <proski@gnu.org>
Cc: Roman Shishkin <r.shishkin@gmail.com>, linux-wireless@vger.kernel.org
Subject: Re: Binary for carl9170
Date: Fri, 15 Jul 2011 20:39:06 +0200 [thread overview]
Message-ID: <201107152039.07294.chunkeey@googlemail.com> (raw)
In-Reply-To: <4E2072BF.6000306@gnu.org>
On Friday 15 July 2011 19:02:55 Pavel Roskin wrote:
> On 07/15/2011 09:09 AM, Christian Lamparter wrote:
> > On Friday 15 July 2011 14:31:07 Roman Shishkin wrote:
> >> Source code avaliable of course, but I need just the binary of 1.9.4.
> >> Probably lot of casual linux users needs this binary too :)
> > Oh no, the firmware is supposed to be shipped by the distribution and
> > not "installed by hand". After all, they provide compiled and fully tested
> > packages for kernel+driver+userland and in doing so verify that no
> > malicious code compromises the system's security.
>
> Christian, I think the latest firmware needs to be on the site. I
> understand that you want to keep the entry barrier high, but it's
> hurting wrong people.
> [...]
> But that's more time to spend on something I thought would take minutes.
> And I'll have to keep the toolchain somewhere if I want to compile
> future version of the firmware.
>
> I was complaining recently that AR5210 hard to get to work (it only
> works on old motherboards), but I think I can get it to work faster than
> AR9170.
>
> Not providing the binary hurts potential tester and contributors.
??? [high entry barrier? no, that theory is something you just made up]
Anyway, pretty much everyone can compile, test and upload their own
favorite firmware on the wiki site. In fact, this is what the site is for, right?
So, since you already have a working version, why simply put it on the
wiki? Or do you really prefer to argue with some uncooperative fool
instead?
next prev parent reply other threads:[~2011-07-15 18:36 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 [this message]
2011-07-15 19:16 ` Pavel Roskin
2011-07-15 22:49 ` Pavel Roskin
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=201107152039.07294.chunkeey@googlemail.com \
--to=chunkeey@googlemail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=proski@gnu.org \
--cc=r.shishkin@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).