From: Christian Lamparter <chunkeey@googlemail.com>
To: tmail133@kglug.org
Cc: linux-wireless@vger.kernel.org
Subject: Re: Carl9170 firmware source code /w kernel.org down
Date: Thu, 6 Oct 2011 16:43:24 +0200 [thread overview]
Message-ID: <201110061643.24960.chunkeey@googlemail.com> (raw)
In-Reply-To: <3b4ddb232a2c884c0d83ee5fe1754932.squirrel@mail.errtech.com>
On Wednesday, October 05, 2011 03:11:08 AM chris wrote:
> How can I get the source code for the Carl9170 firmware
> and drive with kernel.org being down?
Sure, but why the sudden interest?
http://www.sendspace.com/file/cvg2gv [~132 kb]
[This is a snapshot from the latest HEAD, if you
want a specific release just let me know].
> The wiki says:
>
> You can get the firmware source code from
> http://git.kernel.org/?p=linux/kernel/git/chr/carl9170fw.git.
The kernel.org git is still unavailable and will be for
some time:
https://www.linuxfoundation.org/news-media/blogs/browse/2011/08/cracking-kernelorg
Regards,
Chr
prev parent reply other threads:[~2011-10-06 14:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-05 1:11 Carl9170 firmware source code /w kernel.org down chris
2011-10-06 14:43 ` Christian Lamparter [this message]
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=201110061643.24960.chunkeey@googlemail.com \
--to=chunkeey@googlemail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=tmail133@kglug.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).