From: Jesper Juhl <jesper.juhl@gmail.com>
To: Alejandro Bonilla <abonilla@linuxwireless.org>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
ipw2100-admin@linux.intel.com,
Roman Zippel <zippel@linux-m68k.org>,
Sam Ravnborg <sam@ravnborg.org>
Subject: [PATCH] wrong firmware location in IPW2100 Kconfig entry (Was: IPW2100 Kconfig)
Date: Tue, 6 Sep 2005 20:48:29 +0200 [thread overview]
Message-ID: <200509062048.29495.jesper.juhl@gmail.com> (raw)
In-Reply-To: <005101c5b311$4ca69a50$a20cc60a@amer.sykes.com>
On Tuesday 06 September 2005 20:32, Alejandro Bonilla wrote:
> Hi,
>
> I checked the IPW2100 in the current git from linux-2.6 and the menuconfig
> help (Kconfig) says you need to put the firmware in /etc/firmware, it should
> be /lib/firmware.
>
> Who should I send the "patch" to? Or can someone simply change that?
>
Firmware should go into /lib/firmware, not /etc/firmware.
Found by Alejandro Bonilla.
Signed-off-by: Jesper Juhl <jesper.juhl@gmail.com>
---
drivers/net/wireless/Kconfig | 2 +-
1 files changed, 1 insertion(+), 1 deletion(-)
--- linux-2.6.13-mm1-orig/drivers/net/wireless/Kconfig 2005-09-02 23:59:51.000000000 +0200
+++ linux-2.6.13-mm1/drivers/net/wireless/Kconfig 2005-09-06 20:39:45.000000000 +0200
@@ -152,7 +152,7 @@
In order to use this driver, you will need a firmware image for it.
You can obtain the firmware from
<http://ipw2100.sf.net/>. Once you have the firmware image, you
- will need to place it in /etc/firmware.
+ will need to place it in /lib/firmware.
You will also very likely need the Wireless Tools in order to
configure your card:
next prev parent reply other threads:[~2005-09-06 18:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-06 18:32 IPW2100 Kconfig Alejandro Bonilla
2005-09-06 18:48 ` Jesper Juhl [this message]
2005-09-06 18:51 ` [PATCH] wrong firmware location in IPW2100 Kconfig entry (Was: IPW2100 Kconfig) Alejandro Bonilla
2005-09-07 12:44 ` Jiri Slaby
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=200509062048.29495.jesper.juhl@gmail.com \
--to=jesper.juhl@gmail.com \
--cc=abonilla@linuxwireless.org \
--cc=ipw2100-admin@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=zippel@linux-m68k.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).