All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Lamparter <chunkeey@googlemail.com>
To: Roman Shishkin <r.shishkin@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Binary for carl9170
Date: Fri, 15 Jul 2011 15:09:22 +0200	[thread overview]
Message-ID: <201107151509.23258.chunkeey@googlemail.com> (raw)
In-Reply-To: <CACAiNS3rirp4i=pGK2j1Q8CSbVGXthGuHx+nwr21FEyCd3=F_Q@mail.gmail.com>

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.

> I want to check new version at first rather than discuss about my
> dongles bug.
wait... how come you know that the new version might fix a bug?
Furthermore, how do you know that it's a bug in the first place,
what's your reference and how do you test it?

Regards,
	Chr

  parent reply	other threads:[~2011-07-15 13:07 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 [this message]
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
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=201107151509.23258.chunkeey@googlemail.com \
    --to=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.