All of lore.kernel.org
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Johannes Berg <johannes@sipsolutions.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 10:53:45 -0500	[thread overview]
Message-ID: <50325D89.9080209@lwfinger.net> (raw)
In-Reply-To: <1345459509.4459.5.camel@jlt3.sipsolutions.net>

On 08/20/2012 05:45 AM, Johannes Berg wrote:

Johannes,

> Unfortunately, I can't just release this firmware, it was mostly
> internal experimental builds, we released the -6 version later. However,
> as Thomas pointed out, it should be possible to backport some patches to
> make the driver in 3.1.9 work with the device, that simply wasn't a
> concern for us and it's not entirely clear to me that such patches are
> candidates for stable.

The openSUSE user has gotten his system working by installing the 
compat-wireless package. I do not know if he could patch and compile his own 
kernel, and I don't have that device in my collection, thus I would be unable to 
test any such changes.

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.

Larry



  reply	other threads:[~2012-08-20 15:53 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 [this message]
2012-08-20 16:01     ` Johannes Berg
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=50325D89.9080209@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=ben@decadent.org.uk \
    --cc=ilw@linux.intel.com \
    --cc=johannes@sipsolutions.net \
    --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 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.