From: Ferenc Wagner <wferi@niif.hu>
To: Zhu Yi <yi.zhu@intel.com>
Cc: "ipw2100-devel@lists.sourceforge.net"
<ipw2100-devel@lists.sourceforge.net>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [Ipw2100-devel] 2.6.32-rc4 ipw2200: oops on missing firmware
Date: Sat, 17 Oct 2009 04:13:43 +0200 [thread overview]
Message-ID: <87bpk64vjc.fsf@tac.ki.iif.hu> (raw)
In-Reply-To: <1255589428.3719.465.camel@debian> (Zhu Yi's message of "Thu, 15 Oct 2009 14:50:28 +0800")
Zhu Yi <yi.zhu@intel.com> writes:
> OK. The rfkill device is removed without being added before! The root
> cause is, for non-monitor interfaces, the syntax for
> alloc_ieee80211/free_80211 is wrong. Because alloc_ieee80211 only
> creates (wiphy_new) a wiphy, but free_80211() does wiphy_unregister()
> also. This is only correct when the later wiphy_register() is called
> successfully, which apparently is not the case for your fw doesn't exist
> one. Please see if this patch fix the problem.
I confirm that your patch fixes the problem for me. With it, the
kernel doesn't oops and modprobe isn't killed after the firmware load
timeout. Without firmware, the loaded module is nonfunctional, as
expected.
--
Thanks,
Feri.
prev parent reply other threads:[~2009-10-17 2:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87hbu3h023.fsf@tac.ki.iif.hu>
2009-10-13 16:55 ` 2.6.32-rc4 ipw2200: oops on missing firmware Frans Pop
2009-10-13 20:22 ` Ferenc Wagner
2009-10-15 6:50 ` [Ipw2100-devel] " Zhu Yi
2009-10-15 12:59 ` John W. Linville
2009-10-17 2:13 ` Ferenc Wagner [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=87bpk64vjc.fsf@tac.ki.iif.hu \
--to=wferi@niif.hu \
--cc=ipw2100-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=yi.zhu@intel.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 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).