All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Roskin <proski@gnu.org>
To: Christian Lamparter <chunkeey@googlemail.com>
Cc: Roman Shishkin <r.shishkin@gmail.com>, linux-wireless@vger.kernel.org
Subject: Re: Binary for carl9170
Date: Fri, 15 Jul 2011 13:02:55 -0400	[thread overview]
Message-ID: <4E2072BF.6000306@gnu.org> (raw)
In-Reply-To: <201107151509.23258.chunkeey@googlemail.com>

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.

I made some changes to the ath module and wanted to make a quick check 
that carl9170 is OK.  First I found that the 1.9.2 firmware won't work 
with wireless-testing.  Then I found that the binary is not there.  Then 
I downloaded the sources and ran "make -C toolchain".  After a long 
download, I got

configure: error: Building GCC requires GMP 4.2+, MPFR 2.3.1+ and MPC 
0.8.0+.
Try the --with-gmp, --with-mpfr and/or --with-mpc options to specify

No big deal, I'll need to install some libraries and restart make.  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.

At this point I start having doubts whether it's easier just to look at 
my changes more carefully and send them.

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.

-- 
Regards,
Pavel Roskin

  reply	other threads:[~2011-07-15 17:02 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 [this message]
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
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=4E2072BF.6000306@gnu.org \
    --to=proski@gnu.org \
    --cc=chunkeey@googlemail.com \
    --cc=linux-wireless@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.