From: Johannes Berg <johannes@sipsolutions.net>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: Intel Linux Wireless <ilw@linux.intel.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
Ben Hutchings <ben@decadent.org.uk>
Subject: Re: Missing firmware iwlwifi-2030-5.ucode
Date: Mon, 20 Aug 2012 18:01:34 +0200 [thread overview]
Message-ID: <1345478494.4459.30.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <50325D89.9080209@lwfinger.net> (sfid-20120820_175351_872841_14CD8D92)
On Mon, 2012-08-20 at 10:53 -0500, Larry Finger wrote:
> I'm still concerned about the bigger picture. I can understand that the -5
> version was experimental, but why was a driver released that needed a firmware
> version that could never be obtained? If any driver version needs a particular
> firmware, the fw must be available as long as anyone might be using that driver.
> To me, that means forever.
Well, yes. That firmware, however, never was never available publicly.
The fact that the driver was released anyway is due to us working on the
driver upstream while working with the experimental internal firmware.
johannes
next prev parent reply other threads:[~2012-08-20 16:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-16 15:06 Missing firmware iwlwifi-2030-5.ucode Larry Finger
2012-08-19 11:26 ` Thomas Backlund
2012-08-20 10:45 ` Johannes Berg
2012-08-20 15:53 ` Larry Finger
2012-08-20 16:01 ` Johannes Berg [this message]
2012-08-21 4:55 ` Gábor Stefanik
2012-08-21 5:14 ` Larry Finger
2012-08-21 6:46 ` Johannes Berg
2013-06-17 14:57 ` antonio
2021-02-25 5:41 ` Robbi Nespu
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=1345478494.4459.30.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=Larry.Finger@lwfinger.net \
--cc=ben@decadent.org.uk \
--cc=ilw@linux.intel.com \
--cc=linux-wireless@vger.kernel.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).