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 12:45:09 +0200 [thread overview]
Message-ID: <1345459509.4459.5.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <502D0C72.2050207@lwfinger.net> (sfid-20120816_170635_404509_F239FBF6)
Hi Larry,
> I am trying to help an openSUSE 12.1 user who is running kernel 3.1.9, who has
> an Intel 802.11 b/g/n card with Bluetooth mounted in an HP dvdt-7000 Quad
> Edition Series computer.
>
> The driver is asking for firmware named "iwlwifi-2030-5.ucode"; however, that
> particular file does not exist in /lib/firmware, nor is in the linux-firmware
> git repo where only the version 6 firmware exists.
>
> I could find no record of the firmware ever being in the git repo, nor could I
> find it using a Google search. For users of kernel 3.1, I request that this
> firmware file be submitted to linux-firmware. In addition, if you send me a copy
> of the file, I will see that the OP on the openSUSE Forum gets a copy.
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.
johannes
next prev parent reply other threads:[~2012-08-20 10:45 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 [this message]
2012-08-20 15:53 ` Larry Finger
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=1345459509.4459.5.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).