From: Christian Lamparter <chunkeey@googlemail.com>
To: Marius Ladegaard Meyer <marius.l.meyer@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: carl9170 fw 1.9.3 on the binary archive page
Date: Tue, 24 May 2011 18:11:04 +0200 [thread overview]
Message-ID: <201105241811.05128.chunkeey@googlemail.com> (raw)
In-Reply-To: <BANLkTinenbgnE0c8ZQh2wfBOjWNc=T++Dw@mail.gmail.com>
Hello,
On Tuesday 24 May 2011 14:39:16 Marius Ladegaard Meyer wrote:
> I am currently maintaining packages in the AUR of Arch Linux for the
> carl9170 driver and firmware. For the firmware package I use the binary
> firmware files available at
> http://www.kernel.org/pub/linux/kernel/people/chr/carl9170/fw/ I see in the
> git repo of carl9170fw that version 1.9.3 was tagged two months ago, and I
> would like to provide the newest version to Arch users. Would it be possible
> for you to upload a binary to the aforementioned page please?
making new releases is not the issue. But "testing" everything in
every possible combination in different environments, with
different configurations and different devices is a huge task...
But I'm always baffled by distributions.
Why do they insist on having a binary firmware image, when
they can build one from scratch as well... After all, they do
so for every other application/packet, right?
Regards,
Chr
next parent reply other threads:[~2011-05-24 16:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BANLkTinenbgnE0c8ZQh2wfBOjWNc=T++Dw@mail.gmail.com>
2011-05-24 16:11 ` Christian Lamparter [this message]
[not found] ` <BANLkTik7Gg81+KaB2eGnkpG8kSzTD7cwaw@mail.gmail.com>
2011-05-25 12:45 ` carl9170 fw 1.9.3 on the binary archive page Christian Lamparter
[not found] ` <BANLkTikR9pRgvFEh9ahFSk1KpdP9Oxz1Yw@mail.gmail.com>
2011-05-25 20:27 ` Christian Lamparter
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=201105241811.05128.chunkeey@googlemail.com \
--to=chunkeey@googlemail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=marius.l.meyer@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.