From: "John W. Linville" <linville@tuxdriver.com>
To: Don Fry <donald.h.fry@intel.com>
Cc: linux-wireless@vger.kernel.org, kay@vrfy.org, jcm@redhat.com,
linux-modules@vger.kernel.org
Subject: Re: question on non-kernel patch
Date: Fri, 20 Apr 2012 10:09:17 -0400 [thread overview]
Message-ID: <20120420140917.GA13844@tuxdriver.com> (raw)
In-Reply-To: <1334868960.7300.10.camel@dfry-linux1>
On Thu, Apr 19, 2012 at 01:56:00PM -0700, Don Fry wrote:
> Hi John,
> We have a change to the iwlwifi driver for the near future
> which will dynamically load a different module based on the version
> of microcode installed on the system. The driver does a
> request_module_nowait after obtaining the firmware file loaded as part
> of modprobe. This all works fine, however unloading the module is not
> symmetrical/straight forward.
> It looks like there are capabilities already implemented to
> make this easy. If I put the following script into /etc/modprobe.d
> then modprobe iwlwifi-r will do the right thing.
> It is backward compatible with the current iwlwifi driver.
> How do I get this out in the community before we submit the patch that
> would break iwlwifi removal?
>
> Thanks,
> Don
>
>
> # /etc/modprobe.d/iwlwifi.conf
> # iwlwifi will dyamically load either iwldvm or iwlmvm depending on the
> # microcode file installed on the system. When removing iwlwifi, first
> # remove the iwl?vm module and then iwlwifi.
> remove iwlwifi \
> (/sbin/lsmod | grep -o -e ^iwlmvm -e ^iwldvm -e ^iwlwifi | xargs /sbin/rmmod) \
> && /sbin/modprobe -r mac80211
Honestly, I'm not entirely sure -- this seems like a peculiar
situation. Can you go into more detail about why this seems necessary?
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2012-04-20 14:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-19 20:56 question on non-kernel patch Don Fry
2012-04-20 14:09 ` John W. Linville [this message]
2012-04-20 14:41 ` Fry, Donald H
2012-04-20 15:17 ` Larry Finger
2012-04-23 18:56 ` Michal Marek
2012-04-25 19:36 ` John W. Linville
2012-04-25 23:28 ` Kay Sievers
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=20120420140917.GA13844@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=donald.h.fry@intel.com \
--cc=jcm@redhat.com \
--cc=kay@vrfy.org \
--cc=linux-modules@vger.kernel.org \
--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).